SpikeInterface / SpikeInterface/spikeinterface
Need to save analyzer extension's run_info before run starts (bug from #3347?)
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
@ alejoe91, can you explain why this call to
self._save_run_info()line got deleted? I think it's important to have it saved before the run starts, otherwise if the run crashes there is no run_info present to be loaded.
Originally posted by @jonahpearl in ff07ac6
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 analyzer extension implementation and the self._save_run_info() call referenced in the issue, then compare it with commit ff07ac6. Verify that run_info is saved before execution begins and remains available when a run crashes; the payload names no test file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100