chore(weights): drop the linked-issue bonus for sparkinfer - #1687
Merged
LandynDev merged 1 commit intoAug 11, 2026
Conversation
Follow-up to entrius#1682. That PR carried the K3 settings over to gittensor-ai-lab/sparkinfer but left scoring.standard_issue_multiplier and scoring.maintainer_issue_multiplier unset, so the repo inherited the platform defaults (1.33 / 1.66) and a PR that links an issue scored 33-66% above an identical PR that doesn't. SparkInfer already sets issue_discovery_share to 0.0, so the issue channel is meant to be off for this repo. Pin both multipliers to 1.0 (neutral, the floor of the [1, 5] validated range) so PR scoring rests only on the eval:* label multipliers from the trusted label pipeline.
LandynDev
approved these changes
Aug 11, 2026
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
2 participants
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.
Follow-up to #1682.
Summary
scoringblock togittensor-ai-lab/sparkinferpinningstandard_issue_multiplierandmaintainer_issue_multiplierto1.0.Why
#1682 carried the K3 settings over to
gittensor-ai-lab/sparkinferbut left both issue multipliers unset, so the repo silently inherited the platform defaults fromgittensor/constants.py:scoring.standard_issue_multiplierscoring.maintainer_issue_multiplierUnder those defaults,
_calculate_issue_multiplieringittensor/validator/oss_contributions/mirror/scoring.pyscores a PR with a valid linked issue 33–66% above an otherwise identical PR with no linked issue. That is a bonus SparkInfer does not want: the repo already setsissue_discovery_shareto0.0, so the issue channel is intended to be off here, and PR value is already expressed through theeval:*label multipliers applied by the trusted label pipeline. Leaving the linked-issue bonus on adds a scoring axis unrelated to the measured performance win, and rewards linking an issue rather than the contribution itself.1.0is neutral (no bonus) and is the floor of the[1, 5]range enforced by_validate_scoring_configs, so this is the minimum the registry permits. Every other knob —emission_share,maintainer_cut, eligibility, labels, and the platform-default time decay restored in #1682 — is unchanged.Validation
jq empty gittensor/validator/weights/master_repositories.jsonuv run --extra dev pytest tests/validator/test_load_weights.py(64 passed)uv run --extra dev pytest tests/validator/oss_contributions/mirror/(117 passed)resolve_scoringreturnsstandard_issue_multiplier=1.0,maintainer_issue_multiplier=1.0.