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.

Sign up for GitHub

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

Jump to bottom

Re-apply patch to alternative v0.23 #3

Closed
dmitrisvetlov opened this issue Sep 29, 2024 · 0 comments · Fixed by #4
Closed

Re-apply patch to alternative v0.23 #3

dmitrisvetlov opened this issue Sep 29, 2024 · 0 comments · Fixed by #4
Assignees
@dmitrisvetlov
Labels
bug Something isn't working

Comments

@dmitrisvetlov
Copy link
Contributor

Troubleshooting of additional bugs in other repositories revealed that multiple versions of pycromanager carry the 0.23.0 version number, and the one I selected from the commit history was not the one that was actually pushed to PyPI, nor the one used in our repository for controlling our Terminator microscope. Therefore, in this issue, the latter code will be copied verbatim to this repository and the fix made in #1 reapplied.
@dmitrisvetlov dmitrisvetlov added the bug Something isn't working label Sep 29, 2024
@dmitrisvetlov dmitrisvetlov self-assigned this Sep 29, 2024
@dmitrisvetlov dmitrisvetlov mentioned this issue Sep 29, 2024
Merged
@dmitrisvetlov dmitrisvetlov linked a pull request Sep 29, 2024 that will close this issue
3 Re-apply patch to alternative v0.23 #4
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dmitrisvetlov dmitrisvetlov

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

3 Re-apply patch to alternative v0.23 MunskyGroup/pycro-manager-munsky
1 participant
@dmitrisvetlov