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

Delete unused retry implementations #5909

Merged
merged 2 commits into from May 14, 2024

Conversation

stephanos
Copy link
Contributor

@stephanos stephanos commented May 11, 2024

What changed?

  • ConcurrentRetrier: deleted, not used anywhere
  • TwoPhaseRetryPolicy: deleted, not used anywhere
  • SystemClock: replaced with clock.TimeSource

Why?

Less code is good.

How did you test it?

Compiler.

Potential risks

Documentation

Is hotfix candidate?

@stephanos stephanos changed the title Delete unused retry policy Delete unused retry implementations May 11, 2024
@stephanos stephanos force-pushed the delete-unused-retry-policy branch 4 times, most recently from 2781c3a to 585aa13 Compare May 11, 2024 00:39
@stephanos stephanos marked this pull request as ready for review May 11, 2024 00:56
@stephanos stephanos requested a review from a team as a code owner May 11, 2024 00:56
@stephanos stephanos merged commit 814953b into temporalio:main May 14, 2024
42 checks passed
@stephanos stephanos deleted the delete-unused-retry-policy branch May 14, 2024 02:46
hazelkim052 added a commit that referenced this pull request May 14, 2024
<!-- Describe what has changed in this PR -->

- `ConcurrentRetrier`: deleted, not used anywhere
- `TwoPhaseRetryPolicy`: deleted, not used anywhere
- `SystemClock`: replaced with `clock.TimeSource`

<!-- Tell your future self why have you made these changes -->

Less code is good.

<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->

Compiler.

<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
hazelkim052 added a commit that referenced this pull request May 14, 2024
<!-- Describe what has changed in this PR -->

- `ConcurrentRetrier`: deleted, not used anywhere
- `TwoPhaseRetryPolicy`: deleted, not used anywhere
- `SystemClock`: replaced with `clock.TimeSource`

<!-- Tell your future self why have you made these changes -->

Less code is good.

<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->

Compiler.

<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
ychebotarev pushed a commit to ychebotarev/temporal that referenced this pull request May 16, 2024
## What changed?
<!-- Describe what has changed in this PR -->

- `ConcurrentRetrier`: deleted, not used anywhere
- `TwoPhaseRetryPolicy`: deleted, not used anywhere
- `SystemClock`: replaced with `clock.TimeSource`

## Why?
<!-- Tell your future self why have you made these changes -->

Less code is good.

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->

Compiler.

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
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.

None yet

2 participants