• docker-compose
• gunicorn
• nginx

Description

When saving a fireworks program, the timestamp field, which should be a number, is being saved as a string in the exported JSON file. This occurs because the .toFixed(1) method, used to format the timestamp value, converts the number to a string. This leads to a mismatch in expected data types when loading the program, as the validation logic expects a number, not a string.

As a result, once a program has been saved, it cannot be opened again in the editor.

Steps to Reproduce

1. Create a new fireworks program in the visual editor.
2. Add events with various timestamps.
3. Save the program.
4. Opening the program results in the error message: "The loaded Program is ill formed!\nPlease check the file or choose a different one."

Expected behavior: The timestamp field should be stored as a number.

Actual behavior: The timestamp field is stored as a string.

Possible Solution

Convert the timestamp back to a number after applying .toFixed(1).

Additional Context

This issue impacts the loading functionality of the editor as the program fails to validate the loaded data due to the unexpected string type for timestamp. For the backend functionality this is not relevant as a conversion to the numerical datatype is enforced in /backend/program.py:

timestamp = float(event['timestamp'])

• show latest log raw
• show latest log colored
• clear logs