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
{{ message }}
This repository has been archived by the owner on Dec 31, 2024. It is now read-only.
Automatically mark packages as broken if they throw an error
At the moment, I don't know if there is a way to differentiate both errors for the current builder code, but they do not happen at the same code paths during evaluation.
Usage of builtin.tryEval can allow evaluating if an expression did evaluate successfully and outputs a boolean (true or false).
However I'm still missing what kinds of errors did the evaluation trigger, in order to be able to filter at the error evaluation level, something more precise is needed.
Maybe checking with builtin.hasAttr "xyz" pkgs before accessing to pkgs.xyz, this would probably solve the issue if the pkgs does not exists.
But for packages that exists but are broken, it still isn't enough.
There are a few improvements that could be made to fully automatically maintain, the tracker.
todo
if they raise a missing attribute exception.broken
if they throw an error (i.e. Python 2 deprecated/removed) at evaluation.Automatically mark packages as
todo
if they raise a specific exceptionAn update to the nix code is needed to automatically mark the pkg as "todo" if
Does not exist in Nixpkgs unstable
raises not found attribute exception, such as this one :
Nix traceback
Automatically mark packages as
broken
if they throw an errorAt the moment, I don't know if there is a way to differentiate both errors for the current builder code, but they do not happen at the same code paths during evaluation.
Nix traceback
The text was updated successfully, but these errors were encountered: