When running data table backup code via uplink that has worked before, I’ve started to get an internal server error when calling media.get_bytes()
. I haven’t run the backup for a few months, so I can’t say exactly when it stopped working. The error happens on the very first call to media.get_bytes()
.
I updated anvil-uplink
to the latest version, but the internal error is still happening.
I’m hoping the internal error codes are logged somewhere that Anvil staff can get to, with more information about what caused the error. Nothing is showing in the app logs other than the successful uplink connection.
Here’s the stack track where the issue happened, starting at the call to get_bytes()
:
obj.get_bytes(),
File "C:\Users\jshaf\AppData\Roaming\Python\Python37\site-packages\anvil\_server.py", line 482, in get_bytes
return self._fetch().get_bytes()
File "C:\Users\jshaf\AppData\Roaming\Python\Python37\site-packages\anvil\_server.py", line 451, in _fetch
self._fetched = anvil.server.call("anvil.private.fetch_lazy_media", self._spec)
File "C:\Users\jshaf\AppData\Roaming\Python\Python37\site-packages\anvil\server.py", line 403, in call
return _do_call(args, kwargs, fn_name=fn_name)
File "C:\Users\jshaf\AppData\Roaming\Python\Python37\site-packages\anvil\server.py", line 395, in _do_call
return _threaded_server.do_call(args, kwargs, fn_name=fn_name, live_object=live_object)
File "C:\Users\jshaf\AppData\Roaming\Python\Python37\site-packages\anvil\_threaded_server.py", line 435, in do_call
raise error_from_server
anvil._server.InternalError: Internal server error: efe436385a6e
Accelerated tables is off for this app, if that makes a difference.