Intermittent Problem with Mac BlompLive client

[spt3m4]

Hi, hoping someone can shed some light. I had turned on logging, tried uploading two files (see attached jpg for screenshot).

Where the top file (the 454 MB one) failed, and the bottom file (the 400 MB one) succeeded.

The bottom file was uploaded first, then the top one (you can see from the Content-Length they match).

I verified that the Used Storage from the web app did not increase after the second upload, yet it did after the first upload.

The web app also showed the first upload but not the second, Yet the BlompLive client showed both so there is definitely a discrepancy.

Could it be a timed out upload? The second one did return an invalid HTTP response code.

Thanks in advance.

Here is the redacted log from the BlompLive client:

Code: Select all

21:38:59.804560 69 ../blomplive/src/ui/settings_viewmodel.h
onload

2022-12-23 19:46:03.296810 UTC
PUT http://swiftproxy-01.acs.ai.net:8080/v1/AUTH_ <redacted>
path: <redacted>
X-Auth-Token: d4358079379149eaaf146ef78dbd8feb
Content-Type: application/octet-stream
2022-12-23 22:11:43.695008 UTC
201
Last-Modified: Fri, 23 Dec 2022 19:46:04 GMT
Content-Length: 0
Etag: e4a8594c986ca3c8247f2140ae5bc61f
Content-Type: text/html; charset=UTF-8
X-Trans-Id: txf54b2d5409594c1bb47af-0063a6057b
X-Openstack-Request-Id: txf54b2d5409594c1bb47af-0063a6057b
Date: Fri, 23 Dec 2022 22:11:43 GMT
Connection: keep-alive
content length: 400655169

22:50:35.822074 69 ../blomplive/src/ui/settings_viewmodel.h
onload

2022-12-23 22:30:46.041633 UTC
PUT http://swiftproxy-01.acs.ai.net:8080/v1/AUTH_ <redacted>
path: <redacted>
X-Auth-Token: d4358079379149eaaf146ef78dbd8feb
Content-Type: application/octet-stream
2022-12-24 01:02:11.025864 UTC
0
content length: 454479875

[spt3m4]

Additional info: i set up `rclone` and did an `rclone copyto` and the same file that failed above had successfully uploaded.

So at this stage at least i have workaround. Would be nice to get a non-windows GUI working consistently. But no rush. Happy holidays

[BlompSupport]

Hello Blomper,

First of all, happy holidays to you as well.
I hope you had an amazing new years eve!!

Second, are you still having any problems? If not, then perfect!

But in any case, I forwarded the problem you are having to our programmers and they are looking into it as we speak. We apologize for the delay but are grateful for your feedback. Blomp always wants to make your experience top-notch.

Looking forward to your reply blomper

[spt3m4]

Hello,

Thank you for your reply.

Frankly since there were no reply to my inquiry for close to 10 biz days i have resorted to using the `rclone` CLI exclusively to work with my content. The GUI would have been nice, but due to the difficulty in diagnosing problems and failing without proper explanation (as noted above), it is not a trustworthy piece of software. (Think from a user's perspective, what's the point for having a GUI if i can't even trust that an upload was done successfully, and have to go to the web dashboard to verify every time?) So as a result, respectfully, unless there is a drastic improvement to the GUI tool i will be keep using `rclone` to work with my content.

Thanks for your consideration.

[BlompSupport]

Hello there,

First of all, I want to apologize for the delay. Given that it was the holiday season, most of our folks were with their families, appreciating the smaller things in life.

It would be a great help if you tell us if the two redacted AUTH codes are the same. If they aren’t, that likely means the auth cookie had expired on the first upload and was renewed/re-obtained by the second… that isn’t a good operation and we can fix it, but it would be helpful to know.

[spt3m4]

Thanks. Finally have a chance to get back to this and found the saved log. Can confirm that the 2 auth codes are the same between the 2 upload requests, if that still helps.

[BlompSupport]

Hello there!
Thank you for getting back to us. It helps.

Given the number of hours passed between the first and second file transfer, it is possible that the AUTH token aged out. I don’t recall what the default setting is. This is a bug in the older version of Blomplive (that is public) and something we are addressing in the beta ones in limited testing. Are you on Android or IOS? We may be able to get you a newer version under active development to see if that helps.