neume-network / neume-network/core
when defining `extractor` as `extraction` in crawlpath object, process just quits without errors
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
- A statement like this will just stop the process after a short while without throwing any noticeable error message
- we want the program to clearly indicate that something is very wrong
{
name: "call-block-logs",
extraction: {
args: [],
},
}
Contributor guide
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 reproducing the issue with the provided crawlpath object, changing extractor to extraction as shown. Trace where crawlpath objects are processed and identify why this malformed definition exits without a visible error; done means the same input reports a clear error instead of silently stopping.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100