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#1696 _-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
Start by downloading and inspecting the attached solver-input JSON, then determine how the reported case reaches the schematic trace solver. Reproduce the failure using the repository's available entry point or tests. Done means the attached case is handled correctly and a regression check covers the identified 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
- 20/100