fix(auth): remove duplicate fit-anisotropy route policy registration#30098
Merged
Conversation
The endpoint memory/v2/fit-anisotropy:POST was registered twice in ACTOR_ENDPOINTS. Since registerPolicy uses policyRegistry.set(), the second call silently overwrote the first, making one entry dead code. Follow-up to #29626 review feedback from Devin.
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
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.
Follow-up to review feedback on #29626.
Devin flagged that
memory/v2/fit-anisotropy:POSTwas registered twice inACTOR_ENDPOINTS— once before and once after the newconcept-frequencyentry. SinceregisterPolicyusespolicyRegistry.set(), the duplicate silently overwrote the first registration. Removed the duplicate.