Claude
3d904f7cc6
Two real bugs in the clone work, both confirmed with repros before fixing
and re-confirmed by reverting each fix afterwards.
1. Data loss on every rundown switch (blocker).
cachedRundown was a module-level const mutated in place by init(). Once
setRundown stored by reference, db.data.rundowns[loadedId] aliased that
object, so loading a second rundown rewrote the first one's stored record
in place. Repro: after init(A) then init(B), store['rundown-a'] had
id 'rundown-b', title 'B' and order ['b1'] - A's data was gone, and both
keys pointed at one object.
The earlier audit missed this because it only asked whether callers mutate
an object after handing it over, within one rundown's lifetime. It never
considered that cachedRundown is a singleton reused across different
rundowns, which is where the aliasing actually bites.
Fixed at the root: cachedRundown is now reassigned rather than repurposed,
so a stored record keeps pointing at the data it was stored for. Mutating
in place from commit, while it still represents the same rundown, is
unchanged and is what keeps the stored record current. Every
getCurrentRundown() call site was checked - all are locals used within a
single operation, none held across a switch.
2. cloneEntryData was not key-equal to structuredClone.
For an entry without a custom/triggers/entries key, the spread-then-
override form added those as own keys ('custom' as {}, 'triggers' as
undefined). fast-equals deepEqual counts own keys, so a clone never
compared equal to its source, which is the comparison runtime.service.ts
uses to decide whether to re-broadcast - reinstating the per-tick
re-broadcast and restore-save this PR had already fixed once. Dropping
`?? []` earlier corrected the value but not the key.
Containers are now only replaced when the entry carries them.
The regression test was vacuous: toBeUndefined() passes for both an absent
key and an own key holding undefined. It now asserts key equality against
structuredClone plus deepEqual, and was verified to fail against the
previous implementation.
Typecheck, lint, format and the full suite (706 tests) pass.
Download the latest release
- Download for Windows
- Download for macOS (Apple Silicon)
- Download for macOS (Intel)
- Download AppImage for Linux (Intel / AMD 64-bit)
- Download AppImage for Linux (ARM 64-bit, Raspberry Pi 4+)
- Download AppImage for Linux (ARM 32-bit, older Raspberry Pi)
... or
- Get from Docker hub
- Install from NPM
- Install from Homebrew
Need help?
We do our best to have most topics covered by the documentation. However, if your question is not covered, you are welcome to fill in a bug report in an issue, ask a question in GitHub discussions or hop in the discord server for a chat.
Using Ontime?
Let us know! Ontime improves from the collaboration with its users. We would like to understand how you use Ontime and appreciate your feedback.
Ontime
Ontime is a browser-based application that manages event rundowns, scheduling, and cueing.
With Ontime, you can plan, track your schedule, manage automation and cross-department show information all in one place.
Ontime is made by entertainment and broadcast engineers and used by
- Conference organisers
- Touring shows and receiving venues
- Broadcasters and streamers
- Theatres and opera houses
- Houses of worship
Main features
- Multiplatform: Available as a Cloud service and for Windows, macOS, Linux, or self-hosted via Docker.
- In any device: Ontime is available to any device with a browser, eg: tablets, mobile phones, laptops, signage, media servers...
- Team Collaboration: Dedicated views for directors, operators, backstage, and signage.
- Real-Time Updates: Manage and communicate runtime delays effortlessly.
- Automatable: Ontime can be fully or partially controlled by an operator, or run standalone with the system clock
- Flexible Integrations: Use one of the APIs provided (OSC, HTTP, Websocket) or the available Companion module to integrate into your workflow (vMix, disguise, Qlab, OBS)
... and a lot more ...
For live environments
Ontime is designed for use in live environments.
This guides the application into being flexible and efficiently integrating into different workflows.
For teams
All information added in Ontime is shared with the production team and other software / hardware in your workflow.
Ontime also improves team collaboration with dedicated views for cuesheets and operators, and for public and production
signage.
Simple infrastructure
All the data is distributed over the network, making its distribution and infrastructure flexible and cheap.
With the availability of the docker image, you can also leverage IT infrastructure to make Ontime available online for
your team and clients.
Ontime is made by video engineers and entertainment technicians.
Using Ontime
Getting started
The easiest way to start with Ontime is by leveraging our Cloud service.
This will give you immediate access to running instances of Ontime which are available to share with anyone with an internet connection.
Alternatively, you can run Ontime locally for free by downloading the latest release for your platform or using the docker image, available at Docker Hub
Once installed and running, any device that shares the same network as Ontime will have access to Ontime.
More information is available in our docs
Continued development
Ontime is under active development. We continue adding and improving features in collaboration with users.
Have an idea? Reach out via email or open an issue
Issues
We use Github's issue tracking for bug reporting and feature requests.
Found a bug? Open an issue.
Contributing
Looking to contribute? All types of help are appreciated, from coding to testing and feature specification.
If you are a developer and would like to contribute with code, please open an issue to discuss before opening a Pull Request.
Information about the project setup can be found in the development documentation
Links
License
This project is licensed under the terms of the GNU GPL v3
Sponsor
You can help the development of this project or say thank you with a one time donation.
See the terms of donations.