Public bug reported:
When writing a test using Uploader, I thought I'd make use of the
ability to send data straight away, and then just wait for the state
change. Something like:
uploader = folder.createFile(...);
uploader->write(...);
uploader->close();
// wait for statusChanged to Finished
However, this dropped me to the Error state with the message:
Uploader::close(): cannot finalize while Uploader is not in the
Ready state
The preferred behaviour would be for the uploader to queue the close and
send it after the buffered data has been sent.
To be honest, I wonder if we'd be better off not distinguishing between
Loading and Ready states on the Uploader. Cancellation in the Loading
state could be handled by firing off the CancelUpload D-Bus call once
the initial D-Bus call completes.
** Affects: storage-framework (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644669
Title:
Uploader.close() fails if in Loading state
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/storage-framework/+bug/1644669/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
