You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Process substitution FIFO of a background job that still runs at shell exit stays in /tmp #245
Follow-up from #242 (owner ruling AD2, 2026-11-19).
What happens
cmd <(x) & makes a FIFO under /tmp (vsh-fifo-<shell pid>-*). Since #242, the job table keeps the substitution until the job ends. A SIGCHLD flag and polling at safe points then reap the job, release the substitution and remove the FIFO. At exit, the shell cleans the jobs that have ended.
One case is left: if a background job still runs when the shell exits, the shell does not remove its FIFO. It leaves the substitution to the job on purpose (ProcessSubstitution::leave_running), because the job may still open the FIFO. The job still gets its input, but the FIFO file stays in /tmp after the job ends. If the job never opens the FIFO, the substitution's child also stays blocked.
#242 - fix(glob): bound expansion while it runs; stop ** following symlinks [open]
📝 Issue Planner
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
One more case belongs here, since 3e53e52. A background job can end while its connected substitution still works, for example sh -c 'printf data > "$1"' sh >(sh -c 'sleep 5; cat > out') &. The shell no longer waits for that substitution: it checks it at each safe point. If the shell exits first, the substitution is left to finish, and its FIFO stays in /tmp, as for a job that still runs. The same options apply.
Activity
coderabbitai commentedon Nov 19, 2026
🔗 Related PRs
#242 - fix(glob): bound expansion while it runs; stop ** following symlinks [open]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
hyperpolymath commentedon Nov 19, 2026
One more case belongs here, since 3e53e52. A background job can end while its connected substitution still works, for example
sh -c 'printf data > "$1"' sh >(sh -c 'sleep 5; cat > out') &. The shell no longer waits for that substitution: it checks it at each safe point. If the shell exits first, the substitution is left to finish, and its FIFO stays in/tmp, as for a job that still runs. The same options apply.Generated by Claude Code