Skip to content

Conversation

@yehudit1987
Copy link

@yehudit1987 yehudit1987 commented Sep 30, 2025

@github-project-automation github-project-automation bot moved this to Needs Triage in Kubeflow Notebooks Sep 30, 2025
@google-oss-prow google-oss-prow bot added the area/ci area - related to ci label Sep 30, 2025
@yehudit1987 yehudit1987 force-pushed the feat/migrate_twa_tests branch 3 times, most recently from 01e48e4 to a5bfa91 Compare October 5, 2025 08:41
@google-oss-prow google-oss-prow bot added area/backend area - related to backend components area/frontend area - related to frontend components area/v1 area - version - kubeflow notebooks v1 size/XXL and removed size/L labels Oct 5, 2025
@yehudit1987 yehudit1987 force-pushed the feat/migrate_twa_tests branch 3 times, most recently from 8b9b78f to 28f1111 Compare October 5, 2025 09:00
@yehudit1987 yehudit1987 marked this pull request as ready for review October 5, 2025 10:46
@google-oss-prow google-oss-prow bot requested a review from orfeas-k October 5, 2025 10:46
Copy link
Contributor

@andyatmiami andyatmiami left a comment

Choose a reason for hiding this comment

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

Really nice investigations/implementations here @yehudit1987 - but for the immediate needs of notebooks-v1 migration - I would prefer we dial back some of these changes to align more with the "status quo" of how kubeflow/kubeflow implemented these workflows.

@yehudit1987 yehudit1987 force-pushed the feat/migrate_twa_tests branch 2 times, most recently from 2615d17 to a97625b Compare October 15, 2025 09:05
@yehudit1987 yehudit1987 force-pushed the feat/migrate_twa_tests branch from a97625b to 09f01c5 Compare October 15, 2025 11:05
Copy link
Contributor

@andyatmiami andyatmiami left a comment

Choose a reason for hiding this comment

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

Hey @yehudit1987 - thank you for these changes...

Things look pretty good - but would like for yourself and/or @kimwnasptd to weigh in on the observations I have included on this PR for discussion.

"@typescript-eslint/eslint-plugin": "4.28.2",
"@typescript-eslint/parser": "4.28.2",
"cypress": "~13.13.1",
"cypress": "14.1.0",
Copy link
Contributor

Choose a reason for hiding this comment

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

I have confirmed this 14.1.0 version does fix the connectivity issues b/w Cypress and Firefox... but unfortunately leads to this message cropping up in build logs:

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '^18.0.0 || ^20.0.0 || >=22.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }

By all accounts this WARN is not affecting anything - but wanted to surface this so we can discuss what to do.

Copy link
Contributor

Choose a reason for hiding this comment

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

I am also unclear if we want to fix the version of Cypress to 14.1.0 - or use a qualifier like ^ or ~

Copy link
Author

Choose a reason for hiding this comment

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

Regarding the warning, upgrading the Node version to 18 or 20 would resolve it. this mainly impacts CI/CD environments, so there’s likely no real harm. Alternatively, we could just ignore the warning since it doesn’t affect runtime behavior.

As for the version qualifier, I’m not an expert here, but I’d lean toward using ~ since it allows patch updates while avoiding unexpected minor version changes, a safer middle ground than using ^.

Copy link
Member

Choose a reason for hiding this comment

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

I'd personally be OK with fixing the version to 14.1.0. And to cross-reference our discussion in the other PR as well #625 (comment)

Copy link
Author

Choose a reason for hiding this comment

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

Hey @kimwnasptd and @andyatmiami.
I’ve tested the suggested changes from the other PR. I kept the Cypress version pinned as it was and also pinned the tough-cookie version as recommended.

For this PR’s requirements, it wasn’t strictly necessary, but as expected, it didn’t break anything and helps keep things aligned with the other PR and consistent across the project.
Was tested in the attached - https://github.com/yehudit1987/notebooks/actions/runs/18817889000

make docker-build
- name: Install KinD
run: ./components/testing/gh-actions/install_kind.sh
Copy link
Contributor

Choose a reason for hiding this comment

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

While not directly related to changes introduced in this PR - given the AWS outage today - I am seeing issues trying to retrieve the kind binary referenced in install_kind.sh

➜ Downloads/ $ curl -vL -o kind "https://kind.sigs.k8s.io/dl/v0.22.0/kind-linux-amd64"
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Host kind.sigs.k8s.io:443 was resolved.
* IPv6: 2600:1f18:16e:df01::259, 2600:1f18:16e:df01::258
* IPv4: 18.208.88.157, 98.84.224.111
*   Trying 18.208.88.157:443...
*   Trying [2600:1f18:16e:df01::259]:443...
* Immediate connect fail for 2600:1f18:16e:df01::259: No route to host
*   Trying [2600:1f18:16e:df01::258]:443...
* Immediate connect fail for 2600:1f18:16e:df01::258: No route to host
  0     0    0     0    0     0      0      0 --:--:--  0:01:09 --:--:--     0

It seems GitHub also hosts this binary and it available here:

  • https://github.com/kubernetes-sigs/kind/releases/download/v0.22.0/kind-linux-amd64

And I have confirmed its presently accessible:

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 6245k  100 6245k    0     0  17.4M      0 --:--:-- --:--:-- --:--:-- 17.4M

Should install_kind.sh be updated to use this alternative location?

Copy link
Author

@yehudit1987 yehudit1987 Oct 22, 2025

Choose a reason for hiding this comment

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

I guess this wondering depends on the answer to the question which of the two is more reliable in general?

@andyatmiami
Copy link
Contributor

/ok-to-test

Copy link
Contributor

@andyatmiami andyatmiami left a comment

Choose a reason for hiding this comment

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

/lgtm

Thanks for all this work @yehudit1987 - appreciate your responsiveness and diligence in working through issues in this PR (and taking lessons learned to help others facing similar issues 💯 )

I'm comfortable with the changes and have verified the workflows behave as expected.

Tested on my fork:

image

@google-oss-prow google-oss-prow bot added the lgtm label Oct 27, 2025
@kimwnasptd
Copy link
Member

Thank you so much for this effort @yehudit1987!

/approve

@google-oss-prow
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kimwnasptd

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

@kimwnasptd
Copy link
Member

There seems to be a conflict with the releasing/version/VERSION file. Let's rebase on top of the latest notebooks-v1 branch to resolve the conflict

@yehudit1987 yehudit1987 force-pushed the feat/migrate_twa_tests branch from 979501e to bf807b4 Compare October 28, 2025 16:08
@google-oss-prow google-oss-prow bot removed the lgtm label Oct 28, 2025
@andyatmiami
Copy link
Contributor

/lgtm

latest commit simply is a result of a rebase to resolve a merge conflict in the VERSION file.

@google-oss-prow google-oss-prow bot added the lgtm label Oct 28, 2025
@google-oss-prow google-oss-prow bot merged commit e33dc11 into kubeflow:notebooks-v1 Oct 28, 2025
13 checks passed
@github-project-automation github-project-automation bot moved this from Needs Triage to Done in Kubeflow Notebooks Oct 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved area/backend area - related to backend components area/ci area - related to ci area/frontend area - related to frontend components area/v1 area - version - kubeflow notebooks v1 lgtm ok-to-test size/XL

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants