Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

A render failure is hidden from `spawn`/`status` output, and the retry hint names a nonexistent `prepare`

Open Beginner friendly
  • Is something wrong?
#262 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
cli

Research direction

Start by locating the human output paths for spawn and status, then compare them with the spawn --json output where render_error appears. Check how the retry hint is chosen and whether the resource defines the suggested action. Done when human output shows render and export errors and render or export failures suggest fixing the file or definition and re-binding.

Written by the indexing model from the issue text.

Description

When a resource fails to bind because of a render error, the human output of spawn and status never says why, and the retry hint names an action the resource doesn't have.

Repro

Any render whose find no longer matches count times, e.g. after the capture-reversal bug (#260):

$ newgit spawn rev2
Spawned branch instance `rev2` — but `web` did not come up (see below)
spawned with failures: 1 of 2 resources did not bind.

$ newgit status rev2
`rev2` is not ready:
  - `web` failed — retry with `newgit action web.prepare`; its logs are under .newgit/logs/rev2

$ newgit action web.prepare rev2
Error: resource `web` has no action named `prepare`

$ ls .newgit/logs/rev2
deps.key-….log                 # nothing for web

The "(see below)" in the spawn output has nothing below it. The reason exists, but only in spawn --json:

"render_error": "resource `web` renders into `.env.local`, but `127.0.0.1:8000` occurs 2 time(s) there, not 1; …"
Expected
  • Print render_error (and export_error) in the human output of spawn and status. They're already good messages.
  • Base the retry hint on the failure: a render or export failure should point at fixing the file or definition and re-binding, not at prepare. Never suggest an action the resource doesn't define.

Environment: newgit 0.7.0 (06fc371005bc), macOS (Darwin 27.0.0), APFS, git 2.55.0. Minimal scratch project: one secret tracker env owning .env.local, a deps install (hash/recompute), and a web process (python3 -m http.server $WEB_PORT, autostart) with a [[render]] into app.conf.

Dominant language
Rust
Stars
0
Forks
0
Avg merge
4h 56m
Merged PRs (30d)
51

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Spheroman/newgit

All issues in Spheroman/newgit

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.