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

"this is an internal issue with celeste and should be reported" #176

Open
donbright opened this issue Nov 20, 2023 · 11 comments
Open

"this is an internal issue with celeste and should be reported" #176

donbright opened this issue Nov 20, 2023 · 11 comments

Comments

@donbright
Copy link

thread 'main' panicked at src/launch.rs:2406:33:
internal error: entered unreachable code
stack backtrace:

(yes the backtrace was literally blank)

@hwittenborn
Copy link
Owner

Hey @donbright, I'm pretty sure the lack of a backtrace is due to some internal logic for how Celeste captures backtraces (I'm not positive, but you're not the first person to have a blank backtrace).

Would there be any chance you're using Google Drive to sync your files? That's where I've been seeing this issue in the past.

@vcarel
Copy link

vcarel commented Nov 27, 2023

Hi, I just tried to sync Google Drive from scratch and I got the same error. Empty stacktrace too.

@johnblommers
Copy link

I just installed Celeste and setup Google Drive, pCloud and Dropbox. After a while, I also get this unknown error, though in a different place:

thread 'main' panicked at src/launch.rs:2020:54:
called `Option::unwrap()` on a `None` value
stack backtrace:

no backtrace.

@yy00ch
Copy link

yy00ch commented Dec 19, 2023

Just reporting that I've encountered a similar issue when I tried to sync google drive on pop os.

thread 'main' panicked at src/launch.rs:2406:33: internal error: entered unreachable code stack backtrace:

@Gotterbild
Copy link

First, thanks for you work! I know how to use rclone, but having a nice native GUI always feels better.

Just got the same error with Proton, no backtrace:

thread 'main' panicked at src/launch.rs:1882:34:
called `Option::unwrap()` on a `None` value
stack backtrace:

I was syncing two folders, one of which is ~75MB and 920 files and the other one is 2MB, 5 files.

I should say the sync process is pretty slow as first folder was checking for more than 10 hours. Maybe more. And I'm not positive if it finished and on which sync step the error happened.

With direct use of rclone the process was way way faster, even with defaults. By default rclone uses 4 threads and it seems Celeste using only one. Would be nice to have ability to set --multi-thread-streams as you want per service.

@donbright
Copy link
Author

@hwittenborn yup, was using Google Drive from linux mint. Thanks.

@diogotcorreia
Copy link

Just got this as well. Also Google Drive.
Is there any information I could provide that would help with the issue?

@diogotcorreia
Copy link

Update: Instead of running with flatpak, I'm now running with the package from Nixpkgs.
It apparently shows the stack trace now, which might by useful:

thread 'main' panicked at src/launch.rs:2406:33:
internal error: entered unreachable code
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::panicking::panic
   3: celeste::launch::launch::sync_remote_directory
   4: celeste::launch::launch::sync_remote_directory::{{closure}}
   5: celeste::launch::launch::sync_remote_directory
   6: celeste::launch::launch::sync_remote_directory::{{closure}}
   7: celeste::launch::launch::sync_remote_directory
   8: celeste::launch::launch::sync_remote_directory::{{closure}}
   9: celeste::launch::launch::sync_remote_directory
  10: celeste::launch::launch::sync_remote_directory::{{closure}}
  11: celeste::launch::launch::sync_remote_directory
  12: celeste::launch::launch::sync_remote_directory::{{closure}}
  13: celeste::launch::launch::sync_remote_directory
  14: celeste::launch::launch
  15: <O as gio::auto::application::ApplicationExt>::connect_activate::activate_trampoline
  16: g_closure_invoke
  17: signal_emit_unlocked_R.isra.0
  18: signal_emit_valist_unlocked
  19: g_signal_emit_valist
  20: g_signal_emit
  21: g_application_real_local_command_line
  22: g_application_run
  23: <O as gio::application::ApplicationExtManual>::run_with_args
  24: celeste::main

@diogotcorreia
Copy link

I've built Celeste locally and added some dbg! prints and found out that this issue is caused by duplicate file names in Google Drive (i.e., GDrive allows you to have two distinct files with the same name).
image
image

@hwittenborn
Copy link
Owner

Thanks for the information @diogotcorreia! Do you have two files with the same name on your Google Drive in your case then?

@diogotcorreia
Copy link

@hwittenborn I have indeed 🙃
I've left more information and reproducible steps in #193

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

7 participants