-
Notifications
You must be signed in to change notification settings - Fork 356
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
v0.8 deps update #397
v0.8 deps update #397
Conversation
@joelamouche can you look at 7a6b95e . I've attempted to update the types bundle. Is this correct? |
#398) * Change fork test behavior. Test now retrieves re-inserted tx at new canonical chain * Fix format * Change let for const
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 basically good to me. Let's get it merged before it gets stale :)
npm run test -- -j $(($(nproc) / 2 - 2)); | ||
npm run test -- -j 1 |
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.
Do we want to keep this?
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.
@crystalin @notlesh Do we want to keep this change?
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.
Yes for now, it seems to resolve some issue we have in github runners, and it doesn't reduce much the CI duration (<1%)
@notlesh @JoshOrndorff Added cli arg for |
runtime/Cargo.toml
Outdated
pallet-ethereum = { default-features = false, git = "https://github.com/purestake/frontier", branch = "notlesh-moonbeam-v0.7" } | ||
fp-rpc = { default-features = false, git = "https://github.com/purestake/frontier", branch = "notlesh-moonbeam-v0.7" } | ||
pallet-ethereum = { default-features = false, git = "https://github.com/purestake/frontier", branch = "joshy-substrate-2be8fcc4" } | ||
fp-rpc = { version = "1.0.1-dev", default-features = false, git = "https://github.com/purestake/frontier", branch = "joshy-substrate-2be8fcc4" } |
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.
Any reason we need an explicit version here?
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.
I think we're stuck with this as long as we're pointing to a branch that has -dev
versions. Cargo even seems to understand that this is "pre-release":
prerelease package needs to be specified explicitly
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.
...but I suppose you're suggesting we not specify the version. Seems reasonable since we're specifying a git repo instead...
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.
@joelamouche can you please look at 7a6b95e . I don't want to mess up your types bundle. |
npm run test -- -j $(($(nproc) / 2 - 2)); | ||
npm run test -- -j 1 |
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.
Yes for now, it seems to resolve some issue we have in github runners, and it doesn't reduce much the CI duration (<1%)
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. I have questions
@@ -240,6 +240,108 @@ export const moonbeamDefinitions = { | |||
}, | |||
}, | |||
}, | |||
{ |
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.
Are those the same types as above or is there a difference?
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.
They are mostly the same types. There is one difference though. I added "AuthorId": "AccountId"
.
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.
ok that means we need to publish the new version of the types. Lmk if you want me to do it
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.
Yes, please publish it. Thank you.
@@ -19,7 +19,7 @@ describeDevMoonbeam("Web3Api Information", (context) => { | |||
expect(hash.result).to.be.equal(localhash); | |||
}); | |||
|
|||
it("should report peer count in hex", async function () { | |||
it.skip("should report peer count in hex", async function () { |
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.
this is volontary?
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.
This test requires a "fix" for net_peerCount
being returned as an int instead of hex. This is something we've patched on top of frontier
but would like to submit a flexible PR that supports both. The underlying problem is that Ethereum nodes have been inconsistent about the return type.
To keep CI green, we skipped it...
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.
We can unskip it once we bring in polkadot-evm/frontier#377 which we should be able to do very soon.
What does it do?
This builds off of @JoshOrndorff 's #396 (which focused, in part, on updating dependencies) with the goal of stabilizing the codebase, getting CI green, etc.
What important points reviewers should know?
Is there something left for follow-up PRs?
What alternative implementations were considered?
Are there relevant PRs or issues in other repositories (Substrate, Polkadot, Frontier, Cumulus)?
What value does it bring to the blockchain users?
Checklist