docs(activation): clarify temperature conversion - #2204
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
Important Review skippedReview was skipped as selected files did not have any reviewable changes. ⚙️ Run configurationConfiguration used: Repository: ooples/AiDotNet/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe pull request updates the ChangesGumbel-Softmax Comment Update
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Other Merge Risk: ⚪ Minimal · up to This comment-only update introduces no identified production or CI-routing risk. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. A comment shifts its place Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
|
Live production selection proof: https://github.com/ooples/AiDotNet/actions/runs/34919695471/job/104225032304 passed. At 02:05:01 UTC it accepted master-certified map run 34919418484; at 02:06:23 UTC it selected 2 of 116 shards. No proof-branch map override is present. Build/test completion and post-merge validation reuse remain pending; selection alone is not passing test evidence. |
|
Live merge-reuse evidence: isolated PR #2206 merged the identical head/tree using unchanged production workflows and normal master map trust. Run https://github.com/ooples/AiDotNet/actions/runs/34964852374 resolver accepted source run 34919695471, reuse_scope=Validation, execute_validation=false, reused_requires_validation=true. GitHub skipped shard selection, both builds, the test matrix, parameter sweeps, and model-shape conformance. Baseline publication and CodeQL/Sonar remain enabled because the source has a Validation certificate, not Complete. Source Integration A-B and Integration D both passed. This proves live suppression of duplicate validation on a real isolated branch merge; #2204 itself remains unmerged on master due to the Sonar runner failure. Retrying only Sonar and dependents, not the tests. Final quality/baseline outcomes pending. |
These write-ups should never have been committed. Removed here so the file does not arrive on master when this PR merges; .gitignore gains matching rules in #2224. Deliberately untouched: ci-proof/nonruntime-routing-canary.md, which is functional rather than a write-up (it exercises the permanent ci-proof/** workflow trigger). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GYQycGHKxLFBqhEtPMHz29
PR #2223 changed one file - website/package-lock.json - and ran all 164 shards. website/ is the documentation site: on master it holds zero .cs and zero .csproj files, appears nowhere in AiDotNet.sln, and its pipelines are already listed as independent non-runtime workflows. The classifier had no entry for it, so the path fell through to MapCandidate, found no coverage, and escalated. NonRuntimeDirectories is an allowlist, checked after shared infrastructure so a build file keeps its meaning wherever it sits, and before the markdown and map-candidate rules so a non-product tree is spared whatever its extension. Assert-NonRuntimeDirectories is the trip-wire. The entry is trusted because the tree contains nothing the solution compiles, which is a fact about today rather than a law, and the cost of it quietly ceasing to be true is tests skipped on a change that needed them. It is re-checked on every self-test run instead of being remembered. The self-test now pins classification to four real pull requests rather than to a synthetic map, because every failure this feature has shipped was a classification failure and none of them were visible from the synthetic one: #1889 which ran 1 shard, #2223 which ran 164, #2204 which ran 49 and #2098 which ran 161. Verified as a control arm: with the directory check removed the suite fails on exactly the two #2223 paths and names the wrong classification. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This branch was successfully deployed
2 participants
Production CI-routing acceptance canary after #2197. One inline comment changes in a mapped source file; executable code is unchanged. Uses the ordinary master-certified map with no workflow or trust overrides. Master audit 34919418484 passed and certified the map with zero historical misses. Expected shard matrix: Integration A-B plus mandatory Integration D, 2/116. Actual selection and merge-reuse results are pending. Created ready to exercise the genuine PR event rather than draft-skipped CI. Integration D runtime diagnosis remains separate in existing PRs #2183/#2112.
Summary by CodeRabbit