mirror of
https://github.com/ElementsProject/lightning.git
synced 2024-11-20 10:39:49 +01:00
cdb93eefec
On my machine it should have produced: /tmp/ltests-1p0v5z1j/.locks/lock-1631090663.1066182 but instead it produced: /private/tmp/ltests-1p0v5z1j/.locks/lock-1631090663.105848 The mismatch resulted in a hang inside flock. Path .resolve() seems to be causing problems for others as well. It appears the library was not meant to handle complex path situations and isn't maintained as such (see link reference). Since we have already built a full path here anyway, the call to .resolve() appears redundant. Tested on python 3.9.6 on my Mac OS X 11.4 (20F71), Xcode 12.5.1 (12E507) Relevant discussion: https://discuss.python.org/t/pathlib-absolute-vs-resolve/2573 |
||
|---|---|---|
| .. | ||
| init | ||
| keys | ||
| libhsmd_python | ||
| plugins | ||
| pylightning | ||
| pyln-client | ||
| pyln-proto | ||
| pyln-spec | ||
| pyln-testing | ||
| reprobuild | ||
| sanitizer_suppressions | ||
| bootstrap-node.sh | ||
| Dockerfile.builder | ||
| Dockerfile.builder.fedora | ||
| Dockerfile.tester | ||
| lightning-cli.bash-completion | ||
| linuxarm32v7.Dockerfile | ||
| linuxarm64v8.Dockerfile | ||
| short_channel_id-to-txid.sh | ||
| startup_regtest.sh | ||