Fabiano Prestes
Fabiano Prestes
This seems to be the same I experienced and reported on #1555
So I think that what is happening is the heartbeat in only every 30 seconds or so and we drop the participant in 60 seconds, so if the first heartbeat...
`Aug 15 16:50:56.539 ERROR aleo_setup_coordinator::api::queue::contributor: Error inserting confirmation key for contributor with address aleo1sqm5us597r4qyrzhkpxdd2g68ftngysle8jpw7pwjkn6tt79jy8qa2s74t: UNIQUE constraint failed: participation.confirmation_key` We usually see this line in the log after the timeout :point_up:
Thank you, @kyle-u410. I have concerns that, even without logging, this is an attack vector, because it will cause load in all clients and validators.
@vicsn Yes, it has been running on all 3 networks without any noticeable issues. I am of the opinion that one should not be syncing with a bootstrap node, especially...
@iamalwaysuncomfortable could you please confirm this is fixed with the merging of #3413?
@kpandl this branch has conflicts. Could you please resolve them before we attempt to merge?
`check-clippy` finishes fine, in 34s. It is just CircleCI being its usual garbage.
CI link: https://app.circleci.com/pipelines/github/AleoNet/snarkOS?branch=pull%2F3358%2Fhead
Not sure if it helps but can we upgrade to Rust 1.79.0?