Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Carry bounded H3 temporal context through chained video delivery

Open
  • Is something wrong?
#13,671 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript, node.js
Domain
api, backend

Research direction

Read modeContract.js, prepareParams.js, renderArgs.js, chainedVideo.js, and continuousVideo.js, then trace queue validation and model capability projection. Start by confirming which runtime pins support verified temporal continuation; the issue also depends on #13668, #13669, and #13670. Done means the admission and render paths agree, three successive chunks preserve bounded frame and audio history, and replay records the requested and effective strategy plus refusals.

Written by the indexing model from the issue text.

Description

area:media blocked effort:xhigh model:heavy plan planner:gpt-6-1-sol

Current evidence: chainedVideo.js takes source-video tails only for LTX window hops; continuousVideo.js backendJobParams converts local handovers into image mode. Queue replay and helper arguments do not express verified H3 temporal history.

Chosen fix: use the runtime contracts and backend adapters to add explicit temporal continuation admission with a last-frame opt-out. Wire requested strategy and bounded context through modeContract.js, prepareParams.js, renderArgs.js, chainedVideo.js, continuousVideo.js, queue validation/provenance and model capability projection. Refuse an explicitly requested temporal window on an unverified runtime, never silently report success after falling back. Preserve existing requests that implicitly use legacy last-frame behavior and keep source media intact.

Acceptance criteria:

  • Admission before queue persistence and render/replay boundary agrees on supported pins and explicit refusals.
  • Three successive chunks deliver each new frame exactly once; bounded history does not grow with the episode, repeat prefix frames, lose seam frames or repeatedly re-encode the accumulated source.
  • Tail video and corresponding audio intervals reach the correct adapter; timing is runtime-specific.
  • Cancel/restart/history-preparation failure removes only owned scratch assets, preserving completed clips and original source.
  • Persist requested/effective strategy, actual history length, backend pin/capability and refusal reason for later disclosure; preserve LTX window and source-splice coverage.

Scope: existing videoGen admission, queue, render and chain services, model capability projection and public-boundary tests.
Dispatch: heavy capability for cross-service async lifecycle and frame/audio delivery correctness; xhigh effort for persisted replay, failure and three-chunk invariants.

Blocked by #13668, #13669, #13670

Part of #13614

After shipping, check this slice in #13614. If this is its last open child, post a summary of all delivered children and close #13614; otherwise leave the epic open.

Dominant language
JavaScript
Stars
38
Forks
32
Avg merge
44m
Merged PRs (30d)
990

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from atomantic/PortOS

All issues in atomantic/PortOS

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.