-
Notifications
You must be signed in to change notification settings - Fork 28k
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
[SPARK-48222][INFRA][DOCS] Sync Ruby Bundler to 2.4.22 and refresh Gem lock file #46512
Conversation
Thank you, @nchammas . cc @cloud-fan although I'm sure he is testing this PR already. 😄 |
@@ -38,7 +38,7 @@ ENV DEBCONF_NONINTERACTIVE_SEEN true | |||
ARG APT_INSTALL="apt-get install --no-install-recommends -y" | |||
|
|||
ARG PIP_PKGS="sphinx==4.5.0 mkdocs==1.1.2 numpy==1.20.3 pydata_sphinx_theme==0.13.3 ipython==7.19.0 nbsphinx==0.8.0 numpydoc==1.1.0 jinja2==3.1.2 twine==3.4.1 sphinx-plotly-directive==0.1.3 sphinx-copybutton==0.5.2 pandas==2.0.3 pyarrow==10.0.1 plotly==5.4.0 markupsafe==2.0.1 docutils<0.17 grpcio==1.62.0 protobuf==4.21.6 grpcio-status==1.62.0 googleapis-common-protos==1.56.4" | |||
ARG GEM_PKGS="bundler:2.3.8" | |||
ARG GEM_PKGS="bundler:2.4.22" |
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.
shall we also install ruby 3?
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.
Eventually, yes, we should migrate to Ruby 3. However, since we have been running CI on Ruby 2, I think it would be safer to keep it at that for now and get the release process unblocked.
rb-fsevent (0.11.2) | ||
rb-inotify (0.10.1) | ||
ffi (~> 1.0) | ||
rexml (3.2.6) | ||
rouge (3.30.0) | ||
safe_yaml (1.0.5) | ||
sass-embedded (1.69.7) | ||
google-protobuf (~> 3.25) | ||
sass-embedded (1.63.6) |
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.
hmm why is this downgraded?
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.
Probably because I was running a different version of Ruby and/or Bundler when I last updated the lock file.
But as part of this PR I made sure to run Ruby 2.7 and Bundler 2.4.22 to match the CI environment.
Keep in mind that Bundler selects the versions in this lock file based on the Ruby version and required dependencies.
thanks, merging to master! (it's easier for me to test after merging it) |
the Bundler issue is resolved, but I hit a new issue for generating pyspark docs
maybe there is some python library version inconsistency between Github Action and release docker |
cc @HyukjinKwon |
It seems that |
Yes, and we dropped support for Python 3.8 in #46228. |
Ya, as @nchammas mentioned, it seems that we missed to bump Python to 3.9 in |
I see, I'll install python 3.9 on the release docker image. |
…m lock file ### What changes were proposed in this pull request? Sync the version of Bundler that we are using across various scripts and documentation. Also refresh the Gem lock file. ### Why are the changes needed? We are seeing inconsistent build behavior, likely due to the inconsistent Bundler versions. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? CI + the preview release process. ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#46512 from nchammas/bundler-sync. Authored-by: Nicholas Chammas <nicholas.chammas@gmail.com> Signed-off-by: Wenchen Fan <wenchen@databricks.com>
What changes were proposed in this pull request?
Sync the version of Bundler that we are using across various scripts and documentation. Also refresh the Gem lock file.
Why are the changes needed?
We are seeing inconsistent build behavior, likely due to the inconsistent Bundler versions.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
CI + the preview release process.
Was this patch authored or co-authored using generative AI tooling?
No.