Someone's bot is creating multiple repeated issues for failing packages

See:

It’s not helpful to flood the issues tracker with such things. We will be aware that something is broken, and it will be fixed eventually.

2 Likes

I assume Nixpkgs's current development workflow is not sustainable provides some context on why.

1 Like

Indeed, this is https://github.com/samuela/nixpkgs-upkeep/!

Apologies for the duplicates in this case… I was off-the-grid for the past week and did not have the opportunity to triage. nixpkgs-upkeep has some delicate methods for detecting and preventing duplicate issues. I’ll have to debug further why they didn’t apply here. Currently my guess is:

  1. https://github.com/NixOS/nixpkgs/issues/186871 and https://github.com/NixOS/nixpkgs/issues/186872 were race condition collisions and both submitted posts at the same time. Same thing with https://github.com/NixOS/nixpkgs/issues/187043 and https://github.com/NixOS/nixpkgs/issues/187045.
  2. The two latest issues were not flagged as duplicates of the first two issues since the nix store hashes of the dependencies had changed which caused the failure logs to differ.
4 Likes

Check out mitigate race conflicts between jobs when creating issues · samuela/nixpkgs-upkeep@d478e5c · GitHub which should fix issue 1 and ignore /nix/store/<hash>'s when looking at logs · samuela/nixpkgs-upkeep@d814770 · GitHub which should fix issue 2.

1 Like

Can you please stop automatically creating issues in nixpkgs and instead use one of your own repositories? They are not only sometimes duplicated with themselves but also the root cause is often duplicated and a minimum amount of triaging is missing. If the issue can be solved in less than 5 minutes there shouldn’t be an issue for it and instead a PR that fixes it straight away. Otherwise we eventually drown in untriaged issues.

3 Likes
Hosted by Flying Circus.