HiFiBerryOS64 Alpha 7 - Arrange sources not working

[mbolo01]

DO NOT remove the blocks below, but fill these with the requested data. Incomplete bug reports will be ignored!
You should remove this comment before posting the bug report.

Describe the bug
When moving a source item from one position to another, it goes back to the initial place.

HiFiBerryOS version
20240410

HiFiBerry sound card
DAC+DSP

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
Being able to rearrange sources

Screenshots
If applicable, add screenshots to help explain your problem.

Browser (if applicable)

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[mbolo01]

For a reason I ignore, arranging sources works now

[mbolo01]

Here is a video illustrating the issue rearranging sources.
I rebooted the RPI and then tried to rearrange the sources.

Enregistrement.de.l.ecran.2024-04-19.a.11.07.59.mov

Also, some disabled sources like ROON, Airplay, Spotify Daemon, etc... (I guess Extensions generally speaking) do not appear under the Disabled Sources section

[mbolo01]

Today after a reboot it works again ... I can arrange sources and disabled sources are correctly listed in the Disabled sources section. Hard to understand the context that breaks it

[mbolo01]

Failed to work again. I don't have a precise context other than maybe a hard restart of the PI (power off/on)
Subsequently, restarting HBOS via the UI makes no difference, any browser I have tried would show the issue ( I was thinking about a cache issue). I could see that the sources.json had several "null" in the string.
I finally used the CLI to reboot and now it is back to normal.

[mbolo01]

Found the root cause: It happens that I have to power off/on the RPI by unplugging the mains. When HBOS starts back, sources cannot be arranged anymore and disabled sources are no longer shown as disabled. I don't know how to recover from that by a CLI command, and sometimes if corrects by itself post reboot.