diff options
| author | luigi1111 <luigi1111w@gmail.com> | 2022-05-10 16:53:48 -0500 |
|---|---|---|
| committer | luigi1111 <luigi1111w@gmail.com> | 2022-05-10 16:53:48 -0500 |
| commit | 8480575cec2c6dd9de0660849dfa581657bb6d07 (patch) | |
| tree | 5b6075aa536700c334c52d1e38c7353728d6948e /src | |
| parent | fbd1f1e476de88f391994a27a7dcca05adba4e7d (diff) | |
| parent | 070e41d88b79908107518f8716b9ce8418c4b194 (diff) | |
| download | monzero-core-8480575cec2c6dd9de0660849dfa581657bb6d07.tar.gz monzero-core-8480575cec2c6dd9de0660849dfa581657bb6d07.tar.xz monzero-core-8480575cec2c6dd9de0660849dfa581657bb6d07.zip | |
Merge pull request #8300
070e41d Change Github to GitHub (Abdullah)
Diffstat (limited to 'src')
| -rw-r--r-- | src/net/zmq.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/net/zmq.cpp b/src/net/zmq.cpp index bd7855f21..2b3ca8376 100644 --- a/src/net/zmq.cpp +++ b/src/net/zmq.cpp @@ -134,7 +134,7 @@ namespace zmq { /* ZMQ documentation states that message parts are atomic - either all are received or none are. Looking through ZMQ code and - Github discussions indicates that after part 1 is returned, + GitHub discussions indicates that after part 1 is returned, `EAGAIN` cannot be returned to meet these guarantees. Unit tests verify (for the `inproc://` case) that this is the behavior. Therefore, read errors after the first part are treated as a |