Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

count plan does not run without arbitrarily setting the path provider #784

Open
callumforrester opened this issue Jan 16, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@callumforrester
Copy link
Contributor

Even if I have no ophyd-async detectors I have to arbitrarily set the global path provider in my startup file otherwise the count plan fails.

Steps To Reproduce

Steps to reproduce the behavior:

  1. Go to Add fake PathProvider to startup module #783
  2. Comment out the temporary fix in the example startup file
  3. Run the system tests (tox -e system-test)

Acceptance Criteria

  • I do not need a path provider if I have no ophyd-async devices

Also related to #404

@callumforrester callumforrester added the bug Something isn't working label Jan 16, 2025
callumforrester added a commit that referenced this issue Feb 3, 2025
This is a workaround (not a fix) for #784, so won't close it. The
replacement of `PathProvider` in dodal will eventually provide the
proper fix. For now I think we should just pretend to write to a
directory with our start-up file, despite the fact that none of the
simulated detectors actually write files.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant