Renovate: Duplicate issues open when using multiple package files
What Renovate type are you using?
Renovate GitHub App
Describe the bug
Duplicate issues are opened for the same dependancy warning if you're using multiple package files.
Additional context
Please see https://github.com/pymedusa/Medusa/issues/4572
OmgImAlexis
All 4 comments
Sorry for the noise caused, that was the result of a race condition I didn't anticipate - it's meant to check each time if a matching issue is already open however we check for updates from npm in parallel so each one created its own issue essentially simultaneously.
It only happens the first run, so is over now and shouldn't be repeated. However I'll disable the functionality on the bot until I've fixed it. I can perhaps combine it with #2225 as it looks like I need to delay the creation of issues until it can be done synchronously anyway.
rarkins
on 5 Jul 2018
I know this is off-topic..
Is there anything else I need todo to get the bot running again now that we've merged the config into master? We had to change baseBranches and it looks like the bot's closed the old pin PR off because of that but nothing else has happened since.
OmgImAlexis
on 5 Jul 2018
@OmgImAlexis it was just queued up - see https://github.com/pymedusa/Medusa/pull/4578
rarkins
on 5 Jul 2018
:tada: This issue has been resolved in version 13.15.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
renovate-bot
on 5 Jul 2018
Related issues
Arcanemagus
路
4Comments
Flydiverny
路
4Comments
OmgImAlexis
路
4Comments
ChristianMurphy
路
4Comments
ptbrowne
路
3Comments
Most helpful comment
Sorry for the noise caused, that was the result of a race condition I didn't anticipate - it's meant to check each time if a matching issue is already open however we check for updates from npm in parallel so each one created its own issue essentially simultaneously.
It only happens the first run, so is over now and shouldn't be repeated. However I'll disable the functionality on the bot until I've fixed it. I can perhaps combine it with #2225 as it looks like I need to delay the creation of issues until it can be done synchronously anyway.