Process supervision follow-ups: `resource rebind` as a new command, cascade, exit codes over 128, spawn's exit code on a crash
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Start with issues #288, #261, and #262, which frame these follow-up questions. The issue names the supervisor shell wrapper and the spawn readiness wait, but does not identify source files or tests; first locate those entry points and inspect how resource binding and status are handled. Done means the maintainers resolve the listed design questions and the chosen behavior is implemented and covered by tests.
Written by the indexing model from the issue text.
Description
Open questions from #288 (for #261 and #262):
- New command:
newgit resource rebind <res> [instance]. Nothing could bind a failed resource again short ofremoveand a respawn, so #262's retry hint had nothing honest to point at.rebindbinds the resource again asspawndoes (ports, exports, render, prepare, autostart) and refuses while its process runs. Is a new command the right surface, or should this benewgit startretrying failed binds, ortracker use-style re-binding? rebinddoesn't cascade. Rebinding a resource doesn't rebind the resources that depend on it, so if its exports change, theirs go stale. Rebind dependents too, or at least list them?- Exit codes above 128 are read as signals. The supervisor wrapper is
sh, so a program that deliberately exits 137 shows askilled(SIGKILL). That's unavoidable with a shell wrapper; a small in-process supervisor would fix it. Worth it? spawnexits 0 when an autostarted process dies during the readiness wait. It printsnot ready, consistent with other readiness problems today. Should a crash at spawn be a non-zero exit, given agents read the exit code?- Status wording.
exited(1)/killed(SIGKILL)followblocked(deps); the issue proposedexited (1). Minor, but status is what agents parse.
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- Avg merge
- 7h 20m
- Merged PRs (30d)
- 80
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Spheroman/newgit
-
Port allocation order within a resource is unspecifiedPossibly taken A pull request linked to this issue is open or already merged. Opendocumentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Spheroman/newgit#59 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Symlinks: a render writes through a link, a check-then-use race, and a bad link blocking checkoutOpen
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
All issues in Spheroman/newgit
Similar issues
-
bug priority: low ui
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
storytold/photocraft#10370 · 1 comment ·
Maintainers usually reply within 1 day
-
area:doc bug in progress needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bherbruck/solvecraft#9634 · 2 comments · 1 reaction ·
-
inflate: total_in uses plain += on c_ulong (32-bit on Windows), panics in debug for streams > 4 GiBOpen
Difficulty 1/5 Under an hour Newbie friendliness 85/100
trifectatechfoundation/zlib-rs#570 · 1 comment ·
-
bug discord-triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
LanternOps/breeze#10755 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
aranya-project/aranya#803 ·