Something wonky with the lockfile? #1882
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#1882
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I tried updating my frontend Nix package to latest commit but yarn2nix does not seem to like it as shown by the following reproducer:
vikutest.nix
as follows:The only thing I can glean from the trace is that the
offline
package has something to do with it but bisecting points me to17d791027c
, which confusingly does not mentionoffline
at all.The
offline
package is actually an artefact of yarn2nix.I tried replicating what
yarn2nix
does:and the produced contains the following:
Weirdly, if I just run
yarn2nix > yarndeps.nix
in the project directory, there is a hash so possibly this is a bug inyarn2nix
that it did not detect failure.But the weird thing is that every sandboxed build seems to fail in the same way. Even if I switch to a different commit that does not have the same
yarn.lock
so this is not just non-deterministic failure that got cached (plus that would likely get revealed bynix-build --check
, which it did not).I managed to simplify this to a lockfile with a single package:
f1fcab1e8d/yarn2nix-incomprehensible-error
Turns out the hash fragment of the
resolved
URL is thesha1
hash of the tarball and newer versions of Yarn no longer include it according to https://github.com/NixOS/nixpkgs/pull/119522. Sorry for the noise.Very interesting.
I don't know much about NixOS but I may have an idea of the problems origin:
The
browserslist:update
command is responsible to update the compatability tables for browserfeatures which is e.g. used for Autoprefixer.Maybe the issue is not the linked commit but instead the added entry to the drone.yml:
ed6dc94873
It really is just that
yarn2nix
does not likeresolved "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001265.tgz"
line because it no longer contains#sha1
. But that is problem with yarn2nix and needs to be fixed there. https://github.com/NixOS/nixpkgs/pull/119522 should do that.