-
Notifications
You must be signed in to change notification settings - Fork 117
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
fix: knative kafka extensions are short enough to meet the SHOULD req in spec #3994
fix: knative kafka extensions are short enough to meet the SHOULD req in spec #3994
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3994 +/- ##
=======================================
Coverage 48.15% 48.15%
=======================================
Files 246 246
Lines 14517 14517
=======================================
Hits 6990 6990
Misses 6821 6821
Partials 706 706 ☔ View full report in Codecov by Sentry. |
… in spec Signed-off-by: Calum Murray <[email protected]>
cbcd8c7
to
ce44054
Compare
/retest |
@@ -46,7 +46,7 @@ private void applyCloudEventOverrides(CloudEventBuilder builder) { | |||
} | |||
|
|||
private void applyKafkaMetadata(CloudEventBuilder builder, Number partition, Number offset) { | |||
builder.withExtension("knativekafkapartition", partition); | |||
builder.withExtension("knativekafkaoffset", offset); | |||
builder.withExtension("knkafkapartition", partition); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Cali0707 can you check w/ the Java SDK why it is not failing on 20+ chars?
(and maybe double check w/ golang)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
/hold
this seems breaking change. should we do something there? Or is release-notes good enought (I guess it is good enought). Just wondering
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Cali0707, matzew 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 |
@Cali0707: The following test failed, say
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-sigs/prow repository. I understand the commands that are listed here. |
/hold I'm worried this will break users, given that it is a should is it really worth it? I think the JS SDK should not throw for this as it's a |
Sure, let me try opening a PR to the SDK to fix that |
I opened cloudevents/sdk-javascript#593 |
@Cali0707 closing. the fix in JS seems better addressing this /close |
@matzew: Closed this PR. In response to this:
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-sigs/prow repository. |
Fixes #3992
Proposed Changes
Release Note