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

[Prism] Terminate Job with CancelFn instead of panic #31599

Merged

Conversation

damondouglas
Copy link
Contributor

@damondouglas damondouglas commented Jun 13, 2024

This PR closes #31338, refactoring engine.ElementManager Bundles method to receive a context.CancelCauseFunc so that the Job fails instead of panic. This allows us to associate failing validation tests with stuck jobs.


Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

  • Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
  • Update CHANGES.md with noteworthy changes.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

Build python source distribution and wheels
Python tests
Java tests
Go tests

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

@damondouglas damondouglas marked this pull request as ready for review June 13, 2024 23:53
@damondouglas
Copy link
Contributor Author

R: @lostluck

Copy link
Contributor

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control

@@ -22,6 +22,7 @@ import (
"container/heap"
"context"
"fmt"
"github.com/apache/beam/sdks/v2/go/pkg/beam/internal/errors"
Copy link
Contributor

Choose a reason for hiding this comment

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

This import is in the wrong group. Please put it in the group with the other sdk imports, not the standard library imports.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm so embarrassed. I'll fix it.

Copy link
Contributor

@lostluck lostluck left a comment

Choose a reason for hiding this comment

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

Approved after suggested changes.

If you're feeling ambitious, we can write a test that a contrived/bad elementmanager configuration pipeline will call the passed in cancel function when it gets there. For obvious reasons we didn't have a test for that yet.

@damondouglas
Copy link
Contributor Author

I wasn't successful creating a test case that simulates the behavior. I suspect as we fix other unsupported features, we might be able to reveal more what is going on. It's only one Java Test class and only one is it's methods. In the grand scheme of things, I'm ok moving on for now.

@damondouglas damondouglas merged commit e2d6246 into apache:master Jun 15, 2024
7 checks passed
@damondouglas damondouglas deleted the prism-panic-nonzero-element-error branch September 25, 2024 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug][Prism]: panic: nothing in progress and no refreshes with non zero pending elements
2 participants