|
Specified archive's content is too large
|
|
|
Unable to unpack archive
|
|
|
Symlinks are not allowed to be in the archive
|
|
|
The '%s' file is larger than expected
|
|
|
File '%s' is not allowed to be in the archive
|
|
|
Interactive tasks were disabled by server administrator
|
|
|
Required file '%s' is missing
|
|
|
Retrace Server
|
|
|
Welcome to Retrace Server
|
|
|
Retrace Server is a service that provides the possibility to analyze coredump and generate backtrace over network. You can find further information at Retrace Server's github:
|
|
|
Only the secure HTTPS connection is now allowed by the server. HTTP requests will be denied.
|
|
|
Both HTTP and HTTPS are allowed. Using HTTPS is strictly recommended because of security reasons.
|
|
|
The following releases are supported: %s
|
|
|
Your coredump is only kept on the server while the retrace job is running. Once the job is finished, the server keeps retrace log and backtrace. All the other data (including coredump) are deleted. The retrace log and backtrace are only accessible via unique task ID and password, thus no one (except the author) is allowed to view it. All the crash information (including backtrace) is deleted after %d hours of inactivity. No possibly private data are kept on the server any longer.
|
|
|
Your coredump is only used for retrace purposes. Server administrators are not trying to get your private data from coredumps or backtraces. Using a secure communication channel (HTTPS) is strictly recommended. Server administrators are not responsible for the problems related to the usage of an insecure channel (such as HTTP).
|
|
|
At the moment the server is loaded for %d%% (running %d out of %d jobs).
|
|
|
There is no log for the specified task
|
|
|
Architecture
|
|
|
Architectures
|
|
|
Build-id
|
|
