summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch
diff options
context:
space:
mode:
authorr-vdp <ramses@well-founded.dev>2025-02-17 12:06:27 +0100
committerr-vdp <ramses@well-founded.dev>2025-02-17 12:06:27 +0100
commit7a56ddaf9d42e9aee8ddbf2d95f9ea82502d094c (patch)
tree068070f62b9e9485c8670b6126f29dc3b74cb700 /pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch
parent4cf8a147ddd24796ce31b149d446284cbbb55dbe (diff)
switch-to-configuration-ng: don't block when the lockfile is already locked
When the lockfile is already locked, stc-ng currently blocks without any message indicating what is going on. This is very confusing to users, especially because most will not know about the lockfile. Since the current call blocks, we actually never end up in the else branch. Switching to a non-blocking call, makes sure that we print out an error and exit in case the lockfile is already locked by another process, which makes it a lot clearer what's going on and gives the user a clue as to what to do to unblock the situation.
Diffstat (limited to 'pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch')
0 files changed, 0 insertions, 0 deletions