cortex-lab / cortex-lab/phy

Error when executing action next

Open
#1,074 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area: performance status: needs-info type: bug
Dominant language
Python
Stars
430
Forks
187
Avg merge
2h 31m
Merged PRs (30d)
2

Description

System:
Ubuntu 20.04
dataset on a SATA-connected 4TB SSD
nvidia quadro GPU
32GB RAM

Steps to reproduce the problem:
Open phy2, select a unit, hit space

Full error log:

18:22:47.249 [E] qt:178               Timeout in _block().
18:23:24.407 [W] actions:213          Error when executing action Next.
18:23:24.509 [D] actions:214          Traceback (most recent call last):
  File "/home/maxime/anaconda3/envs/phy2/lib/python3.7/site-packages/phy/gui/actions.py", line 211, in wrapped
    return callback(*args)
  File "/home/maxime/anaconda3/envs/phy2/lib/python3.7/site-packages/phylib/utils/event.py", line 141, in emit
    res.append(f(sender, *args, **kwargs))
  File "/home/maxime/anaconda3/envs/phy2/lib/python3.7/site-packages/phy/cluster/supervisor.py", line 847, in _on_action
    _block(lambda: not self._is_busy)
  File "/home/maxime/anaconda3/envs/phy2/lib/python3.7/site-packages/phy/gui/qt.py", line 182, in _block
    raise RuntimeError("Timeout in _block().")
RuntimeError: Timeout in _block().

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure in phy2 by selecting a unit and pressing Space, then inspect phy/cluster/supervisor.py around _on_action, phy/gui/qt.py around _block, and phy/gui/actions.py around the reported wrapper. Trace why the action remains busy until _block() times out; done means the Next action no longer raises the reported RuntimeError under the stated setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.