Merged
Conversation
Addresses qupath#1974
Member
Author
|
I've merged qupath/qupath-extension-instanseg#172 so once we make a new InstanSeg extension release then we can merge this too. We may as well merge qupath/qupath-extension-instanseg#168 first though @alanocallaghan |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses #1974
Not ready to be merged yet: I find it does enable the use of PyTorch 2.7.1 (good!) but breaks the InstanSeg extension (bad!).
Reason seems... surprising.
We make calls to
baseManager.debugDump(2). This attempts to create a substring of a UUID, which would be ok except that UUIDs aren't used any more.The result is
We should be able to work around it by avoiding any use of
debugDump- I've checked that removing this line means that InstanSeg can run. But I suspect this must affect others.