Travis is shutting down, so the last remaining job needs to be moved to cirrus ci. The others have been moved in #19179.

Useful skills:

Backround in:

• Travis CI, Cirrus CI
• python, bash
• linters

Want to work on this issue?

For guidance on contributing, please read CONTRIBUTING.md before opening your pull

As OpenSSL does not support asynchronous read/write duplex, sometimes, the asynchronous read/write logic needs to be changed to consecutive processing. An interface for viewing the job status in internal objects maybe helpful for this.

ASYNC_JOB *SSL_get_job(const SSL *s)
{
    return s->job;
}

Welcome to JavaScript community

Describe your change:

• Add an algorithm?
• Fix a bug or typo in an existing algorithm?
• Documentation change?

Checklist:

• I have read CONTRIBUTING.md.
• This pull request is all my own work -- I have not plagiarized.
• I know that p

Hello spoooopyyy hackers 🎃

This is a Hacktoberfest only issue! 👻

This is also data-sciency!

The Problem

Our English dictionary contains words that aren't English, and does not contain common English words.

Examples of non-common words in the dictionary:

"hlithskjalf",
  "hlorrithi",
  "hlqn",
  "hm",
  "hny",
  "ho",
  "hoactzin",
  "hoactzine

Currently stratumserver has no unit tests. This will improve the quality and allow future commits to be TDD safe. All units will be tested to ensure the module as a unit itself is tested.

Background

When a node has multiple private channels with the same peer, the hop hints in their payment requests will be populated with multiple channels. The purpose of these hop hints is to specify the next node's key and indicate the fees and cltv delta needed for route construction.

In pathfinding, due to non-strict forwarding, an LND node paying to this destination will only use the

Problem:

A common pattern is:

GUARD(s2n_stuffer_skip_write(stuffer, bytes_to_write));
uint8_t* ptr = suffer->blob.data + stuffer->write_cursor - bytes_to_write;

which could be simplified.

Solution:

*ptr could be an *out parameter to s2n_stuffer_skip_write

• Does this change what S2N sends over the wire? No.
• Does this change any public APIs? No.

We will be supporting v0.33 till the next major release (0.35). We should bump golangci-lint version to the latest version to fix ci failures. In doing so many linting errors will arise, these should be cleaned up in the same PR.

This is an easy first contribution to Tendermint, if you are looking to get your hands dirty :)

Clients that support multiple server connections would like to have a way to decide which server connection is best able to handle a query. Servers currently "sort of" expose their load as fees, but there's no real exposure of server load in a useful way. Some parameter should be added to the "server" publication stream that clients can just compare across servers to decide which is most likely to

https://scotthelme.co.uk/a-new-security-header-feature-policy/

I guess it will be easy to add, because we certainly don't use any of these features.
Or maybe "gyroscope" or so may be used by the random number generator in sjcl, but that's all.