Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash report #969

Closed
tecosaur opened this issue Jun 27, 2024 · 2 comments
Closed

Crash report #969

tecosaur opened this issue Jun 27, 2024 · 2 comments

Comments

@tecosaur
Copy link

So, I've just seen a fun message

Well, this is embarrassing.

Juliaup had a problem and crashed. To help us diagnose the problem you can send us a crash report.

We have generated a report file at "/tmp/report-e764e12c-6321-4a4a-84a7-322b01ee5731.toml". Submit an issue or email with the subject of "Juliaup Crash Report" and include the report as an attachment.

Here's the report.toml

"name" = "Juliaup"
"operating_system" = "openSUSE 20240622.0.0 [64-bit]"
"crate_version" = "1.14.9"
"explanation" = """
Panic occurred in file 'src/operations.rs' at line 1348
"""
"cause" = 'called `Result::unwrap()` on an `Err` value: reqwest::Error { kind: Request, url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("julialangnightlies-s3.julialang.org")), port: None, path: "/bin/linux/x86_64/julia-latest-linux-x86_64.tar.gz", query: None, fragment: None }, source: TimedOut }'
"method" = "Panic"
"backtrace" = """

   0: 0x55653c7a35db - <core::iter::adapters::filter_map::FilterMap<I,F> as core::iter::traits::iterator::Iterator>::next::h78f74617b54029c4
   1: 0x55653c76c6fb - juliaup::operations::update_version_db::h274b42a72bdd9265
   2: 0x55653c660db5 - juliaup::main::h990f1ce64d381b81
   3: 0x55653c6575e3 - std::sys_common::backtrace::__rust_begin_short_backtrace::he7973c5422ce3954
   4: 0x55653c66d7ef - main
   5: 0x7f4cf282a1f0 - __libc_start_call_main
   6: 0x7f4cf282a2b9 - __libc_start_main@GLIBC_2.2.5
   7: 0x55653c652279 - _start
   8:        0x0 - <unresolved>"""

Good luck!

@Gambitier
Copy link
Contributor

the error is because of client side http timeout. Fixed recently with #951

@LilithHafner
Copy link
Member

Please re-open if this persists once #951 is released

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants