Conversation
What was broken QA Challenge winners could rerate into the public Data Science Challenge bucket and update the member's main rating, but winner-only QA challenge cards could still be absent from profile stats history when no persisted history row was available. Root cause (if identifiable) The previous fix mapped QA Challenge rows for rating replay, but the stats history fallback still resolved challenge-backed history rows from the source challenge track. QA source rows therefore resolved to a Quality Assurance track, which is not one of the public history groups exposed by member-api. What was changed Normalized QA Challenge source rows to the public DATA_SCIENCE / Challenge dimension in the shared stats dimension resolver used by review-result and ChallengeWinner history fallbacks. Any added/updated tests Added StatisticsService coverage showing a winner-only QA Challenge is returned under DATA_SCIENCE.Challenge history when the member has the Data Science Challenge aggregate but no persisted history row.
PM-5223: show QA winner history under Data Science
What was broken QA Challenge rows were being replayed and displayed under DATA_SCIENCE / Challenge, so profile history showed QA wins in the Data Science Challenge section instead of the Testing section. Root cause (if identifiable) The previous follow-up normalized Quality Assurance Challenge rows into the Data Science Challenge bucket for both rerating and history fallback. That made the rating update visible, but it used the wrong public profile bucket for QA challenges. What was changed Routed Quality Assurance Challenge rerates to DEVELOP / BUG_HUNT, the legacy testing subtrack used by the profiles app for Testing. Data Science Challenge rerates now replay only Data Science source challenges. History reads also remap persisted QA Challenge rows out of DATA_SCIENCE / Challenge and into DEVELOP / BUG_HUNT when challenge metadata identifies the source as Quality Assurance. The member stats recalculation helper applies the same QA dimension normalization for future backfills. Any added/updated tests Updated Development rating engine and StatisticsService coverage for QA Challenge winners under Testing. Added StatisticsService coverage for remapping previously persisted Data Science QA history rows into Testing. Added recalculation coverage for QA aggregate normalization into the Testing bucket.
PM-5223: route QA challenge stats to Testing
What was broken QA Challenge ratings and history were previously being forced into existing public buckets instead of using a QA stats dimension. The latest QA feedback asked for the QA track/type to be supported directly instead of using DEVELOP. Root cause The stats dimension resolver and unified stats response helpers did not treat QA as a supported canonical track, so follow-up fixes mapped Quality Assurance Challenge rows to DATA_SCIENCE or DEVELOP-based buckets. What was changed Added QA as a canonical stats track, routed Quality Assurance Challenge rerates and history normalization to QA / Challenge, exposed QA in unified stats/history/search responses, and updated the recalculation path to normalize QA Challenge aggregates to QA / Challenge. Any added/updated tests Updated rerating and history tests to expect QA / Challenge, added recalculate coverage for QA Challenge aggregates, and added formatter coverage for QA stats and QA history responses.
PM-5223: route QA challenge ratings to QA
What was broken AI Engineering stats could show challenge counts, but the profile challenge details view could still be empty because the member stats history response did not expose those rows under the configured AI Engineering rating path. Root cause When history rows were enriched with Challenge API metadata, configured rating-path rows kept their challenge id and name but had their stored track/type overwritten by the source challenge's native Challenge or Marathon Match dimensions. What was changed Preserve configured rating-path dimensions during history metadata enrichment so AI Engineering history remains under DATA_SCIENCE.AI Engineering while still receiving canonical challenge metadata. Any added/updated tests Added a StatisticsService regression test that verifies an AI Engineering rating-path history row stays under DATA_SCIENCE.AI Engineering after challenge metadata enrichment.
PM-5397: Preserve AI Engineering history dimensions
Stats update for AI ratings'
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.
https://topcoder.atlassian.net/browse/PM-5223