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

Try to recover when the main process fails #634

Merged
merged 2 commits into from
Oct 27, 2022

Conversation

XAMPPRocky
Copy link
Collaborator

Fixes spurious errors like #626

fixes #626

Commands::Manage(manager) => tokio::spawn(async move { manager.manage(config).await }),
Commands::GenerateConfigSchema(generator) => {
tokio::spawn(std::future::ready(generator.generate_config_schema()))
let fut = tryhard::retry_fn({
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shall we warn a log on retry?

@XAMPPRocky XAMPPRocky force-pushed the ep/recover-when-main-fails branch from dad40b0 to 7bfc423 Compare October 27, 2022 10:29
@quilkin-bot
Copy link
Collaborator

Build Succeeded 🥳

Build Id: dc33e41f-80f5-4303-ab39-96edf54b9afd

The following development images have been built, and will exist for the next 30 days:

To build this version:

git fetch git@github.com:googleforgames/quilkin.git pull/634/head:pr_634 && git checkout pr_634
cargo build

@markmandel markmandel merged commit 53ec116 into main Oct 27, 2022
@markmandel markmandel deleted the ep/recover-when-main-fails branch October 27, 2022 17:46
@markmandel markmandel added kind/bug Something isn't working area/user-experience Pertaining to developers trying to use Quilkin, e.g. cli interface, configuration, etc labels Nov 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/user-experience Pertaining to developers trying to use Quilkin, e.g. cli interface, configuration, etc kind/bug Something isn't working size/s
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fatal error from too old resource version
3 participants