-
Notifications
You must be signed in to change notification settings - Fork 53
Conversation
Hi Tim, cool, that already looks like a substantial amount of work and additions, happy to see the progress! Will think about the testing questions, can't promise though that I will make it today. Let's not over-rush now in the other direction 😄 , you can really take your time, I would actually prefer a bit if this can ripen a bit during 2-3 weeks of ongoing work. Of course this also depends on the time-slots you can set free. Anyway, cool to see progress here! |
Hi Tim, can you make For testing you should probably be able to build upon the integration tests and extend the Not sure if this is enough for tests but that would be a start, does this makes sense or do I miss something? Maybe also start early with this since according to my experience especially on the devp2p library having some tests makes further development a lot easier. |
Awesome sounds good. Yeah, baby steps! Sure thing, will have a bunch of free time this weekend. Good call on the cli args for versioning, that ran through my mind, will add! |
@tcsiwula Just to make sure that there is no misunderstanding: |
@holgerd77 option for the constructor, got it, thanks for clarifying -- pr update coming today |
Hey @holgerd77 how is your linting working for the CI or whatever? I saw there was a |
@tcsiwula Just run |
What about for fixing my linting errors? Running:
. |
Just temporarily add "--fix" to the standard lint command in package.json and fix the remaining ones manually. |
Pull Request Test Coverage Report for Build 134
💛 - Coveralls |
Issue update for node discovery v5Completion status: ~46% Structural tasks
Version 5 demo example tasks
New test coverage tasks
Pass existing tests, style, coverage
update next on monday 😀 |
It's best if you start with node records. The actual v5 protocol in geth is a temporary placeholder. |
@fjl thanks for the heads up, sounds good ^_^ |
@tcsiwula There is now a tracking issue for the actual protocol spec. Let's discuss there :). |
Hi @tcsiwula, thanks for all the active engagement in the direct protocol discussion with @fjl, I am also realizing that this is much more a work-in-progress spec than I thought. I would nevertheless try to see that we find some clean finish for this bounty PR, so that we don't have to carry this into 2019. 😛 Do you think it's realistic to get to a point where we have a somewhat complete version of a currently consistent draft state of the protocol implemented, or - if this is still too much work left - can't judge at the moment: do you see a consistent set of subfeatures/-parts that can be finished implementing, so that a) tests are running and (that would be the base conditions I could think of now, feel free to add). Best |
Succeeded by new PR #48 allowing administrative access & direct collaborator branch discovery-v5 |
WIP: Please do not merge yet
Fixes #19.
Issue update for node discovery v5
Completion status: ~46%
Today's date: Saturday August 25th 2018
Target finish date: Monday September 3rd 2018
Task break down: ~46% = [6.5 / 14] = [ ((4 ✅ + (3🚧/2)) ) / (14✅🚧✖️)]
Issue: #19
Pull request: #42
Structural tasks
Version 5 demo example tasks
New test coverage tasks
Pass existing tests, style, coverage
almost there 😀