Skip to content

[wip] make resource init failures result in step retries #29619

New issue

Have a question about this project? No Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “No 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? No Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

OwenKephart
Copy link
Contributor

Summary & Motivation

this does not work at all, just trying to narrow in on a potential solution

How I Tested These Changes

Changelog

Insert changelog entry or delete this section.

Copy link
Contributor Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

Comment on lines +273 to +274
SerializableErrorInfo("", [], ""),
active_execution.get_known_state(),
Copy link
Contributor

Choose a reason for hiding this comment

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

The empty SerializableErrorInfo("", [], "") will cause issues with the retry mechanism. The get_failure_or_retry_event_after_crash method relies on this error information to determine retry behavior and generate appropriate failure reports.

Consider extracting the actual error details from the resource initialization failure event instead. This would ensure the retry logic has complete information to make correct decisions about whether to retry the step and how to report the failure to users.

# Extract error info from the resource init failure event
error_info = event_or_none.event_specific_data.error
Suggested change
SerializableErrorInfo("", [], ""),
active_execution.get_known_state(),
event_or_none.event_specific_data.error,
active_execution.get_known_state(),

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

No Sign up for free to join this conversation on GitHub. Already have an account? No Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant