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

Remove unnecessary error from retryOnTimeoutActivity #6256

Conversation

fimanishi
Copy link
Contributor

What changed?
Removed unnecessary error from retryOnTimeoutActivity from canary/retry.go workflow

Why?
The error was introduced because there was a bug in the service that would allow completion from a previous attempt. The bug has been corrected.

How did you test it?
Executed the workflow without the error and confirmed that it completed successfully.

Potential risks

Release notes

Documentation Changes

What changed?
Removed unnecessary error from retryOnTimeoutActivity from canary/retry.go workflow

Why?
The error was introduced because there was a bug in the service that would allow completion from a previous attempt. The bug has been corrected.

How did you test it?
Executed the workflow without the error and confirmed that it completed successfully.

Potential risks

Release notes

Documentation Changes
Copy link

codecov bot commented Aug 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.01%. Comparing base (6ba8ad8) to head (ad49026).
Report is 2 commits behind head on master.

Additional details and impacted files

see 8 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6ba8ad8...ad49026. Read the comment docs.

@fimanishi fimanishi merged commit 1b02d78 into uber:master Aug 28, 2024
20 checks passed
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