-
Notifications
You must be signed in to change notification settings - Fork 753
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
Update ethereumjs-blockchain to latest #469
Conversation
@holgerd77 I've successfully gotten this PR to test the TypeScript migration. I'll update that PR and bump this one as I adjust the API to minimize breaking changes and update the VM here to use what's changed. |
Cool, congrats! |
As ethereumjs/ethereumjs-blockchain#92 gets closer to the finish line, I've dropped the |
@whymarrh Since the blockchain library is now released can you update here (or alternatively just do a new PR if squashing all the commits and general cleaning produces more work after all the updates then just starting fresh)? |
1d3adcd
to
7733918
Compare
Thanks for the update! Not sure what's going on with the browser tests, we might need to do some quasi-empty comparison PR or something to see how these behave atm without the changes. Or eventually you can directly debug. Side note: can you additionally drop a note next time and not just mark this ready for review? One is getting absolutely no notification on this (or can this be adopted?), I just accidentally stumbled upon the update cause I am following you on GitHub and visited GitHub.com. 😜 |
My apologies, I thought that notified the reviewers. I will add a comment as well next time. |
I too am confused about the |
@whymarrh If you work on this (browser test fixing) can you address in a separate PR and not combine with this one? We are generally getting a bit too lazy with mixing up different fixes in combined PRs. |
7733918
to
7011f2c
Compare
Have updated this using the Preparation for a release on the |
7011f2c
to
e1e1b03
Compare
This is not really properly testable (at least I didn't find a way to do it) since TypeScript is giving me errors when referencing just the brach and not the release with the type declarations. I will do it other way around and directly do the release and then update on the final release here. |
4155757
to
4318f35
Compare
@s1na @alcuadrado Ok, this is working now including the API tests. Now ready for a review. |
This is not ideal, but you can build the other project, run Maybe git references can be used with one of those special npm scripts. Maybe |
Looks good thanks. Can you maybe also add annotations for other blockchain instances? I saw one in |
Same. I saw some in |
4318f35
to
983c33d
Compare
Got the one in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks!
Refs ethereumjs/ethereumjs-blockchain#92
This PR updates the version of ethereumjs-blockchain we're depending on to the latest, post-TypeScript version.
Note: while the above PR is in-progress this will be pointing to a Git URL of my fork. Once the PR is merged (and the tests here will serve as a useful smoke test) this PR will be updated with the correct version on the registry.