Skip to content

Update docker.io/apache/spark Docker tag to v3.5.7#59

Closed
renovate[bot] wants to merge 1 commit intomainfrom
renovate/docker.io-apache-spark-3.x
Closed

Update docker.io/apache/spark Docker tag to v3.5.7#59
renovate[bot] wants to merge 1 commit intomainfrom
renovate/docker.io-apache-spark-3.x

Conversation

@renovate
Copy link

@renovate renovate bot commented Oct 24, 2025

This PR contains the following updates:

Package Type Update Change
docker.io/apache/spark final patch 3.5.6-java17-python3 -> 3.5.7-java17-python3
docker.io/apache/spark final patch 3.5.6-java17 -> 3.5.7-java17

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Author

renovate bot commented Oct 24, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (3.5.7-java17-python3). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/docker.io-apache-spark-3.x branch October 24, 2025 12:21
snazy added a commit that referenced this pull request Nov 20, 2025
* NoSQL: do not use delayedExecutor in monotonic clock

It is possible that `CompletableFuture.deleyedExecutor` (or better the JVM global `CompletableFuture.Delayer#delayer`) stalls, if another call site supplies an `Executor` that blocks when offering tasks (i.e. when the delayed tasks shall be scheduled), in cases when such `Executors` use a bounded/blocking queue.

This change moves back to a single thread. The alternative would be to use a single-threaded-scheduled-executor, which would also permanently run one thread.

Also adds some logging for big-ish wall-clock adjustments.

* longer sleep
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant