You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{"issue_number":1841,"body":"@ordian https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/4468802 was started for your command `\"$PIPELINE_SCRIPTS_DIR/commands/fmt/fmt.sh\"`. Check out https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/pipelines?page=1&scope=all&username=group_605_bot to know what else is being executed currently. \n\nComment `bot cancel 20-879efa0a-9e37-42d1-93b7-e400fda1bc7f` to cancel this command or `bot cancel` to cancel all commands in this pull request."}
looks like a race condition with bot clean which probably removed the initial comment which bot have left with promise to update 🙈
The reason is the sequence.. if you place bot clean after the other command - it will be executed after the first comment posted - so the posted comment will be treated as "outdated".
Solution would be - check only the comments which were left by bot BEFORE the current set of commands in any of the sequence
The text was updated successfully, but these errors were encountered:
thanks @ordian for reporting
It's looks like a race condition with bot clean which probably removed the initial comment which bot have left with promise to update 🙈
mordamax
changed the title
bot fmt fails with HttpError
"bot fmt" + "bot clean" fails with HttpError because of removed comment
Nov 24, 2023
paritytech/polkadot-sdk#1841 (comment)
EDIT: but the command succeeded eventually.
looks like a race condition with
bot clean
which probably removed the initial comment which bot have left with promise to update 🙈The reason is the sequence.. if you place
bot clean
after the other command - it will be executed after the first comment posted - so the posted comment will be treated as "outdated".Solution would be - check only the comments which were left by bot BEFORE the current set of commands in any of the sequence
The text was updated successfully, but these errors were encountered: