tscircuit / tscircuit/schematic-trace-solver
JSON Bug Report:
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 314
- Avg merge
- 9h 3m
- Merged PRs (30d)
- 132
Description
Solver input JSON attachment
_board#647 _-SchematicTracePipelineSolver-solver-input.json
Notes
No response
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Begin by downloading and inspecting the attached solver-input JSON to identify the reported case and determine how it reproduces in the schematic trace solver. No source file, test, or expected-versus-actual behavior is specified, so first document the failure and locate the relevant solver entry point. Done means the input is handled correctly and a regression check covers the discovered behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100