-
Notifications
You must be signed in to change notification settings - Fork 20.4k
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
cmd,eth: 16400 Add an option to stop geth once in sync. WIP for light mode #17321
Conversation
Thank you for your contribution! Your commits seem to not adhere to the repository coding standards
Please check the contribution guidelines for more details. This message was auto-generated by https://gitcop.com |
Thank you for your contribution! Your commits seem to not adhere to the repository coding standards
Please check the contribution guidelines for more details. This message was auto-generated by https://gitcop.com |
Thank you for your contribution! Your commits seem to not adhere to the repository coding standards
Please check the contribution guidelines for more details. This message was auto-generated by https://gitcop.com |
Hi, I am working on the light mode implementation right now. Do you have any feedback on this or why it is failing the two integration tests, I am having trouble running the integration tests and am wondering if this could be a timing out error |
This does appear to work for me for the full node. I am now working on the light node implementation |
Hi @karalabe i have added in support for light mode how can I receive feedback on this? |
Hi @zsfelfoldi light node is working on my end and I resolved the merge conflict, any feedback on why it's not passing the tests? |
So regarding the tests:
That means you have not used |
I'm not quite sure about what happens in this PR, if the sync method is neither |
@holiman I think some of the issues were caused by merging with several recent commits. I am working on fixing those. If the node is not fast/light it will stop geth regardless when it is caught up. Should I make it so that it only does that for full? |
@holiman I fixed the issues and I can confirm that for other modes, including archive mode, it also shuts down when synced. Let me know if I should change that, I can set it up so it does that for only full mode and does nothing else for others. |
@holiman @karalabe I have posted the question to issue 16400 and have not gotten clarification for about a week, as such I am taking the issue/feature to ask for a full stop regardless of mode should the flag be raised, which makes sense for the flag and it currently accomplished. Additionally, its cleaned and fits the standards/gofmt and is mergeable. Please let me know on any feedback there is for this |
Hi, Touching base again @holiman @karalabe @zsfelfoldi to see if there are any suggestions or updates |
Hi @karalabe and @rjl493456442 , I have pushed code for the direction I am going based on the last requests. I am not sure if this is the appropriate way to do this and am still waiting for feedback on if we should switch from the downloader event to a timestamp in the header, if we do the switch what the threshold should be, and feedback on what should be done regarding the time delay. Currently, I am looking at grabbing the time stamp in the downloader processFastSyncContent with a new event that triggers the shutdown. I am not 100% familiar with this portion of the downloader and this appears to work for full/fast mode and I am investigating light mode. Additionally, this will require a check for roughly every header. Please let me know your thoughts, I have pushed this early to get feedback. |
Any comments @karalabe or @rjl493456442? Also @adamschmideg the travis build still appears to be failing due to timeout errors unrelated to this code |
Not finished yet, trying a new method based on conversations with @rjl493456442 trying to take in @karalabe request |
I have added changes and am testing it based on earlier feedback |
Based on @rjl493456442 I have passed the latest header through the done event so that I can check and validate, based on time, if this downloader done event is the correct event to resolve @karalabe conversations/suggestions. I have also turned the flag into a boolean as @karalabe suggested. I am wrapping up testing now |
Any thoughts? |
I think the current implementation is pretty clean. My approval stands. @karalabe or @rjl493456442 or @fjl please review after @lhendre fixes the travis errors:
and from https://travis-ci.org/ethereum/go-ethereum/jobs/479247288 :
I'm not sure how that happens, it seems |
A few feedbacks, check out here. |
fixed the sug gested changes, testing on Rinkeby and looking into travis report |
Still testing on Rinkeby, but the travis report looks more promising after implementing the feedback |
@lhendre The travis errors are not relative with this PR, but please take a look at lint suggestion and fix it. And a few nitpicks: |
Linting issues fixed, wrapping up rinkeby testing |
@holiman @rjl493456442 @karalabe The issues where fixed. I have successfully tested this on Rinkeby and it is working properly |
Thanks for all the work you've put into this, @lhendre , it's sometimes very difficult to get PRs merged, even for us |
No Problem, Glad to help and thanks for the support! |
No description provided.