You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@zeppelin.apache.org by "miinhho (via GitHub)" <gi...@apache.org> on 2026/10/21 11:14:17 UTC

[PR] [ZEPPELIN-6739] Keep Python CI locks current with validated Pixi refreshes [zeppelin]

miinhho opened a new pull request, #5584:
URL: https://github.com/apache/zeppelin/pull/5584

   ### What is this PR for?
   
   Linux Python CI installs committed dependency locks to avoid resolving dependencies on every run. However, these locks are refreshed manually, so newer compatible dependencies remain untested and upstream breaking changes can go unnoticed.
   
   This PR adds weekly dependency refreshes within the supported Python and backend versions. It runs the existing backend and Selenium tests against the candidate lock and proposes a draft PR only when the tests pass and dependencies have changed. Failures leave the committed lock unchanged. Regular CI continues using the committed lock, with no automatic merging.
   
   The shared Python, TensorFlow and PyFlink environments are managed through `pixi.toml` and `pixi.lock`. Regular CI and refresh validation reuse the same test definitions.
   
   ### What type of PR is it?
   Improvement
   
   ### Todos
   - [ ] Complete backend and Selenium validation on GitHub Actions before merge.
   
   ### What is the Jira issue?
   * https://issues.apache.org/jira/browse/ZEPPELIN-6739
   
   ### How should this be tested?
   
   1. Run the core and frontend workflows. Verify that the existing backend and Selenium tests run using the committed lock without resolving dependencies.
   2. Manually run Python dependency refresh on a test fork. Verify that it generates a candidate lock and runs both validation workflows using that candidate.
   3. On a disposable branch, force a validation test to fail and rerun the refresh. Verify that the failure is visible in Actions.
   
   Manual execution requires the workflow to exist on the fork’s default branch. Fork runs validate candidate generation and testing; actual draft-PR publication is restricted to `apache/zeppelin` master.
   
   ### Questions:
   
   - Does the license files need to update? No.
   - Is there breaking changes for older versions? No.
   - Does this needs documentation? Yes, updated in `testing/README.md`.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: reviews-unsubscribe@zeppelin.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] [ZEPPELIN-6739] Keep Python CI locks current with validated Pixi refreshes [zeppelin]

Posted by "miinhho (via GitHub)" <gi...@apache.org>.
miinhho commented on PR #5584:
URL: https://github.com/apache/zeppelin/pull/5584#issuecomment-6400749799

   I am replacing this Pixi-based implementation with an approach that retains Conda and uses conda-lock.
   
   The replacement keeps regular CI lock-based, adds periodic dependency resolution and compatibility checks, and proposes tested lock updates for review. It also documents how contributors can update the locks from Linux, macOS, and Windows.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: reviews-unsubscribe@zeppelin.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] [ZEPPELIN-6739] Keep Python CI locks current with validated Pixi refreshes [zeppelin]

Posted by "miinhho (via GitHub)" <gi...@apache.org>.
miinhho closed pull request #5584: [ZEPPELIN-6739] Keep Python CI locks current with validated Pixi refreshes
URL: https://github.com/apache/zeppelin/pull/5584


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: reviews-unsubscribe@zeppelin.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] [ZEPPELIN-6739] Keep Python CI locks current with validated Pixi refreshes [zeppelin]

Posted by "miinhho (via GitHub)" <gi...@apache.org>.
miinhho commented on PR #5584:
URL: https://github.com/apache/zeppelin/pull/5584#issuecomment-6316448647

   Keeping this as a draft: using a new GitHub Action requires a PR to [apache/infrastructure-actions](https://github.com/apache/infrastructure-actions), and CI fails on unapproved actions. I’ll mark it ready once that PR is approved.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: reviews-unsubscribe@zeppelin.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] [ZEPPELIN-6739] Keep Python CI locks current with validated Pixi refreshes [zeppelin]

Posted by "miinhho (via GitHub)" <gi...@apache.org>.
miinhho commented on PR #5584:
URL: https://github.com/apache/zeppelin/pull/5584#issuecomment-6314636352

   The lock-file migration adds 6,553 lines in `pixi.lock` and removes 607 lines from the previous Conda and PyFlink lock files. These generated-file changes account for a substantial part of the overall diff.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: reviews-unsubscribe@zeppelin.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org