-
Notifications
You must be signed in to change notification settings - Fork 624
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
[release-4.9] Bug 2084028: Improve Firehose cache, so that it does not return unexpected data also if isList differs on two concurrent calls #11476
Conversation
@jerolimov: This pull request references Bugzilla bug 2084028, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 6 validation(s) were run on this bug
Requesting review from QA contact: 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/test-infra repository. |
…e in hooks" This reverts commit 5881b3d.
Incl. tests which shows the bug #2069621 (without a fix here)
when requesting this data as list (data.toArray().map(item => item.toJSON) or single object (data.toJSON()) so that different usages of isList for the same data doesn't effect a 2nd component.
496f0aa
to
d859458
Compare
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.
Tested on cluster, firehose calls work as expected and caching still works without issues.
Code changes also look good.
/lgtm
0.mp4
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jerolimov, rottencandy 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 |
/label backport-risk-assessed |
/label cherry-pick-approved |
@jerolimov: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
@jerolimov: All pull requests linked via external trackers have merged: Bugzilla bug 2084028 has been moved to the MODIFIED state. 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/test-infra repository. |
/cherry-pick release-4.8 |
@jerolimov: #11476 failed to apply on top of branch "release-4.8":
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/test-infra repository. |
Fixes:
https://bugzilla.redhat.com/show_bug.cgi?id=2084028
Revert hot-fix #11256 and manual backport of #11382 for 4.9