Desktop uploader fails to upload

Contributing and equipment
1

Use the desktop uploader they said (meaning support).

No surprise there. It won’t upload. :smile:

[2021-10-05 01:00:09.188] [debug] [mapillary:tools] Finishing upload c1ed7678-6800-4418-8b30-5471da51f955

[2021-10-05 01:00:10.156] [debug] [mapillary:tools] Traceback (most recent call last):
  File "\\vmware-host\Shared Folders\Dev\mapillary_tools\pyinstaller\main.py", line 4, in <module>

[2021-10-05 01:00:10.157] [debug] [mapillary:tools]   File "mapillary_tools\__main__.py", line 93, in main

[2021-10-05 01:00:10.158] [debug] [mapillary:tools]   File "mapillary_tools\commands\upload.py", line 112, in run

[2021-10-05 01:00:10.159] [debug] [mapillary:tools]   File "mapillary_tools\upload.py", line 146, in upload
  File "mapillary_tools\uploader.py", line 357, in upload_sequence_v4

[2021-10-05 01:00:10.160] [debug] [mapillary:tools] RuntimeError: Upload server error: failed to create the cluster {}
[14104] Failed to
[2021-10-05 01:00:10.161] [debug] [mapillary:tools]  execute script 'main' due to unhandled exception!

[2021-10-05 01:00:10.300] [debug] [mapillary:tools] process exit code 1 and signal null
[2021-10-05 01:00:10.300] [error] [store:modules:uploadSession] Error: exit with code 1 and signal null
    at ChildProcess.<anonymous> (file:///C:/Users/sergei/AppData/Local/Programs/mapillary-desktop-uploader/resources/app.asar/webpack:/src/renderer/services/rx/ipc.ts:16:11)
    at ChildProcess.emit (events.js:215:7)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
[2021-10-05 01:00:10.310] [info] [power-saver-blocker] stop: 2
[2021-10-05 01:00:10.321] [info] [services:observer-manager] Stopping 6f483740-255e-11ec-b5c4-2b379a34ba22
[2021-10-05 01:00:10.322] [error] [vue] Error: exit with code 1 and signal null
    at ChildProcess.<anonymous> (file:///C:/Users/sergei/AppData/Local/Programs/mapillary-desktop-uploader/resources/app.asar/webpack:/src/renderer/services/rx/ipc.ts:16:11)
    at ChildProcess.emit (events.js:215:7)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
2

This is likely related to recent outages. Services appear to be coming back online.
https://twitter.com/mapillary/status/1445088765962166275?s=20

3 Likes
3

Can you confirm whether it is working for you again now?

4

It is working now, but still I use it because of not working Android uploader. I am stuck with 20Gb of sequenceses on my phone which have been sitting there for 2 month already because mapillary Android app keeps crashing on upload tab. Therefore, I have to use Open Camera to be able to use the SD-card and Desktop uploader which adds unnecessary hassle and takes way more time. Said from the support team just stopped replying. The version was updated from 5.0.5 to 5.0.6 and no fix for the problem with the Android uploader. Why can’t you fix a serious issue or give access to pictures to upload them via the desktop uploader? I have 1Gb of free memory on my phone and I don’t know when I am able to use again the memory taken by Mapillary. Some sequences may become outdated by that time. But what am I talking about if the whole bundle of fb apps can go down for several hours globally. This just says it all about the professionals working there. If you can fix the whole fb eco-system in one day, how much time do you need to fix the uloader on Android? I reported the bug 2 mo ago!

1 Like