flake update json parse coredump when gitlab api coudn't be fetched #642
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
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#642
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 tried to run
nix flake update
ind15f0b6265
with a bad network connection. lix fails to connect to the GitLab (one of the inputs) and then crashes as the GitLab API "result" is empty.Steps To Reproduce
nix flake update
Expected behavior
It shouldn't crash ;)
nix --version
outputAdditional context
coredump: https://cloud.leona.is/s/2sSbDbGMoGfYKMM
@lheckemann i think you know more about the gitlab code or who to ping
This doesn't happen with
(which does result in a DNS resolution failure as suggested); is there any reliable way to reproduce this?
maybe you need a name that resolves but doesn't reply? idk. maybe try localhost, assuming you don't have a web server running? or it might have to actually fully time out, so you'd need a black hole; could make one of those with iptables i guess.
flake.lock
triggersstd::terminate
due to unhandled json parsing exception #661This issue was mentioned on Gerrit on the following CLs: