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

Gracefully shut down container when we want logs #392

Merged
merged 2 commits into from
Jun 10, 2022
Merged

Conversation

erikjohnston
Copy link
Member

This gives the container a chance to flush out any pending logs, otherwise we can end up with truncated logs.

This gives the container a chance to flush out any pending logs,
otherwise we can end up with truncated logs.
@erikjohnston erikjohnston requested review from kegsay and a team June 10, 2022 10:02
Copy link
Contributor

@squahtx squahtx left a comment

Choose a reason for hiding this comment

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

1 suggestion, otherwise looks good to me!

I wonder if homeservers might sometimes take more than a second to shut down. Synapse certainly does for production instances.

internal/docker/deployer.go Outdated Show resolved Hide resolved
@erikjohnston
Copy link
Member Author

1 suggestion, otherwise looks good to me!

I wonder if homeservers might sometimes take more than a second to shut down. Synapse certainly does for production instances.

Yeah, though I really only care about keeping them going long enough to flush the logs from the tests.

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

Successfully merging this pull request may close these issues.

2 participants