jiayuasu opened a new pull request, #3248:
URL: https://github.com/apache/sedona/pull/3248

   ## Did you read the Contributor Guide?
   
   - Yes, I have read the [Contributor 
Rules](https://sedona.apache.org/latest/community/rule/) and [Contributor 
Development Guide](https://sedona.apache.org/latest/community/develop/)
   
   ## Is this PR related to a ticket?
   
   - No, this is a CI update. The PR name follows the format `[CI] my subject`
   
   ## What changes were proposed in this PR?
   
   The nightly docker image build has been failing intermittently since 
2026-08-05 with:
   
   ```
   Downloading Zeppelin 0.12.0 from Lyra Hosting mirror...
   curl: (60) SSL certificate problem: certificate has expired
   ```
   
   `mirror.lyrahosting.com` sits behind a load balancer where one backend has 
been serving an expired TLS certificate (expired 2026-08-04); whether a given 
`curl` hits the good or bad backend is a coin flip, so the amd64 and arm64 
build stages can fail independently.
   
   Changes to `docker/install-zeppelin.sh`:
   
   - Download Zeppelin from `dlcdn.apache.org` (the Apache CDN) instead of the 
third-party Lyra mirror.
   - Fall back to `archive.apache.org` if the CDN download fails, since dlcdn 
only hosts current releases. The sha512 checksum is still fetched from the 
Apache archive and verified either way.
   - Pass `--fail` to curl (matching `install-spark.sh`) so an HTTP error page 
is not saved as the tarball and a 404 correctly triggers the fallback.
   
   ## How was this patch tested?
   
   - Verified both `dlcdn.apache.org` and `archive.apache.org` serve 
`zeppelin-0.12.0-bin-netinst.tgz` (HTTP 200).
   - Smoke-tested the fallback path locally: a 404 on the primary URL now fails 
fast and the archive fallback downloads and passes the content check.
   - `bash -n` and shellcheck (pre-commit) pass.
   
   ## Did this PR include necessary documentation updates?
   
   - No, this PR does not affect any public API so no need to change the 
documentation.


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to