Skip to content

Conversation

@fmoessbauer
Copy link
Member

The mtda-cli already supports to write the image using a bmap file. By that, writing images with large holes is speedup a lot. Further, the image data ranges are checksumed. We now implement the same feature for the web UI as well.

By moving it to the utils, we make it reusable from both the client, as
well as from the webserver.

Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
The StorageOpenHandler still required the mtda instance as second
argument. Since the introduction of the Pyro proxy, this interface does
not exist anymore and needs to be ported to the new remote_call proxy.

This apparently was forgotten for the storage_open API, hence these
requests (like storage-write) always failed.

Fixes: 7e13aac ("fix(www): create a Pyro proxy from the worker ...")
Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
The mtda-cli already supports to write the image using a bmap file. By
that, writing images with large holes is speedup a lot. Further, the
image data ranges are checksumed. We now implement the same feature for
the web UI as well.

Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
@github-actions github-actions bot requested a review from chombourger January 14, 2026 16:41
@fmoessbauer
Copy link
Member Author

Note, that the UI is still not hardened against any sort of user-error (e.g. flashing while the storage is attached to target, multiple clicks on upload, etc...). We should really improve at this frontier, as currently the chances to break MTDA by an erroneous click in the UI is quite high. Also, errors are not reported back to the user at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant