cobalt/web/i18n/en/error/queue.json
wukko 77e78d55fc
web/workers/fetch: catch network-related errors & retry 3 times
previously all network issues showed a "worker crashed" error, which people misinterpreted all the time, and reasonably so
2025-06-07 11:46:16 +06:00

20 lines
1.0 KiB
JSON

{
"no_final_file": "no final file output",
"worker_didnt_start": "couldn't start a processing worker",
"fetch.crashed": "fetch worker crashed, see console for details",
"fetch.bad_response": "couldn't access the file tunnel",
"fetch.no_file_reader": "couldn't write a file to cache",
"fetch.empty_tunnel": "file tunnel is empty, try again in a few minutes",
"fetch.corrupted_file": "file wasn't downloaded fully, try again",
"fetch.network_error": "downloading was interrupted by a network issue",
"ffmpeg.probe_failed": "couldn't probe this file, it may be unsupported or corrupted",
"ffmpeg.out_of_memory": "not enough available memory, can't continue",
"ffmpeg.no_input_format": "the file's format isn't supported",
"ffmpeg.no_input_type": "the file's type isn't supported",
"ffmpeg.crashed": "ffmpeg worker crashed, see console for details",
"ffmpeg.no_render": "ffmpeg render is empty, something very odd happened",
"ffmpeg.no_args": "ffmpeg worker didn't get required arguments"
}