Feature Request: Different error messages for SciUnit/NeuronUnit vs SciDash/Geppetto errors.
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
I would like to be able to quickly tell if the error is in my code or the site's. If the exception is raised inside of SciUnit or NeuronUnit, can we color the error message that gets printed on the site blue instead of red? Then I know what I should be debugging myself vs. handing off to you.
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
No files or tests are named. Start by locating the site's error rendering and the exception-handling entry point for SciUnit, NeuronUnit, SciDash, and Geppetto; done means exceptions from SciUnit or NeuronUnit are visibly blue while site errors remain red.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100