Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

fix for notice forwarding #835

Merged
merged 1 commit into from
Dec 1, 2017
Merged

Conversation

pmesnier
Copy link
Contributor

OK, this should prevent notice forwarding all together. Which is OK for now since the mesh connects all producers to each other.

@@ -1516,6 +1516,7 @@ namespace eosio {
// notices of previously unknown blocks or txns,
//
fc_dlog(logger, "got a notice_message from ${p}", ("p",c->peer_name()));
bool can_fwd = false;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we get a comment here or below, indicating we are not currently setting it?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's going to take a little more time to figure out the safe way to determine whether or not to forward notifications.

@heifner heifner merged commit 21f37d4 into master Dec 1, 2017
spoonincode pushed a commit that referenced this pull request Dec 8, 2017
fix for notice forwarding

(reapplied on noon branch)
@pmesnier pmesnier deleted the p2p-sync-ignore-txns-stat-221-gh-833 branch December 20, 2017 09:06
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants