chore: sync skills (AIQ,CUDA-Q,DeepStream,Holoscan Sensor Bridge,Megatron-Core,NeMo MBridge,NeMo Relay,NeMo Retriever,accelerated-computing-cudf,aiq-deploy,aiq-research,cuDF,cudaq-guide,deepstream-sop,mcore-create-issue,mcore-linting-and-formatting,mcore-run-on-slurm,mcore-split-pr,mcore-testing,nemo-mbridge-perf-cuda-graphs,nemo-mbridge-perf-expert-parallel-overlap,nemo-mbridge-perf-moe-comm-overlap,nemo-mbridge-perf-moe-dispatcher-selection,nemo-mbridge-perf-moe-hardware-configs,nemo-mbridge-perf-moe-optimization-workflow,nemo-mbridge-perf-sequence-packing,nemo-mbridge-recipe-recommender,nemo-relay-instrument-typed-wrappers,nemo-retriever) - #409
Merged
Conversation
…tron-Core,NeMo MBridge,NeMo Relay,NeMo Retriever,accelerated-computing-cudf,aiq-deploy,aiq-research,cuDF,cudaq-guide,deepstream-sop,mcore-create-issue,mcore-linting-and-formatting,mcore-run-on-slurm,mcore-split-pr,mcore-testing,nemo-mbridge-perf-cuda-graphs,nemo-mbridge-perf-expert-parallel-overlap,nemo-mbridge-perf-moe-comm-overlap,nemo-mbridge-perf-moe-dispatcher-selection,nemo-mbridge-perf-moe-hardware-configs,nemo-mbridge-perf-moe-optimization-workflow,nemo-mbridge-perf-sequence-packing,nemo-mbridge-recipe-recommender,nemo-relay-instrument-typed-wrappers,nemo-retriever)
github-actions
Bot
requested review from
jasonnvidia,
mosheabr and
sayalinvidia
as code owners
August 3, 2026 19:33
mosheabr
approved these changes
Aug 3, 2026
mosheabr
added a commit
that referenced
this pull request
Aug 5, 2026
The sync PR title names every changed component, so it grows with the
catalog. It passed 256 characters and GitHub began rejecting it — first on
update, then on create:
Validation Failed: {"resource":"Issue","code":"custom","field":"title",
"message":"title is too long (maximum is 256 characters)"}
Rejection on create is the damaging case: no sync PR exists at all, so
synced content sits on automated/sync-skills unmerged and never reaches
main, while the rolling failure tracker emails on every run. That is the
state the repo has been in since 2026-08-04 11:47 UTC, with a
doca-telemetry-exporter update stranded on the branch.
Name as many components as fit and count the remainder — "+N more". The
complete list is unchanged in the PR body, which has no length limit, so
nothing is lost. Falls back to a bare count if even one name will not fit,
with a final length guard so an over-long title can never be emitted.
Verified against the composed title for each case:
29 components (the list that broke #409) 649 -> 229 chars
1 component (today's stranded sync) 44 chars
2 components 30 chars
200 components 253 chars
single 300-character name "chore: sync skills (1 component)"
sync-skills.yml still parses; the sync job's 17 steps are unchanged.
Signed-off-by: Moshe Abramovitch <moshea@nvidia.com>
melo-gonzo
pushed a commit
to melo-gonzo/NVIDIAskills
that referenced
this pull request
Aug 5, 2026
The sync PR title names every changed component, so it grows with the
catalog. It passed 256 characters and GitHub began rejecting it — first on
update, then on create:
Validation Failed: {"resource":"Issue","code":"custom","field":"title",
"message":"title is too long (maximum is 256 characters)"}
Rejection on create is the damaging case: no sync PR exists at all, so
synced content sits on automated/sync-skills unmerged and never reaches
main, while the rolling failure tracker emails on every run. That is the
state the repo has been in since 2026-08-04 11:47 UTC, with a
doca-telemetry-exporter update stranded on the branch.
Name as many components as fit and count the remainder — "+N more". The
complete list is unchanged in the PR body, which has no length limit, so
nothing is lost. Falls back to a bare count if even one name will not fit,
with a final length guard so an over-long title can never be emitted.
Verified against the composed title for each case:
29 components (the list that broke NVIDIA#409) 649 -> 229 chars
1 component (today's stranded sync) 44 chars
2 components 30 chars
200 components 253 chars
single 300-character name "chore: sync skills (1 component)"
sync-skills.yml still parses; the sync job's 17 steps are unchanged.
Signed-off-by: Moshe Abramovitch <moshea@nvidia.com>
Signed-off-by: Carmelo Gonzales <43048528+melo-gonzo@users.noreply.github.com>
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.
Automated skills sync
Components updated:
Skills held — signature drift (content changed without
skill.oms.sigrefresh):skills/accelerated-computing-cudf— reverted (2 file(s) changed without skill.oms.sig refresh)skills/aiq-deploy— reverted (3 file(s) changed without skill.oms.sig refresh)skills/aiq-research— reverted (4 file(s) changed without skill.oms.sig refresh)skills/cudaq-guide— reverted (5 file(s) changed without skill.oms.sig refresh)skills/deepstream-sop— reverted (4 file(s) changed without skill.oms.sig refresh)skills/mcore-create-issue— reverted (1 file(s) changed without skill.oms.sig refresh)skills/mcore-linting-and-formatting— reverted (1 file(s) changed without skill.oms.sig refresh)skills/mcore-run-on-slurm— reverted (1 file(s) changed without skill.oms.sig refresh)skills/mcore-split-pr— reverted (1 file(s) changed without skill.oms.sig refresh)skills/mcore-testing— reverted (1 file(s) changed without skill.oms.sig refresh)skills/nemo-mbridge-perf-cuda-graphs— reverted (3 file(s) changed without skill.oms.sig refresh)skills/nemo-mbridge-perf-expert-parallel-overlap— reverted (2 file(s) changed without skill.oms.sig refresh)skills/nemo-mbridge-perf-moe-comm-overlap— reverted (2 file(s) changed without skill.oms.sig refresh)skills/nemo-mbridge-perf-moe-dispatcher-selection— reverted (3 file(s) changed without skill.oms.sig refresh)skills/nemo-mbridge-perf-moe-hardware-configs— reverted (3 file(s) changed without skill.oms.sig refresh)skills/nemo-mbridge-perf-moe-optimization-workflow— reverted (3 file(s) changed without skill.oms.sig refresh)skills/nemo-mbridge-perf-sequence-packing— reverted (3 file(s) changed without skill.oms.sig refresh)skills/nemo-mbridge-recipe-recommender— reverted (3 file(s) changed without skill.oms.sig refresh)skills/nemo-relay-instrument-typed-wrappers— reverted (1 file(s) changed without skill.oms.sig refresh)skills/nemo-retriever— reverted (12 file(s) changed without skill.oms.sig refresh)Components that failed to sync:
skills/dynamo-interconnect-check/empty or missingskills/dynamo-recipe-runner/empty or missingskills/dynamo-router-starter/empty or missingskills/dynamo-troubleshoot/empty or missingTriggered by:
schedule