Repository navigation
docs(site): correct the claims about channels, sizes and RunAsDate - #106
Merged
Merged
Conversation
The link preview still said 36 time channels and "no install". The home page showed a fixed "26 of" in its session illustration. Three pages promised that --scale-duration scales object waits, which the hook only counts. The audit page put the high-resolution counter in the observed bucket of every session, while it is not hooked at all without --scale-qpc, and two pages listed the exit codes without 6, 7 and 8. The sample reports predated the call totals in the report header. The comparison with RunAsDate said it can neither freeze nor jump. Its own documentation (version 1.41) shows a clock that holds still unless "Move the time forward according to the real time" is on, and a return to the real time after a set number of seconds. The page also left out two things RunAsDate does and this tool does not: attaching to a running process, and several applications at different dates at once. The download sizes on every page were those of an older release. - chrono_ctl: ChannelCategory::observed(), the one list of the observed bucket, used by the mechanism and by the website. - Site generator: substituted_count and observed_count counted from CHANNELS, download sizes kept once in site.json and written with each language's decimal mark, a refusal of a size that is not a plain number, and a test that holds social-preview.svg to CHANNEL_COUNT. - Pages: the corrections above in all 22 languages, and the audit page's sample report regenerated from the current build. - README: package sizes and the date of the last suite run. Reversal probes: the preview test failed on the old 36, and the size test failed on the Polish download page with the decimal mark taken out of the render. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important Review skippedToo many files! This PR contains 249 files, which is 149 over the limit of 100. To get a review, reduce the PR to 100 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configuration
⛔ Files ignored due to path filters: 2
📒 Files selected for processing: 249
You can disable this status message by setting the
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Summary
The website, the README and the link-preview picture had fallen behind the program. This corrects every claim that was no longer true and moves the numbers that drifted into places that cannot drift again.
What was wrong
.msi). The home page's session illustration showed a fixed "26 of 44". A default session hooks 21 channels and its report lists 16, so no single number is true for every session.--scale-durationdoes. Three pages said it puts object waits on the session clock. The hook counts them and leaves their timeout as it was.--scale-qpcit is not hooked at all.What changed
chrono_ctl::ChannelCategory::observed(): the one list of the observed bucket. The mechanism now uses it, and so does the website.substituted_count(30) andobserved_count(14) tokens counted fromCHANNELS.site.json, written with each language's decimal mark (decimal_separatorin every dictionary, validated).social-preview.svgtoCHANNEL_COUNT.Verification
cargo test:chrono-site: 23 unit tests (was 20) and 20 integration tests (was 18).chrono-ctlandchrono-mech: all green.chrono-clihygiene and names guards: green.clippy -D warningsis clean on the three changed crates.chrono-site --strictbuilds 353 pages in 22 languages, with no unresolved token.--scale-duration: 28 substituted, 11 observed,Left out on purpose
🤖 Generated with Claude Code