This is a helper library for usb access from python scripts. It is added
here in support of the cflib (crazyflie library) used to controll the
small crazyflie nano drones.
Signed-off-by: Brian McGillion <bmg.avoin@gmail.com>
Without the change the eval fails as:
$ nix build --no-link -f. pythonInterpreters.pypy310_prebuilt.tests.test-packageOverrides
error:
… in the condition of the assert statement
at pkgs/development/interpreters/python/tests.nix:212:11:
211| in
212| assert myPython.pkgs.foobar == myPython.pkgs.numpy;
| ^
213| myPython.withPackages (ps: with ps; [ foobar ]);
… while evaluating the attribute 'outPath'
at lib/customisation.nix:421:7:
420| drv.drvPath;
421| outPath =
| ^
422| assert condition;
(stack trace truncated; use '--show-trace' to show the full, detailed trace)
error: attribute 'mainProgram' missing
at pkgs/by-name/me/meson/package.nix:75:52:
74| --replace-fail "PythonExternalProgram('python3', mesonlib.python_command)" \
75| "PythonExternalProgram('${python3.meta.mainProgram}', mesonlib.python_command)"
| ^
76| substituteInPlace mesonbuild/modules/python3.py \
Polars is now a dependencies.
Running it with nix in some configuration fails to remove temporary
directories. Before skipping this step, it retries 10 times and doubles the waiting
time each time. We set max retries to 2.
GitHub comments have a length limit, so we can't just dump everything.
The 10k limit is arbitrary, but the assumption is that reviewing the
range-diff is not the sensible thing to do once it becomes a certain
size - reviewing the regular diff and treating the commit as "new" is
easier to do in that case. Thus, truncating should work out fine,
especially when the full range-diff is still available in the runner
log.
This could still end up in with an error, if a PR has multiple commits,
which all hit the limit. Let's get there first, before we try to fix
that hypothetical case, too.
Instead of failing the job, the workflow will now post review comments
as "Request Changes". This makes the feedback more readily visible and
avoids having to merge despite a failing CI job. It is also a
pre-requisite to enable required status checks / required workflows in
the future.
Committers are asked to confirm the differences by explicitly dismissing
the generated review. After dismissal, the related review comment will
automatically be marked as "resolved".
The comments only report warnings and errors. Reviews are automatically
dismissed when they have been addressed by the author and no problems
remain. If problems remain, existing, still pending, review comments
will be updated. If the same problems had already been dismissed
earlier, no new review comment will be created either.
Brian McGillion