pcdshub / pcdshub/hutch-python
BestEffortCallback explodes when our devices aren't hinted properly
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 18
- Avg merge
- 7d 9h
- Merged PRs (30d)
- 1
Description
Expected Behavior
No explosions
Current Behavior
Explosions for some of our sim devices without hints configured
Possible Solution
- Go through and hint things properly
- Look into an alternate BEC that doesn't explode
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 locating the BestEffortCallback entry point and the configuration for simulated devices without hints. Reproduce the failure, determine whether device hints or an alternate callback is the intended direction, and verify that those devices no longer cause explosions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100