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

Sync retry option with spec #6834

Merged
merged 2 commits into from
Apr 5, 2023
Merged

Conversation

Rahul-Kumar-prog
Copy link
Contributor

@Rahul-Kumar-prog Rahul-Kumar-prog commented Apr 3, 2023

Fixes #6691

Proposed Changes

change imc dispatcher's retry option form RetryGreaterThen300 to SelectiveRetry

Pre-review Checklist

  • At least 80% unit test coverage
  • E2E tests for any new behavior
  • Docs PR for any user-facing impact
  • Spec PR for any new API feature
  • Conformance test for any change to the spec

Release Note


Docs

Debug Test Image

Screenshot 2023-04-03 at 4 32 59 PM

@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Apr 3, 2023

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: Rahul-Kumar-prog / name: Rahul kumar (3818358)

@knative-prow
Copy link

knative-prow bot commented Apr 3, 2023

Welcome @Rahul-Kumar-prog! It looks like this is your first PR to knative/eventing 🎉

@knative-prow knative-prow bot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Apr 3, 2023
@knative-prow
Copy link

knative-prow bot commented Apr 3, 2023

Hi @Rahul-Kumar-prog. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@@ -83,7 +83,7 @@ func RetryConfigFromDeliverySpec(spec v1.DeliverySpec) (RetryConfig, error) {

retryConfig := NoRetries()

retryConfig.CheckRetry = RetryIfGreaterThan300
Copy link
Member

@pierDipi pierDipi Apr 3, 2023

Choose a reason for hiding this comment

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

Is RetryIfGreaterThan300 function used somewhere? Can we remove it?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

sorry I accidentally add the RetryIfGreaterThan300 test screen short

Screenshot 2023-04-03 at 4 32 59 PM

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is the correct one.

Copy link
Member

Choose a reason for hiding this comment

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

Ok, if the function RetryIfGreaterThan300 is only used in tests, we should remove it

Copy link
Member

Choose a reason for hiding this comment

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

The reason being, if the function is not useful to production code, we don't need it anymore and we should remove it

Copy link
Contributor Author

Choose a reason for hiding this comment

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

so I need to remove the RetryIfGreaterThen300 entirely ?

Copy link
Member

@pierDipi pierDipi Apr 4, 2023

Choose a reason for hiding this comment

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

It depends if it is still used and where in the codebase, have you found the places where the RetryIfGreaterThen300 function is used in your branch?

@knative-prow knative-prow bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Apr 4, 2023
@pierDipi
Copy link
Member

pierDipi commented Apr 4, 2023

/ok-to-test

@knative-prow knative-prow bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Apr 4, 2023
@codecov
Copy link

codecov bot commented Apr 4, 2023

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (f6ca59b) 80.45% compared to head (32030d8) 80.45%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #6834   +/-   ##
=======================================
  Coverage   80.45%   80.45%           
=======================================
  Files         236      236           
  Lines       12213    12235   +22     
=======================================
+ Hits         9826     9844   +18     
- Misses       1896     1899    +3     
- Partials      491      492    +1     
Impacted Files Coverage Δ
pkg/kncloudevents/retries.go 100.00% <100.00%> (ø)

... and 2 files with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@Rahul-Kumar-prog
Copy link
Contributor Author

/test upgrade-tests

Copy link
Member

@pierDipi pierDipi left a comment

Choose a reason for hiding this comment

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

Thanks @Rahul-Kumar-prog

/lgtm
/approve

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Apr 5, 2023
@knative-prow
Copy link

knative-prow bot commented Apr 5, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pierDipi, Rahul-Kumar-prog

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 5, 2023
@pierDipi
Copy link
Member

pierDipi commented Apr 5, 2023

/test upgrade-tests

@knative-prow knative-prow bot merged commit 642699b into knative:main Apr 5, 2023
21 of 30 checks passed
vishal-chdhry pushed a commit to vishal-chdhry/eventing that referenced this pull request Apr 25, 2023
Fixes knative#6691 

## Proposed Changes
change imc dispatcher's retry option form `RetryGreaterThen300` to
`SelectiveRetry`

### Pre-review Checklist

<!-- If these boxes are not checked, you will be asked to complete these
requirements or explain why they do not apply to your PR. -->

- [ ] **At least 80% unit test coverage**
- [ ] **E2E tests** for any new behavior
- [ ] **Docs PR** for any user-facing impact
- [ ] **Spec PR** for any new API feature
- [ ] **Conformance test** for any change to the spec

**Release Note**

<!--
:page_facing_up: If this change has user-visible impact, write a release
note in the block
below. Include the string "action required" if additional action is
required of
users switching to the new release, for example in case of a breaking
change.

Write as if you are speaking to users, not other Knative contributors.
If this
change has no user-visible impact, no release note is needed.
-->

```release-note

```


**Docs**

<!--
:book: If this change has user-visible impact, link to an issue or PR in
https://github.com/knative/docs.
-->

**Debug Test Image**

<img width="1270" alt="Screenshot 2023-04-03 at 4 32 59 PM"
src="https://user-images.githubusercontent.com/68837569/229492305-1cd9b042-5794-4268-b403-b97d28bfe7f5.png">
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

imc-channel's retry option is different with the spec
2 participants