Dear team,
We're hitting segfaults when running pyisyntax on a shared Linux server. The cause is that the bundled libisyntax uses sem_open() with fixed global names (/worksem, /completionsem, /benaphore), which creates files under /dev/shm/. If a process gets killed, these files persist and cause other users to crash on their next run.
This was fixed upstream in amspath/libisyntax, which switches to sem_init() on Linux. But pyisyntax 0.1.6 still seems to have the submodule pinned to an older commit.
Could you update the submodule and publish a new release?
Thanks!
Dear team,
We're hitting segfaults when running pyisyntax on a shared Linux server. The cause is that the bundled libisyntax uses sem_open() with fixed global names (/worksem, /completionsem, /benaphore), which creates files under /dev/shm/. If a process gets killed, these files persist and cause other users to crash on their next run.
This was fixed upstream in amspath/libisyntax, which switches to sem_init() on Linux. But pyisyntax 0.1.6 still seems to have the submodule pinned to an older commit.
Could you update the submodule and publish a new release?
Thanks!