Skip to content

Conversation

@dscho
Copy link
Member

@dscho dscho commented Oct 15, 2025

We have recently seen a flurry of bogus, duplicate issues, for Cygwin v3.6.5 and for OpenSSH v10.2.

The most likely/plausible cause is that GitHub is experiencing availability issues that it did not experience before, where listing existing issues fails with a HTTP status of 500. Which revealed that this here Action lazily did not even catch those (because it did not need to).

Let's catch those problems and avoid opening issues in those instances.

dscho added 2 commits October 15, 2025 16:27
As of a couple of weeks ago, GitHub seems to have serious issues with
reliability, where the issues sometimes fail to be listed.

Those issues revealed that this here Action failed to inspect the
returned HTTP status (which was previously unnecessary because it was
always 200, but this now apparently is no longer as reliable).

Let's inspect the `status` attribute to find out, and complain loudly
instead of opening duplicate issues.

Signed-off-by: Johannes Schindelin <[email protected]>
Signed-off-by: Johannes Schindelin <[email protected]>
@dscho dscho merged commit 7352cd8 into main Oct 16, 2025
1 check passed
@dscho dscho deleted the avoid-duplicate-issues branch October 16, 2025 15:47
@dscho
Copy link
Member Author

dscho commented Oct 17, 2025

Dangit. This did not fix the issue. There was another duplicate issue, namely git-for-windows/git#5887, probably opened by this workflow job. And that did use v0.0.13 of rss-to-issues...

Maybe the order in which the issues are now reported is no longer sorted by time?

In any case, I think it is safe to say that this Action needs to output more:

  • It needs to print a ::notice:: when it opened a new issue
  • It needs to print out which new RSS feed entries it wants to look for
  • For the time being, it might need to print out which existing issues it saw
  • In general, the Action should log what it is doing (retrieving feed from <url>, looking through <N> feed items, etc)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants