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

[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

@openshift-ci openshift-ci bot added bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels May 11, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 11, 2022

@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
  • bug is open, matching expected state (open)
  • bug target release (4.9.z) matches configured target release for branch (4.9.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2077641 is in the state RELEASE_PENDING, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2077641 targets the "4.10.z" release, which is one of the valid target releases: 4.10.0, 4.10.z
  • bug has dependents

Requesting review from QA contact:
/cc @sanketpathak

In response to this:

[release-4.10] Bug 2084028: Improve Firehose cache, so that it does not return unexpected data also if isList differs on two concurrent calls

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.

@christoph-jerolimov christoph-jerolimov changed the title [release-4.10] Bug 2084028: Improve Firehose cache, so that it does not return unexpected data also if isList differs on two concurrent calls [release-4.9] Bug 2084028: Improve Firehose cache, so that it does not return unexpected data also if isList differs on two concurrent calls May 11, 2022
@openshift-ci openshift-ci bot added component/core Related to console core functionality component/dev-console Related to dev-console labels May 11, 2022
@christoph-jerolimov
Copy link
Member Author

/cc @rottencandy @invincibleJai

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 11, 2022
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.
@christoph-jerolimov christoph-jerolimov force-pushed the tojson-cache-improvements-4.9 branch from 496f0aa to d859458 Compare May 11, 2022 13:52
Copy link
Contributor

@rottencandy rottencandy left a 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

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 11, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 11, 2022

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@christoph-jerolimov
Copy link
Member Author

/label backport-risk-assessed
/cc @sanketpathak

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label May 16, 2022
@sanketpathak
Copy link
Contributor

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label May 17, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 17, 2022

@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.

@openshift-merge-robot openshift-merge-robot merged commit bd45974 into openshift:release-4.9 May 17, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 17, 2022

@jerolimov: All pull requests linked via external trackers have merged:

Bugzilla bug 2084028 has been moved to the MODIFIED state.

In response to this:

[release-4.9] Bug 2084028: Improve Firehose cache, so that it does not return unexpected data also if isList differs on two concurrent calls

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.

@christoph-jerolimov
Copy link
Member Author

/cherry-pick release-4.8

@openshift-cherrypick-robot

@jerolimov: #11476 failed to apply on top of branch "release-4.8":

Applying: Revert "return process data as array for list true in firehose as done in hooks"
Using index info to reconstruct a base tree...
M	frontend/public/components/utils/__tests__/firehose.spec.tsx
M	frontend/public/components/utils/firehose.jsx
Falling back to patching base and 3-way merge...
Auto-merging frontend/public/components/utils/__tests__/firehose.spec.tsx
No changes -- Patch already applied.
Applying: Add unit tests to test Firehose and useK8sWatchResources together
Using index info to reconstruct a base tree...
M	frontend/public/components/utils/__tests__/firehose.spec.tsx
Falling back to patching base and 3-way merge...
Auto-merging frontend/public/components/utils/__tests__/firehose.spec.tsx
CONFLICT (content): Merge conflict in frontend/public/components/utils/__tests__/firehose.spec.tsx
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0002 Add unit tests to test Firehose and useK8sWatchResources together
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.8

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.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. component/core Related to console core functionality component/dev-console Related to dev-console lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants