Skip to content
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

fix: getMany: ensuring we set the want list #162

Merged
merged 3 commits into from
Jan 28, 2018

Conversation

pgte
Copy link
Contributor

@pgte pgte commented Jan 22, 2018

... independently of having all blocks or not.

@ghost ghost assigned pgte Jan 22, 2018
@ghost ghost added the status/in-progress In progress label Jan 22, 2018
@daviddias
Copy link
Member

@pgte seems that some race condition might be happening. See Jenkins and Circle

@daviddias daviddias added the P1 High: Likely tackled by core team if no one steps up label Jan 25, 2018
@pgte
Copy link
Contributor Author

pgte commented Jan 26, 2018

I don't see how this commit could have triggered a race condition. In this test, we're putting a block on node 1 before the test, and then getting it on node 2. The stats update occurs independently from the get, so the order of the sequence shouldn't matter.
I'll push a fix to this test.

@daviddias daviddias merged commit 8e91def into master Jan 28, 2018
@daviddias daviddias deleted the fix/final-pending-start branch January 28, 2018 03:00
@ghost ghost removed the status/in-progress In progress label Jan 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 High: Likely tackled by core team if no one steps up
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants