INCATools / INCATools/dosdp-tools
Debugging: catch exceptions and name pattern when in batch mode
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 33
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Currently when dealing with dozens or hundreds of patterns, its impossible to figure out which pattern causes the issue when something fails, for example like this:
The only thing I can do is binary search (deleting patterns until I find the one causing the issue), but that costs a lot of time. Can we, in batch mode, catch any exceptions and inform the user which pattern is at fault?
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 locating the batch-mode entry point and the code that processes each pattern. Trace how failures are currently reported, then verify that a failing batch identifies the pattern responsible and that other error details remain available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100