UI Change Persistence Bug – Disk Allowance Not Updating Client

[hucker]

�I am experiencing an issue where changes made to the Disk Allowance (Maximum Disk Usage) within the BoincTasks JS interface are not being sent to or saved by the BOINC client.
�The Issue:
�The BoincTasks JS interface showed a limit of 1,000 GB after I edited it.
�However, the actual BOINC client continued to operate under a 1 GB limit.
�Upon restarting the BOINC client, BoincTasks JS reverted to showing the 1 GB limit, indicating that the previous change to 1,000 GB was never actually written to the client's configuration files (e.g., global_prefs_override.xml).
�Steps to Reproduce:
�Open BoincTasks JS and navigate to the preferences/settings for a connected client.
�Change the Disk Allowance from a low value (1 GB) to a higher value (1,000 GB).
�Observe that the UI reflects the change.
�Check the local BOINC Manager or the global_prefs_override.xml file; the change is not present.
�Restart the BOINC client/Manager and note that BoincTasks JS reverts to the old 1 GB value.
�Impact:
This caused the GPU scheduler to halt work fetch requests, as it incorrectly believed the disk was full. The only fix was to bypass BoincTasks JS and update the limit directly in the native BOINC Manager.
�Request:
Could you look into whether there is a "silent failure" occurring when BoincTasks JS attempts to write preference overrides back to the BOINC client? It seems the UI updates locally in the browser, but the RPC command to update the client is either not being sent or is being rejected