summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorDavHau <hsngrmpf+github@gmail.com>2025-01-02 17:50:44 +0700
committerJörg Thalheim <joerg@thalheim.io>2025-01-05 14:36:05 +0100
commitd7d59e137cdd8307caa4fb7d0a687fc3f88191b6 (patch)
treeb5b3e3472357618a634f48903e70dbdcc1731df0 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent45b4efbacf84af2ebff0bc5da22f1194a3575e82 (diff)
breakpointHook: re-implement using nsenter
breakpointHook is amazing and has been a daily driver for me. Though it has been buggy several times in the past and recently it stopped working on my system, as the approach using cntr seems to be a bit sensitive to the environment and which shell is used etc. After speaking with @mic92, it turned out there is an alternative approach using `nsenter`. After playing with that for a while, I think we should replace the current implementation of breakpointHook. The new output when a build fails will look like this: ``` build failed in configurePhase with exit code 1 To attach, run the following command: sudo /nix/store/2kzihv08w9vsyi6zhs0pi2i9117v4q1v-attach/bin/attach 28715971284 ``` Benefits of the new implementation over the old one: - no need to install cntr tool on the local machine first, the copy pasted command will just work - no need to execute `cntr exec ...` manually to enter the namespace - interactive shell by default - dropped into correct working directory by default - $out available by default - possibility to override the shell with zfs or fish, etc. by defining `debugShell` in the derivation to debug - probably less prone to bugs as it only uses nsenter cc @mic92
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions