Skip to content

chore(deps-dev): bump @types/node from 22.19.21 to 25.9.3 in the dev-dependencies group across 1 directory#13

Merged
srperens merged 1 commit into
mainfrom
dependabot/npm_and_yarn/dev-dependencies-a243c58be6
Jun 15, 2026
Merged

chore(deps-dev): bump @types/node from 22.19.21 to 25.9.3 in the dev-dependencies group across 1 directory#13
srperens merged 1 commit into
mainfrom
dependabot/npm_and_yarn/dev-dependencies-a243c58be6

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 15, 2026

Copy link
Copy Markdown
Contributor

Bumps the dev-dependencies group with 1 update in the / directory: @types/node.

Updates @types/node from 22.19.21 to 25.9.3

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the dev-dependencies group with 1 update in the / directory: [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node).


Updates `@types/node` from 22.19.21 to 25.9.3
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

---
updated-dependencies:
- dependency-name: "@types/node"
  dependency-version: 25.9.3
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: dev-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jun 15, 2026
@srperens srperens merged commit 148e120 into main Jun 15, 2026
6 checks passed
@srperens srperens deleted the dependabot/npm_and_yarn/dev-dependencies-a243c58be6 branch June 15, 2026 11:46
srperens added a commit that referenced this pull request Jun 22, 2026
…AI correction

The clock derived the playhead time from first-segment-PDT + video.currentTime.
That assumes an uninterrupted stream: across a producer-off gap (discontinuity)
media currentTime does not advance but wall-clock does, so the clock drifted
behind by the total gap length (e.g. ~76 min of accumulated gaps). Now it tracks
the fragment actually on screen (FRAG_CHANGED) and uses that segment's own
PROGRAM-DATE-TIME plus only the offset within the segment, which is gap-immune.
Removed the first-segment anchor fallback that caused the drift; show "—" rather
than a guessed value when the playhead time is not yet known. Also subtract the
37s TAI-UTC offset so the time shown is civil local, matching the feed's burnt-in
timecode.

Bump build stamp to #13.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
srperens added a commit that referenced this pull request Jun 22, 2026
…~37s ahead) (#46)

* fix(ui): show civil local time, not TAI (clock was ~37s ahead)

The playhead clock and the segment list rendered TAMS timestamps directly. TAMS
time is TAI, which is 37s ahead of UTC, so the displayed wall-clock ran ~37s ahead
of civil local time and did not match the timecode burnt into the video feed.
Verified against the live flow: latest segment read 16:31:22 local while the real
time was 16:30:48 (+34s, = TAI minus a few seconds of ingest latency). Subtract the
37s TAI-UTC offset so the inspector shows civil local time, matching the feed.

Bump build stamp to #12.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* fix(ui): playhead clock tracks the on-screen segment (gap-immune) + TAI correction

The clock derived the playhead time from first-segment-PDT + video.currentTime.
That assumes an uninterrupted stream: across a producer-off gap (discontinuity)
media currentTime does not advance but wall-clock does, so the clock drifted
behind by the total gap length (e.g. ~76 min of accumulated gaps). Now it tracks
the fragment actually on screen (FRAG_CHANGED) and uses that segment's own
PROGRAM-DATE-TIME plus only the offset within the segment, which is gap-immune.
Removed the first-segment anchor fallback that caused the drift; show "—" rather
than a guessed value when the playhead time is not yet known. Also subtract the
37s TAI-UTC offset so the time shown is civil local, matching the feed's burnt-in
timecode.

Bump build stamp to #13.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant