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.

Sign up for GitHub

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

Jump to bottom

Export succeeding but ugly exit: thread 'main' panicked at 'there is no reactor running, must be called from the context of a Tokio 1.x runtime #565

Closed
joepio opened this issue Jan 24, 2023 · 1 comment
Closed

Export succeeding but ugly exit: thread 'main' panicked at 'there is no reactor running, must be called from the context of a Tokio 1.x runtime #565

joepio opened this issue Jan 24, 2023 · 1 comment

Comments

@joepio
Copy link
Member

joepio commented Jan 24, 2023 •
edited
Loading

When running cargo run -- export on main, I get:

Succesfully exported data to /Users/joep/.config/atomic/backups/2023-01-24T10:20:30.426230+01:00.json
thread 'main' panicked at 'there is no reactor running, must be called from the context of a Tokio 1.x runtime', /Users/joep/.cargo/registry/src/github.com-1ecc6299db9ec823/actix-0.13.0/src/utils.rs:186:20
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
@joepio joepio changed the title Export failing: thread 'main' panicked at 'there is no reactor running, must be called from the context of a Tokio 1.x runtime Export succeeding but ugly exit: thread 'main' panicked at 'there is no reactor running, must be called from the context of a Tokio 1.x runtime Jan 24, 2023
joepio added a commit that referenced this issue Jan 24, 2023
@joepio
Fix errors on succesful export / import #565
4e7a7a6
@joepio
Copy link
Member Author

joepio commented Jan 24, 2023 •
edited
Loading

Adding a std::process::exit(0); fixed the issue

@joepio joepio closed this as completed Jan 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@joepio