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

Do not stop REST API before outputs are flushed #4276

Merged
merged 1 commit into from
Jan 24, 2025

Conversation

mstoykov
Copy link
Contributor

What?

Do not stop REST API until flushing outputs is done

Why?

Flushing outputs may take some time and it will be good if the REST API is up for this - there is no need for it not to be.

Checklist

  • I have performed a self-review of my code.
  • I have added tests for my changes.
  • I have run linter locally (make lint) and all checks pass.
  • I have run tests locally (make tests) and all tests pass.
  • I have commented on my code, particularly in hard-to-understand areas.

Related PR(s)/Issue(s)

@mstoykov mstoykov added this to the v0.57.0 milestone Jan 24, 2025
@mstoykov mstoykov requested a review from a team as a code owner January 24, 2025 10:08
@mstoykov mstoykov requested review from ankur22 and codebien and removed request for a team January 24, 2025 10:08
Copy link
Contributor

@ankur22 ankur22 left a comment

Choose a reason for hiding this comment

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

What i understand is that the REST API will close after the outputs are flushed due to the change in ordering of the defer.

LGTM

@mstoykov mstoykov merged commit 454253f into master Jan 24, 2025
28 checks passed
@mstoykov mstoykov deleted the restAPIUntilOutputsFlushed branch January 24, 2025 10:41
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.

3 participants