Skip to content

Conversation

@vikram-raj
Copy link
Member

The createHash function has been used from the crypto package, which causes the console to break with a TypeError.

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 26, 2025
@openshift-ci-robot
Copy link
Contributor

@vikram-raj: This pull request references Jira Issue OCPBUGS-60886, which is invalid:

  • expected the bug to target the "4.20.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

The createHash function has been used from the crypto package, which causes the console to break with a TypeError.

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 openshift-eng/jira-lifecycle-plugin repository.

@vikram-raj
Copy link
Member Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 26, 2025
@openshift-ci-robot
Copy link
Contributor

@vikram-raj: This pull request references Jira Issue OCPBUGS-60886, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.0) matches configured target version for branch (4.20.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @yapei

Details

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added component/dev-console Related to dev-console component/shared Related to console-shared approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Aug 26, 2025
@@ -1,5 +1,5 @@
import { createHash } from 'crypto';
import { useMemo } from 'react';
import { createHash } from 'crypto-browserify';
Copy link
Member

Choose a reason for hiding this comment

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

per OCPBUGS-44505 we are trying to remove crypto-browserify. can you try using the window.crypto object?

Copy link
Member Author

Choose a reason for hiding this comment

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

Sure, I wasn't aware of that. Thanks.

Copy link
Contributor

Choose a reason for hiding this comment

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

I need to revisit that, still hasn't figured out the CI failures after the migration to window.crypto

@logonoff
Copy link
Member

/retitle OCPBUGS-60886: use window.crypto from useGetUserSettingConfigMap
/label tide/merge-method-squash

@openshift-ci openshift-ci bot changed the title OCPBUGS-60886: import createHash from crypto-browserify OCPBUGS-60886: use window.crypto from useGetUserSettingConfigMap Sep 18, 2025
@openshift-ci openshift-ci bot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Sep 18, 2025
@logonoff
Copy link
Member

/retitle OCPBUGS-60886: use window.crypto in useGetUserSettingConfigMap

@openshift-ci openshift-ci bot changed the title OCPBUGS-60886: use window.crypto from useGetUserSettingConfigMap OCPBUGS-60886: use window.crypto in useGetUserSettingConfigMap Sep 18, 2025
Copy link
Member

@logonoff logonoff left a comment

Choose a reason for hiding this comment

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

/verified by useGetUserSettingConfigMap.spec.ts
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 18, 2025
@logonoff
Copy link
Member

/verified by useGetUserSettingConfigMap.spec.ts

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 18, 2025
@openshift-ci-robot
Copy link
Contributor

@logonoff: This PR has been marked as verified by useGetUserSettingConfigMap.spec.ts.

Details

In response to this:

/verified by useGetUserSettingConfigMap.spec.ts

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 6098ca4 and 2 for PR HEAD d3082df in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 6efa508 and 1 for PR HEAD d3082df in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 6efa508 and 2 for PR HEAD d3082df in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 11d1f43 and 1 for PR HEAD d3082df in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD b16f659 and 0 for PR HEAD d3082df in total

@openshift-ci-robot
Copy link
Contributor

/hold

Revision d3082df was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 20, 2025
@vikram-raj
Copy link
Member Author

/retest

3 similar comments
@vikram-raj
Copy link
Member Author

/retest

@vikram-raj
Copy link
Member Author

/retest

@vikram-raj
Copy link
Member Author

/retest

@vikram-raj
Copy link
Member Author

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 14, 2025
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 9ec1a9d and 2 for PR HEAD d3082df in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 85c59f9 and 1 for PR HEAD d3082df in total

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 15, 2025
@openshift-ci-robot openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label Oct 15, 2025
@vikram-raj vikram-raj requested a review from logonoff October 15, 2025 15:08
@logonoff
Copy link
Member

/verified by useGetUserSettingConfigMap.spec.ts
/lgtm

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 15, 2025
@openshift-ci-robot
Copy link
Contributor

@logonoff: This PR has been marked as verified by useGetUserSettingConfigMap.spec.ts.

Details

In response to this:

/verified by useGetUserSettingConfigMap.spec.ts
/lgtm

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 15, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 15, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: logonoff, vikram-raj

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 15, 2025

@vikram-raj: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit a991638 into openshift:main Oct 15, 2025
8 checks passed
@openshift-ci-robot
Copy link
Contributor

@vikram-raj: Jira Issue Verification Checks: Jira Issue OCPBUGS-60886
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-60886 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

The createHash function has been used from the crypto package, which causes the console to break with a TypeError.

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 openshift-eng/jira-lifecycle-plugin repository.

Leo6Leo pushed a commit to Leo6Leo/console that referenced this pull request Oct 15, 2025
…penshift#15432)

* import createHash from crypto-browserify

* use window.crypto

* fix e2e add-flow-ci.feature
@vikram-raj vikram-raj deleted the ocpbugs-60886 branch October 22, 2025 13:20
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. component/dev-console Related to dev-console component/shared Related to console-shared jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants