This repository was archived by the owner on Nov 24, 2025. It is now read-only.
Revert Traffic Monitor renaming to rascal #7190
Merged
Conversation
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
Member
ocket8888
reviewed
Nov 14, 2022
Contributor
ocket8888
left a comment
There was a problem hiding this comment.
This does indeed seem to revert the specified changes. But I don't think it's recorded anywhere: can you explain why this is necessary? Otherwise it seems like a step backwards to anyone not in the know.
3 tasks
… prefix (apache#7175)" This reverts commit 3721d91.
5cc217c to
9e9bec1
Compare
ocket8888
approved these changes
Nov 16, 2022
4 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
We need to roll back Rascal changes until we can identify all the tools that expect Traffic Monitor to be Rascal. Users may have tools used internally that hard-code
RASCALwhich need to first change before these changes can be merged. So before changing it, we need to have a discussion on the mailing list to ensure everyone's okay with it.Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Run integration, unit test.
Ensure CIAB build correctly
TO API endpoints work as expected.
Clients (eg: T3C) work as expected.
If this is a bugfix, which Traffic Control versions contained the bug?
PR submission checklist