-
Notifications
You must be signed in to change notification settings - Fork 79
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
TypeError in ScalerCH.select_channels(None) #714
Comments
waiting on bluesky/ophyd#714
Example local workaround until the new tag. |
Thanks for sharing the workaround. We could at least tag a beta this week. @klauer Are there still known problems with signals / callback-processing in |
Yes, this needs resolving: #708 We're looking to a new pyepics release soon, but there is not yet a fix designed for this issue. It likely will cause issues with PV reusage during a session. As far as I am aware, the refactor has not been extensively tested outside of CI. |
Ah, when I did the backports I looked at merged PRs, it looks like that commit got pushed directly to master so I missed it. As @klauer points out master currently needs a bit more work before it can be tagged (and has some pretty big improvements (but given the rules of un-intended consequences means will also break something 😞 ) ). Unless someone protests I'll cherry-pick that commit back to 1.3.x and tag 1.3.3 this afternoon? |
That's a good plan, @tacaswell. |
Done and released on PyPI. Conda packages in progress. |
Thanks! Conda package coming or I switch to pip on this as proof-of-fix? |
I'm blind. |
New conda packages are available at https://anaconda.org/lightsource2-tag/ophyd/files. |
Seems that the code committed as part of #692 did not make it into tag 1.3.2, thus my local code expecting this fix fails like this:
The fix does exist in the master branch now. Can a new tag be made in the next week?
The text was updated successfully, but these errors were encountered: