Datasets:

maxwellinked
/

time-lapse-artifacts

Current main commit: 9aa0bacc6f37f64e2568d2203bd8f369e764c927
Change: explicit, identical 29-field features declarations for the canonical and pre_standard VideoFolder configs; no media files changed
Independent datasets==4.8.4 streaming test at that exact revision passes: canonical/archive = 338 rows, pre_standard/archive = 129 rows; both expose encoded_frame_rate as float64
Public Viewer endpoints /splits, /is-valid, /parquet, /size, and /rows all currently return HTTP 500: ?The server is busier than usual and the response is not ready yet. Please retry later.?
The prior build completed successfully before this corrective metadata merge.

Could you please inspect or retrigger the Viewer job for the current main revision? I am deliberately withholding the planned v0.3.0 tag until the production Viewer/Parquet output is verified.

maxwellinked

Owner 38 minutes ago

Hugging Face CLI

Update: the rebuild has partially recovered, which narrows the problem.

At 2026-08-18 21:51 UTC:

/is-valid returns 200 with preview, viewer, search, and filter all true (statistics remains false).
/rows returns 200 for both canonical/archive and pre_standard/archive, including their last rows. Live totals are 338 and 129, partial: false, 29 fields in both, and encoded_frame_rate is now correctly float64. This confirms row serving is using the corrected 9aa0bacc... schema.
/splits, /parquet, and /size still return HTTP 500 with x-error-code: ResponseNotReady.
The public Hugging Face status feed shows no active incident.

This now looks like a stuck or incomplete dataset-specific split/Parquet aggregation job rather than a general outage. The v0.3.0 tag remains withheld pending those three outputs.

Upload images, audio, and videos by dragging in the text input, pasting, or clicking here.

Tap or paste here to upload images

· Sign up or log in to comment