chore(scripts): report what the language backfill would actually write - #252
Merged
Conversation
The dry run said how many posts it would label but not into what, which is the one question a dry run exists to answer. Running it against production made that concrete: "1367 labelled" looks fine, and would have hidden either a healthy corpus or a detector quietly filing every Turkish post under English. It now tallies per language and samples per bucket rather than in scan order. Scan order is by id, which in practice is a run of news bots all writing the same language, so a flat sample of the first twenty says nothing about what is further down. Posts the detector declines to call are sampled too. That bucket is where a language it cannot handle would silently pile up, and a bare count would never say so - reading it is what confirmed the 229 unlabelled posts are link-only bot release notes rather than missed Turkish. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LP54iXPnpBLkTfg2te3hcn
|
🎉 This PR is included in version 1.14.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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 dry run said how many posts it would label but not into what, which is the one question a dry run exists to answer. Running it against production made that concrete: "1367 labelled" looks fine, and would have hidden either a healthy corpus or a detector quietly filing every Turkish post under English.
It now tallies per language and samples per bucket rather than in scan order. Scan order is by id, which in practice is a run of news bots all writing the same language, so a flat sample of the first twenty says nothing about what is further down.
Posts the detector declines to call are sampled too. That bucket is where a language it cannot handle would silently pile up, and a bare count would never say so - reading it is what confirmed the 229 unlabelled posts are link-only bot release notes rather than missed Turkish.
Claude-Session: https://claude.ai/code/session_01LP54iXPnpBLkTfg2te3hcn
What does this PR do?
A brief description of the changes introduced.
Closes #
Type of Change
Checklist
feature/,fix/,chore/,docs/)