Skip to content

Conversation

@intojhanurag
Copy link
Member

@intojhanurag intojhanurag commented Nov 16, 2025

Propagates the ReadTimeout option from InMemoryEventDispatcherArgs to
the underlying HTTPEventReceiver. The dispatcher previously created a
receiver without setting its ReadTimeout, despite the TODO in the code.

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

knative-prow bot commented Nov 16, 2025

Hi @intojhanurag. Thanks for your PR.

I'm waiting for a github.com 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.

Details

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.

@knative-prow knative-prow bot requested review from Cali0707 and creydr November 16, 2025 19:28
@intojhanurag
Copy link
Member Author

Hey @Cali0707 , Do you think , Is it good to go? Please take a look if you have a moment.

@Cali0707
Copy link
Member

Hey @intojhanurag - this seems to be the same change as you proposed in #8786 originally. In general, when making updates to a set of changes you've already submitted as a PR you should update the existing PR rather than opening a new one. That helps everyone understand the history and context behind the change

Copy link
Member

@Cali0707 Cali0707 left a comment

Choose a reason for hiding this comment

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

Thanks @intojhanurag for this - this looks good overall.

I have one small nit on the code itself, otherwise just keep in mind my comment about trying to keep changes in the same PR and not opening new ones in the future 😄

@Cali0707
Copy link
Member

/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 Nov 17, 2025
@codecov
Copy link

codecov bot commented Nov 17, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 51.11%. Comparing base (161a91a) to head (a75fa64).
⚠️ Report is 12 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #8790   +/-   ##
=======================================
  Coverage   51.10%   51.11%           
=======================================
  Files         409      409           
  Lines       21356    21360    +4     
=======================================
+ Hits        10915    10919    +4     
  Misses       9589     9589           
  Partials      852      852           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@intojhanurag
Copy link
Member Author

My bad 😭! I reopened a new PR because the previous one slipped my mind. While exploring the repo again, I noticed the same issue and ended up creating a new PR unintentionally.

@intojhanurag
Copy link
Member Author

intojhanurag commented Nov 19, 2025

Hey @creydr , Can you review this one please ?

Copy link
Member

@creydr creydr left a comment

Choose a reason for hiding this comment

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

Thanks for working on this @intojhanurag

I only left a tiny comment

@intojhanurag
Copy link
Member Author

Hey @creydr , Please can you point out why these tests are failing after new changes ?

@creydr
Copy link
Member

creydr commented Nov 21, 2025

Hey @creydr , Please can you point out why these tests are failing after new changes ?

Its a build issue. The code doesn't compile. Seems #8790 (comment) was too simple. We probably need something like

	bindingsReceiver := kncloudevents.NewHTTPEventReceiver(
		args.Port,
		append(
			[]kncloudevents.HTTPEventReceiverOption{
				kncloudevents.WithReadTimeout(args.ReadTimeout),
			},
			args.HTTPEventReceiverOptions...)...,
	)

@intojhanurag
Copy link
Member Author

intojhanurag commented Nov 21, 2025

Hey @creydr , Now Is it good to go ? Again one test is failing

@creydr
Copy link
Member

creydr commented Nov 22, 2025

/retest-required

@creydr
Copy link
Member

creydr commented Nov 24, 2025

/test reconciler-tests

1 similar comment
@creydr
Copy link
Member

creydr commented Nov 24, 2025

/test reconciler-tests

Copy link
Member

@creydr creydr left a comment

Choose a reason for hiding this comment

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

/lgtm

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Nov 25, 2025
@knative-prow
Copy link

knative-prow bot commented Nov 25, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: creydr, intojhanurag

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

The pull request process is described here

Details 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 Nov 25, 2025
@creydr
Copy link
Member

creydr commented Nov 25, 2025

/retest-required

@knative-prow knative-prow bot merged commit 6ae393a into knative:main Nov 25, 2025
36 checks passed
@intojhanurag
Copy link
Member Author

Thanks @creydr

@creydr
Copy link
Member

creydr commented Nov 25, 2025

Finally 😄 Thanks @intojhanurag for your patience!

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/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants