Skip to content

issues Search Results · language:Dune language:JavaScript language:JavaScript language:JavaScript

Filter by

18.9M results  (658 ms)

18.9M results

Severity: P2 Symptom: The candidate fallback boundary (16 vs 17 measures) and scoring were untested, so the degenerate-fixture-only suite couldn t catch regressions. Resolution: Extracted find_loop_candidates ...
backend
bug

Severity: P1 Symptom: Re-exporting a different loop/BPM/key could bundle stale MOGGs from a previous export into the ZIP. Root cause: The mogg dir was reused and trim_and_export zipped mogg_dir.glob( ...
backend
bug

Severity: P1 Symptom: A null key reached the UI and the export filename (..._None_...). One captured job had key: None. Root cause: beat_info.get( key , C ) does not substitute the default when the value ...
backend
bug

Severity: P1 Symptom: Even for unedited jobs, reloading the loop screen replaced the server s accurate (possibly uneven) measure_times with a synthetic even grid recomputed from persisted BPM/firstBeat. ...
bug
frontend

Severity: P2 Symptom: A spurious Connection lost error could flash when processing finished normally. Root cause: EventSource.onerror treated every error as a connection loss; the browser fires onerror ...
bug
frontend

Severity: P3 Resolution: Removed the unused btnSecondary style constant from Upload.jsx.
bug
frontend

Severity: P2 Symptom: Dropping a non-audio file (or .aiff) could upload something the backend can t serve. Root cause: The drop handler bypassed the input accept filter; .aiff had no backend MIME mapping. ...
bug
frontend

Severity: P2 Symptom: At playback rates other than 1x, the loop jumped early/late. Root cause: scheduleLoopJump timed the boundary with wall-clock ms (endTime - now)*1000, not divided by the active rate. ...
bug
frontend

Severity: P1 (latent) Symptom: A BPM change could snap the loop start to 0:00. Root cause: applyBpm() recomputed the grid without re-clamping startMeasureIdx; startTime = measureTimes[idx] ?? 0 then ...
bug
frontend

Severity: P1 Symptom: Candidate ordering was nondeterministic on real data. Root cause: cands.sort((a) = …) returned constants based only on a, violating the Array.sort contract. Masked because the degenerate ...
bug
frontend
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! Restrict your search to the title by using the in:title qualifier.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! Restrict your search to the title by using the in:title qualifier.