Repository navigation
Correct live WCL Buffs target-filter verification - #72
Merged
Merged
Conversation
Co-Authored-By: OpenAI Codex <noreply@openai.com>
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.
The new live target-filter journey assumed that Buffs
--target-idselects the raw event recipient. Warcraft Logs applies that filter to the aura caster, whose ID issourceIDin the raw event. Once public authentication was restored, the journey rejected correct upstream results.Derive the caster from the complete baseline and compare the filtered stream against its exact source-ID subset. Keep full event equality, pagination, duplicate events, and a strict nonempty subset. Clarify the Buffs event scope in the consumer documentation.
Validation:
auth_failed; user-account/private-report verification remains blocked. No credentials or token state are changed by this PR.