aboutsummaryrefslogtreecommitdiff
path: root/src/net/zmq.cpp
diff options
context:
space:
mode:
authorluigi1111 <luigi1111w@gmail.com>2022-05-10 16:53:48 -0500
committerluigi1111 <luigi1111w@gmail.com>2022-05-10 16:53:48 -0500
commit8480575cec2c6dd9de0660849dfa581657bb6d07 (patch)
tree5b6075aa536700c334c52d1e38c7353728d6948e /src/net/zmq.cpp
parentMerge pull request #8293 (diff)
parentChange "Github" to "GitHub" (diff)
downloadmonero-8480575cec2c6dd9de0660849dfa581657bb6d07.tar.xz
Merge pull request #8300
070e41d Change Github to GitHub (Abdullah)
Diffstat (limited to 'src/net/zmq.cpp')
-rw-r--r--src/net/zmq.cpp2
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