Edit spool - initial weight gets reset to filament default

[Paul-Damian]

Describe the bug
Editing a spool resets the initial_weight to the default one taken from the filament definition

To Reproduce
Steps to reproduce the behavior:
Installed Spoolman as Docker container, with MariaDB server on the same Debian machine. Klipper/Moonraker are installed on another machine - a Raspberry Pi, making requests trough the network.

Defined a new filament. Set 1000g for the filament, because that's what the manufacturer is selling.
Defined a new spool of that filament. Weighted the spool, so I entered 1009 g for it, because no spool is initial exactly the advertised weight.
Saved the spool. Spool list shows correctly 0g used weight, 1009g remaining.
Edit spool. In the edit form the Initial Weight field shows now 1000g, not 1009. Look in the MariaDB database, initial_weight field shows correctly 1009.
At every refresh or entering the spool edit for a fraction of a second it shows 1009, but it will be overwritten with 1000.
This appears 9 times out of ten, occasionally it shows the correct value.

Spoolman Host (please complete the following information):

• Installation type: Docker
• Installed version: 0.19.3
• OS and Distro: Debian
• Database type: mariaDB

Desktop (please complete the following information):

• OS: Windows
• Browser: Firefox and Edge

[Paul-Damian]

Made also a little screen record:

[nikstohn]

Noticed the exact same problem on my install since starting using it with 0.18.1 (on Synology DSM 7 using Container Manager).
Also had to refresh the edit pages multiple times to actually get my override values.

[igiannakas]

Same thing is happening when updating the empty spool weight. It gets overridden by the default for the manufacturer and loses the edited values :(

is there any workaround for this by any chance?