mirror of
https://github.com/4gray/iptvnator.git
synced 2026-10-10 01:56:16 -08:00
* fix(xtream): render catch-up start times in the panel timezone
The `{Y-m-d:H-M}` segment of an Xtream timeshift URL is read by the panel
with `strtotime()` in ITS timezone (`server_info.timezone`), never the
viewer's. The timezone was learned in memory only, by the store's
`checkPortalStatus()`, so the Favorites / Recent catch-up resolver — which
reads the STORED playlist row — always fell back to the viewer's local
clock and asked the panel for the wrong programme (#1562).
- Normalize the panel's clock once (`resolveXtreamServerTimezone`): an
ICU-resolvable name is kept, otherwise a `UTC±HH:MM` offset is derived
from the `time_now` / `timestamp_now` clock pair, so spellings such as
`UTC+3` no longer silently mean "local time".
- Persist it on the playlist row through `transformPlaylistMeta` (no-op
when unchanged) and project it back from the payload in
`DB_GET_PLAYLIST`, so both catch-up entry points and a restart see it.
- Format with `hourCycle: 'h23'` (server midnight is `00`, never `24`) and
read timestamp-less EPG `start`/`end` strings in the panel's clock.
- Mock: `tzoffset:tzoffset` scenario with an unusable timezone name and a
+03:00 clock pair; Electron e2e covers Live TV, Favorites, a restart into
Global favorites, and the clock-pair derivation at a UTC-3 viewer.
Closes #1562
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* fix(xtream): guard the account-info answer by playlist identity and reject rolled-over dates
Review follow-ups (Greptile):
- A source switch while `get_account_info` is in flight no longer hands
playlist A's status or clock to playlist B: the store is patched only
while the asking playlist is still selected, the timezone is persisted
under the asking playlist's id regardless, and a late failure cannot mark
the newly selected playlist unavailable.
- `parseNaiveUtcMs` reads the constructed date back, so out-of-range panel
strings (`2026-13-01 25:00:00`) are rejected instead of silently rolling
over into a real instant.
- Document that a clock-derived fixed offset is a DST-less snapshot, refreshed
by every account-info check and only ever used for non-standard servers.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* fix(xtream): drop a panel clock that no longer belongs to the source
Review follow-ups (Codex + Greptile):
- A metadata update or DB_UPDATE_PLAYLIST that points the source at another
server drops the persisted `serverTimezone` (payload-only) until the next
account-info check, so Favorites / Recent cannot keep rendering the OLD
panel's clock; an update that supplies a clock keeps it.
- A late account-info answer is persisted only onto a row that still points
at the panel it came from — an edit that moved the source during the
request keeps the clock the edit flow dropped.
- The PWA data source and the route-session converter carry the persisted
timezone into the store playlist, so a later response without a usable
clock has a previous value to preserve.
- Mirror the catch-up timezone contract into AGENTS.md.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* fix(xtream): drop the stale panel clock inside the UPDATE statement
Review follow-up (Codex): the database worker interleaves requests, so a
read-modify-write of the playlist payload could hand a concurrent upsert's
newer payload back to the past. The `serverTimezone` removal on a server
URL change is now one `CASE … json_remove(payload, '$.serverTimezone')`
expression inside the same UPDATE, guarded by `json_valid`; the spec runs
the real statement against Electron's SQLite on the actual `playlists`
table (moved, renamed, clock-less, malformed-payload and NULL-URL rows).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* refactor(xtream): split the server-clock primitives out of the timezone util
Review follow-up (Greptile): `xtream-server-timezone.util.ts` had grown past
the 300-line file guideline. The zone-agnostic wall-clock primitives (stored
forms, Intl parts, naive parsing) now live in `xtream-server-clock.util.ts`;
the timezone util keeps the Xtream policy and re-exports the public helpers,
so every import and the spec are unchanged.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* fix(xtream): offer the learned panel clock to storage on every check
Review follow-up (Codex): a transient storage failure left the clock in the
store but not on the row, and the next check compared the answer with the
in-memory value and never retried. The resolved timezone is now always
handed to `transformPlaylistMeta`, whose row-level equality check keeps the
common case a read without a write; a failed write is retried by the next
account-info check.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* fix(xtream): apply an account-info answer only to the panel it came from
Review follow-up (Codex): an in-place edit keeps the playlist id while
moving the source, so an answer already on the wire for the OLD panel
passed the id-only guard and patched the new panel's status and clock into
the store. One `answersFor(candidate, credentials)` predicate now gates the
store patch, the error path and the persisted-row transform alike.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* fix(xtream): never report another panel's status for the selected playlist
Review follow-up (Greptile): callers gate content initialization on the
value `checkPortalStatus()` returns for whatever is selected NOW. When the
answer no longer describes the selected playlist (source switch or in-place
edit during the request), the store's own verdict about the current
selection is returned instead of the old panel's status — on success and on
failure alike.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* fix(xtream): persist the panel clock with one conditional UPDATE
Review follow-up (Codex): `transformPlaylistMeta` reads the row and then
upserts it whole, while the Xtream edit dialog saves through
`DB_UPDATE_PLAYLIST` outside `PlaylistsService`'s queue and the database
worker interleaves requests — an edit landing between that read and the
upsert was silently undone.
Persistence now goes through `IXtreamDataSource.rememberServerTimezone`:
- Electron: new `DB_SET_PLAYLIST_SERVER_TIMEZONE` worker op — one UPDATE
that `json_set`s the payload only while the row still points at the
request's connection and does not already carry the value; a malformed
payload is never rewritten (CASE, not AND, so json_extract cannot run
before json_valid). Wired through the worker types, main handler,
preload, bridge interface, both IPC contract tables and
`DatabaseService.setXtreamPlaylistServerTimezone`.
- PWA: `transformPlaylistMeta`, whose read and write share one IndexedDB
readwrite cursor transaction, plus the localStorage copy.
The store no longer injects `PlaylistsService`; it offers the resolved clock
to the data source and keeps only its in-memory guards. Real-SQLite coverage
for the op (fresh / same / moved / NULL / malformed / missing rows),
delegation specs for both data sources, docs updated.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* fix(xtream): keep the stored panel clock across clockless full upserts
Review follow-up (Codex): a `PlaylistsService` mutation that read the row
before `DB_SET_PLAYLIST_SERVER_TIMEZONE` landed and upserted afterwards
replaced the payload with its clockless snapshot. `DB_UPSERT_APP_PLAYLIST(S)`
now carry the STORED clock into a snapshot that has none while the row still
points at the same connection (`playlistConflictUpdate`, nested CASE so the
json_* readers never run on a malformed payload); a snapshot with its own
clock, or one that moves the source, wins as is. Real-SQLite coverage for
kept / moved / own-clock / batch rows.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* refactor(release): split capture-navigation under the max-lines cap
`tools/release/capture-navigation.ts` had grown to 567 counted lines, past
the 400-line rule, which failed `release-tools:lint` and — because the file
was not in the baseline — the max-lines baseline test on master and on
every PR branched from it. The 19 named setup actions are now grouped by
subject over one leaf module of shared page helpers:
- `capture-navigation-helpers.ts`: playlist-id registry, dialog handling,
navigation moves, `settleUi`
- `capture-navigation-setup-actions.ts`: add-playlist dialogs, settings
sections, remote control
- `capture-navigation-portal-actions.ts`: portal catalogs, live lists,
alternative sources (the two identical live-category flows share one
helper)
- `capture-navigation-download-actions.ts`: the download manager shots
- `capture-navigation.ts`: the `runAction` dispatcher, theme switching and
the re-exported API the seeding driver and the capture script import
Actions call their siblings directly instead of recursing through
`runAction`, so no module depends on the dispatcher. The action vocabulary
is unchanged (same 19 names, same waits and timeouts); every file is under
300 lines and the new modules are listed in the `release-tools` lint target.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* refactor(electron): move the panel-clock SQL into its own operations module
Review follow-up (Greptile): the timezone persistence, invalidation,
upsert-preservation and row projection had landed in
`playlist.operations.ts`, a baselined 1,000-line file. They now live in
`playlist-server-timezone.operations.ts` (155 lines) — the three SQL
shapes plus the payload projection — and the playlist operations compose
them; the baselined file shrinks by 107 lines. Behaviour and the
real-SQLite coverage are unchanged.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
112 lines
4.4 KiB
TypeScript
112 lines
4.4 KiB
TypeScript
import { PlaylistRecentlyViewedItem } from './playlist-recently-viewed.interface';
|
|
import { StalkerPortalItem } from './stalker-portal-item.interface';
|
|
|
|
/**
|
|
* An interface that describe the possible states of the playlist update/refresh process
|
|
*/
|
|
export enum PlaylistUpdateState {
|
|
UPDATED,
|
|
IN_PROGRESS,
|
|
NOT_UPDATED,
|
|
}
|
|
|
|
/**
|
|
* Describes playlist interface
|
|
*/
|
|
export interface Playlist {
|
|
_id: string;
|
|
title: string;
|
|
filename?: string;
|
|
playlist?: any;
|
|
importDate: string;
|
|
lastUsage: string;
|
|
/**
|
|
* M3U playlists store channel URL strings (`string[]`).
|
|
* Stalker portals store full item objects (`StalkerPortalItem[]`).
|
|
*/
|
|
favorites?: (string | StalkerPortalItem)[];
|
|
items?: unknown[];
|
|
header?: unknown;
|
|
count: number;
|
|
url?: string;
|
|
userAgent?: string;
|
|
referrer?: string;
|
|
origin?: string;
|
|
filePath?: string;
|
|
/** M3U-scoped EPG source URLs enabled for automatic import and lookup. */
|
|
epgUrls?: string[];
|
|
/** All M3U EPG source URLs detected from the playlist header. */
|
|
detectedEpgUrls?: string[];
|
|
/** Playlist-local EPG source URLs explicitly enabled by the user. */
|
|
manualEpgUrls?: string[];
|
|
/** Detected playlist EPG source URLs explicitly disabled by the user. */
|
|
disabledEpgUrls?: string[];
|
|
autoRefresh: boolean;
|
|
updateDate?: number;
|
|
updateState?: PlaylistUpdateState;
|
|
position?: number;
|
|
isTemporary?: boolean;
|
|
serverUrl?: string;
|
|
username?: string;
|
|
password?: string;
|
|
macAddress?: string;
|
|
portalUrl?: string;
|
|
recentlyViewed?: PlaylistRecentlyViewedItem[];
|
|
/** Indicates if this is a full stalker portal URL (e.g., /stalker_portal/c) requiring handshake authentication */
|
|
isFullStalkerPortal?: boolean;
|
|
/**
|
|
* The Xtream panel's own timezone, learned from `server_info` of the
|
|
* account-info response and normalized by `resolveXtreamServerTimezone`
|
|
* (an IANA name, or a clock-derived `UTC±HH:MM`). Persisted on the row so
|
|
* every catch-up URL builder — the Live TV layout AND the Favorites /
|
|
* Recent resolver, which reads the stored row — renders programme start
|
|
* times in the clock the panel's `strtotime()` expects (issue #1562).
|
|
*/
|
|
serverTimezone?: string;
|
|
/** Session token for full stalker portal authentication - persisted for session */
|
|
stalkerToken?: string;
|
|
/**
|
|
* Identity fingerprint the persisted `stalkerToken` was negotiated for.
|
|
* Re-presenting a token minted for a DIFFERENT identity (the user edited
|
|
* the MAC, serial or device ids) would pair a new identity with an old
|
|
* session — the same class of bug the in-memory cache guards against, so
|
|
* reuse is refused unless this still matches the playlist.
|
|
*/
|
|
stalkerSessionIdentity?: string;
|
|
/**
|
|
* Watchdog cadence the portal advertised in `get_profile`, persisted
|
|
* alongside the token: reusing a stored token skips the profile request
|
|
* that carries these, so without persistence the keep-alive would fall
|
|
* back to the 120 s default forever.
|
|
*/
|
|
stalkerWatchdogTimeout?: number;
|
|
/** Per-user watchdog jitter (seconds) from `get_profile`. */
|
|
stalkerTimeslot?: number;
|
|
/** Serial number for stalker portal - generated once and stored for consistency */
|
|
stalkerSerialNumber?: string;
|
|
/**
|
|
* Optional device ID 1 for stalker portal. Absent means absent — nothing
|
|
* generates one at request time. The import dialog can pre-fill a
|
|
* MAC-derived value on request, but it is stored here as a literal string
|
|
* from then on: the portal pins the first non-empty value to the MAC
|
|
* permanently, so a value that silently followed a later MAC edit would be
|
|
* refused as a device conflict.
|
|
*/
|
|
stalkerDeviceId1?: string;
|
|
/** Optional device ID 2 for stalker portal - same pinning rules as `stalkerDeviceId1`. */
|
|
stalkerDeviceId2?: string;
|
|
/** Optional signature 1 for stalker portal - required by some portals for device verification */
|
|
stalkerSignature1?: string;
|
|
/** Optional signature 2 for stalker portal - required by some portals for device verification */
|
|
stalkerSignature2?: string;
|
|
/** Account info from get_profile call */
|
|
stalkerAccountInfo?: {
|
|
login?: string;
|
|
expireDate?: number;
|
|
tariffPlanName?: string;
|
|
status?: number;
|
|
};
|
|
/** Hidden M3U group titles for the groups view */
|
|
hiddenGroupTitles?: string[];
|
|
}
|