Conversation
b-long
force-pushed
the
fix/remove-nanotdf
branch
from
September 15, 2026 02:34
42e0dc1 to
4d0dbe9
Compare
Owner
Author
|
@arkavo-com I'm wondering if you can weigh in (early) on this PR. It's not exactly "Ready for review", but I'm wondering if you can shed some light. I'm not exactly sure what's going on with NanoTDF, but based on some testing I've done trying to upgrade to a newer platform for integration testing (see #182 ) all of my NanoTDF tests have been breaking. My understanding is that I need to remove it, in order to upgrade. But, it seems like maybe it's being added back into OpenTDF, so maybe I should just mark tests as skipped? |
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
1 participant
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.
Closes: #186
Relates-to: #182