Slicer Preview Release package for Windows failed to upload

If I try to download the latest Slicer Preview Release then I got an empty zip file of 22 bytes.

It seems that there was an upload error.

@Sam_Horvath @jcfr Could you please have a look at this and remove the invalid file (or upload the correct file)? There are about 400 Windows downloads a day, so such an error makes many people unhappy (I already got complaints coming in).

For people who come across this topic and need a workaround: you can download the Slicer release from the previous day using this link: https://download.slicer.org/?offset=-1

I am working on getting the upload fixed

@lassoan This should be fixed now, can you confirm?

1 Like

It works perfectly now, thank you!

1 Like

@Sam_Horvath @jcfr There appears to be the same upload error again on the Windows platform.

https://slicer.cdash.org/viewBuildError.php?buildid=2445193

Fixed again. Not sure why this is happening, the extension packages are uploading fine.

@jcfr This seems to be some sort of interaction between the upload script and the server? Does not happen with the extension packages.

Traceback (most recent call last):
  File "c:\python36-x64\lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "c:\python36-x64\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "D:\Support\slicer_package_manager-venv\Scripts\slicer_package_manager_client.exe\__main__.py", line 7, in <module>
  File "d:\support\slicer_package_manager-venv\lib\site-packages\click\core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "d:\support\slicer_package_manager-venv\lib\site-packages\click\core.py", line 697, in main
    rv = self.invoke(ctx)
  File "d:\support\slicer_package_manager-venv\lib\site-packages\click\core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "d:\support\slicer_package_manager-venv\lib\site-packages\click\core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "d:\support\slicer_package_manager-venv\lib\site-packages\click\core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "d:\support\slicer_package_manager-venv\lib\site-packages\click\core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "d:\support\slicer_package_manager-venv\lib\site-packages\click\decorators.py", line 27, in new_func
    return f(get_current_context().obj, *args, **kwargs)
  File "d:\support\slicer_package_manager-venv\lib\site-packages\slicer_package_manager_client\cli.py", line 610, in _cli_uploadApplicationPackage
    pkg = sc.uploadApplicationPackage(*args, **kwargs)
  File "d:\support\slicer_package_manager-venv\lib\site-packages\slicer_package_manager_client\__init__.py", line 469, in uploadApplicationPackage
    progressCallback=_displayProgress)
  File "d:\support\slicer_package_manager-venv\lib\site-packages\girder_client\__init__.py", line 878, in uploadFileToItem
    return self._uploadContents(obj, f, filesize, progressCallback=progressCallback)
  File "d:\support\slicer_package_manager-venv\lib\site-packages\girder_client\__init__.py", line 994, in _uploadContents
    data=_ProgressBytesIO(chunk, reporter=reporter))
  File "d:\support\slicer_package_manager-venv\lib\site-packages\girder_client\__init__.py", line 479, in post
    data=data, json=json, headers=headers, jsonResp=jsonResp)
  File "d:\support\slicer_package_manager-venv\lib\site-packages\girder_client\__init__.py", line 465, in sendRestRequest
    response=result)
girder_client.HttpError: HTTP error 502: POST https://slicer-packages.kitware.com/api/v1/file/chunk?offset=134217728&uploadId=617104b3342a877cb3d2680d
Response text: <html>

<head><title>502 Bad Gateway</title></head>

<body bgcolor="white">

<center><h1>502 Bad Gateway</h1></center>

<hr><center>nginx</center>

</body>

</html>
1 Like

We could retry a few times, with increasingly longer delays (after 10sec, 30sec, 2, 5, 10 minutes), but it would be better to have a look at the nginx and girder logs to see if the root cause can be addressed. Maybe we hit some time limit (due to having more and more files stored on the server).

Extension packages are smaller, so maybe that’s why the issue comes up only for the Slicer installer upload.