Description

A clear and concise description of what the bug is.

Setup

Create/import a GPG key.

Steps to Reproduce the behavior

Try to encrypt some text:

[root@master1 salt]# salt-call gpg.encrypt text=foo recipients=2CFCA2B538DD0FAC75838096A4E89A0D3328D483 output=/tmp/encypted_foo.txt user=salt
local:
    ----------
    comment:
        Encrypted data has bee

Issue description

In writing rust zmq bindings for tokio, the question came up about when zmq_send and zmq_recv might return EAGAIN when passed the ZMQ_DONTWAIT flag in a multipart message. The implication of the high water mark documentation is that it will only return EAGAIN on the first part of the multipart message, but I couldn't find it explicitly stated anywhere that this

We've got quite a few standardized labels configured in our GitHub but no documentation on which labels to use and when.

We should add a "Labeling Issues" section to our CONTRIBUTING.md so this informational is accessible to people.

Coming from a Python-in-Jupyter background, I notice that Tab works as you would expect (reveals all available methods/attributes), but Shift+Tab (signature hinting) does not. I could not find documentation on this. Is Shift+Tab not supported, or is my setup is incorrect?

Example:

type Foo struct {
    name string
    description string
}
func (f Foo) Qux(s string) string {
   

ZMTP3 and the Null Mechanism is implemented as part of #843, supporting Curve is a matter of implementing the Curve mechanism classes.

.Net port of libsodium:
https://www.nuget.org/packages/dlech.Chaos.NaCl/
https://github.com/dlech/Chaos.NaCl
https://github.com/drr00t/tweetnacl-cs/

ZMTP3 and Curve RFC:
https://rfc.zeromq.org/spec:37/ZMTP/
https://rfc.zeromq.org/spec:25/ZMTP-CURVE/

C

I'm not sure if this is the right place to remark this, but the documentation webpage has many links to the underlying zmq functions, but all links to those appear to be broken.

We should update the main API reference page:

• Include links to latest release API references
• Include links to past releases of API references
• Use same UI as skygear-JS-SDK

it seems that in the Docs, the server and client for PubSub got mixed up (p25).
It should be the Server that sends the message, and the client subscribes.

Hello, I think you should 'utf-8' decode the signature here:

https://github.com/fedora-infra/fedmsg/blob/develop/fedmsg/crypto/gpg.py#L177

Re-implement all the zguide Erlang examples in Chumak:
https://github.com/booksbyus/zguide/tree/master/examples

This will serve to document the library and iron out any quirks in the library.

Very low priority, but... the F# narrative docs are old. They're still perfectly valid. But they should be reviewed. In some case the code can be simplified. In other cases, it may be worth tweaking the code to use a newer API (or a different idiom).

(Note: this dove-tails with #66 and #144)

The official and locally built napalm-logs Docker container I made don't support the kafka transport. Upon inspection, I realized that kafka-python is missing from requirements.txt--so it will never make it into the container. I've fixed this in my fork, but wanted to know if that was deliberately left out or if there's a way to get it into the Docker container other than this that I'm not aware o