-
Notifications
You must be signed in to change notification settings - Fork 767
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
Replace unnecessary &mut self
with &self
in BlockImport::import_block()
#5339
Conversation
The CI pipeline was cancelled due to failure one of the required jobs. |
1238396
to
90f6ec0
Compare
Is there some kind of tooling for semver? There are a lot of files changed and I'd hate to go through each crate manually. |
Yea am gonna try to run the bot now for this. Just added it now #5331 |
Looks like the bot failed. Ran the script manually now. You probably want to demote some of these Details
|
Nice, thank you! |
feac7a5
…block()` (paritytech#5339) There was no need for it to be `&mut self` since block import can happen concurrently for different blocks and in many cases it was `&mut Arc<dyn BlockImport>` anyway 🤷♂️ Similar in nature to paritytech#4844
After seeing some cases of reported changes that did not happen by the merge request proposer (like #5339), it became clear that [this](https://github.com/orgs/community/discussions/59677) is probably the issue. The base commit of the SemVer check CI is currently using the *latest* master commit, instead of the master commit at the time when the MR was created. Trying to get the correct base commit now. For this to be debugged, i have to wait until another MR is merged into master. --------- Signed-off-by: Oliver Tale-Yazdi <[email protected]>
There was no need for it to be
&mut self
since block import can happen concurrently for different blocks and in many cases it was&mut Arc<dyn BlockImport>
anyway 🤷♂️Similar in nature to #4844