serialised integer is too large for type #831
Labels
No labels
Affects/CppNix
Affects/Nightly
Affects/Only nightly
Affects/Stable
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/lix ci
Area/nix-eval-jobs
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/repl/debugger
Area/store
bug
Context
contributors
Context
drive-by
Context
maintainers
Context
RFD
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Language/Bash
Language/C++
Language/NixLang
Language/Python
Language/Rust
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
Topic/Large Scale Installations
ux
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#831
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Describe the bug
I can't quite say when it's been starting (I'd guess a month or two), but recently I've been getting a large number of these errors:
full error
and a snippet from the even more verbose version
Where 7ak8cya3ryxn7wyv20pbpxvyrrx0ij7y-python3-3.11.12-env.drv looks like a normal derivation to me.
To be sure I checked the internal-json log format and while that one mentions an "id", it is a different one than the reported "j", and
grep -Eo '[0-9]+' | jq -s max
on the .drv file gives 56118121 which is far off.Steps To Reproduce
The problem is that I can consistently reproduce it whenever it happens (i.e. Arrow Up, Enter), but since it depends on the ssh transport and only happens sometimes with a seemingly random derivation.
Not sure if anyone can reproduce this with the
Expected behavior
Either a more usable error message (if there is an identifiable underlying problem) or "it should just work".
nix --version
outputLix
885dde9c3d
Additional context
The only reference (that isn't the upstream bug which doesn't apply to me) I can find to this is a Discourse thread.
To be clear, this is not breaking for me due to my infra, so I don't depend on this, and I'm fine with it being lowest prio given that I seem to be one of three people who had this issue.
duplicate of #830