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
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered:
Ok, making some headway with this today … I’ve created tags in the upstream xyz provider so we can run upgrades on pulumi-xyz without it failing.
I’ve also added the ability to set the version of upgrade-provider when running in CI for better predictability and to enable testing.
Observations:
When using CI to create both the issue and PR, I’m still seeing no “fixes” appear.
When I re-run the PR creation locally it adds the “fixes”.
When closing existing PRs and re-running in CI, I also see the “fixes”.
Therefore, I think we’re running into an issue with a delay in the GitHub issue searching. I think there’s a delay between opening an issue and being able to search on the contents of the body.
I would guess searching on author doesn’t have this issue because it’s using a simpler indexing strategy which is updated synchronously at the point of saving, but the text body searching is only “eventually consistent”.
Therefore, I could see a few approaches to solving this:
Add a delay between creating the issue and starting the PR creation (not good IMO)
Remove the filtering on pulumiupgradeproviderissue so we just fetch the 100 latest issues in the repo and look at their titles for matching the exact upgrade issue title format
Try switching away from a keyword in the body and see if labels indexing is faster. This would require setting up new labels in all repos and reworking more aspects.
This might be running very quickly after the issue was created and it might not yet be indexed. Instead, just list the latest 100 issues and filter on exact title format instead.
The current rate of issue creation is low enough that the latest 100 issues should safely include all open upgrade issues.
Fixes#291
We'll continue to use the token for issue de-duplication as this only happens once per day and so is reliably in the GH issue search index.
What happened?
See example below - it seems that automation-created issues are missing the "Fixes" keyword.
Locally created PRs as pulumi/pulumi-dbtcloud#168 do not have this problem.
Example
pulumi/pulumi-auth0#687
should have closed
pulumi/pulumi-auth0#686
but was missing the "Fixes <issue #>" text .
Output of
pulumi about
n/a
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: