-
Notifications
You must be signed in to change notification settings - Fork 786
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
debug_node wants but does not get sentinel value for reading blocks #606
Comments
Merged
theoreticalbts
added a commit
that referenced
this issue
Dec 9, 2016
theoreticalbts
added a commit
that referenced
this issue
Dec 9, 2016
theoreticalbts
added a commit
that referenced
this issue
Dec 9, 2016
Closing since this was merged. |
On1x
pushed a commit
to VIZ-Blockchain/viz-cpp-node
that referenced
this issue
May 28, 2018
On1x
pushed a commit
to VIZ-Blockchain/viz-cpp-node
that referenced
this issue
May 28, 2018
…-comments Fix start_author in get_discussions_by_comments. steemit#606
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Warning with
~0
here led me to look at this code indebug_node
. It seems to be expecting to get~0
as a sentinel value for "I couldn't read a block" but the corresponding code inblock_log.cpp
here cannot produce such sentinel value. This issue merits further investigation.The text was updated successfully, but these errors were encountered: