Skip to content

Tracking: follow-ups after NVIDIA sysexts and CI/cache work #325

Closed

Description

@jeefy

Tracking issue for follow-ups after the NVIDIA sysext work (#305, #304, #319) and the recent CI/cache work. Edit this list as ideas come up; open a separate issue or PR for each item when it's picked up.

NVIDIA sysexts

CI speed / build cache

Other

Ideas

Add here.

Activity

  1. added
    hive/covered-by-prHive verified that an open PR references or claims this issue; still actionable until confirmed
    on Oct 1, 2026
  2. added
    hive/likely-doneHive verified that a merged PR references or claims this issue; pending confirmation
    and removed
    hive/covered-by-prHive verified that an open PR references or claims this issue; still actionable until confirmed
    hive/likely-doneHive verified that a merged PR references or claims this issue; pending confirmation
    on Oct 1, 2026
  3. kylerankin commented on Oct 4, 2026

    @kylerankin
    Contributor

    test 2>&1


    🐝 Hive Agent: contributor | SHA: 3772407

  4. kylerankin commented on Oct 4, 2026

    @kylerankin
    Contributor

    This tracking issue's concrete follow-ups are all done (NVIDIA sysexts #305/#304/#319, patch-release tracking #326, toolkit version tracking #333, nvidia-sysext.md docs #326, parallel module signing #331, release-race #332, Ignition sig #285, Booty version help).

    Every remaining unchecked item is non-shippable from this repo today:

    No in-repo change is clearly actionable; the follow-ups are deferred, optional, or waiting on maintainer/external decisions.


    🐝 Hive Agent: contributor | SHA: 3772407

  5. hivecommons-hive commented on Oct 4, 2026

    @hivecommons-hive
    Contributor

    What to reply

    • /hive approve: go with the recommendation
    • /hive decision <your instructions>: go ahead, following your instructions
    • /hive help: show these again

    If this issue is waiting only for reporter confirmation after a merged fix, the reporter or a maintainer can reply /fixed instead.

    Only a maintainer with write access can un-park; everything else is ignored. Full command reference: https://github.com/hivecommons/hive/blob/v5/src/docs/maintainer-commands.md.

  6. jeefy commented on Oct 6, 2026

    @jeefy
    CollaboratorAuthor

    Closing: every follow-up this repo can ship is done (see the Oct 4 summary above). What remains is an optional second NVIDIA flavour (when a branch is needed), hardware validation on a Turing+ node, and admin secret moves documented in ci-tooling.md. Each of these can get its own issue when it's picked up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions