refactor: remove obsolete ovni-based TraCR instrumentation hooks - #1
Draft
noabauma wants to merge 1 commit into
Draft
refactor: remove obsolete ovni-based TraCR instrumentation hooks#1noabauma wants to merge 1 commit into
noabauma wants to merge 1 commit into
Conversation
The new TraCR no longer uses ovni as a backend, and TaskR now records these state transitions itself via its task/worker callbacks (which fire at the exact same points). The nOS-V marks relied on nOS-V owning the ovni process, which no longer applies. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
noabauma
marked this pull request as draft
August 28, 2026 14:31
Collaborator
Author
|
Still an idea, but it will let nosv being unable to tracr again... |
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.
The new TraCR no longer uses ovni as a backend, and TaskR now records these state transitions itself via its task/worker callbacks (which fire at the exact same points). The nOS-V marks relied on nOS-V owning the ovni process, which no longer applies.
Description
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Type of change
What type of changes does your code introduce to HiCR? Put an
xin the box that apply.CHANGE(fix or feature that would cause existing functionality to not work as expected)FEATURE(non-breaking change which adds functionality)BUGFIX(non-breaking change which fixes an issue)ENHANCEMENT(non-breaking change which improves existing functionality)NONE(if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)Verification
Please check the testing guidelines for recommendations about automated tests.