Repository navigation
chore: update kernel revision - #976
Merged
Merged
Conversation
Picks up databricks-sql-kernel#388, which fixes an intermittent hang in Session.close() when a runtime worker is forwarding a log record to Python logging as the runtime shuts down. Co-authored-by: Isaac <no-reply@databricks.com> Signed-off-by: Vu Anh Phung <vu.phung@databricks.com>
vuanhphung
enabled auto-merge
October 8, 2026 17:28
vuanhphung
disabled auto-merge
October 8, 2026 18:11
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
Description
Updates
KERNEL_REVfrom80f2aeetoab1e6a707e4a15a3a7a8c78d8fdd12c752c51102(kernelmain) to pick up databricks/databricks-sql-kernel#388. That PR fixes an intermittent hang inSession.close(): the runtime is dropped with the GIL held while a worker is waiting for the GIL to forward a log record. This hang causes the 60-minute timeouts in the driver-test Pythonkernel · reydennightly.The bump also includes the kernel changes merged since
80f2aee. The ones that change default behavior are:Accept-Encoding: identity).CreateSessionand fail open.GEOMETRY/GEOGRAPHYvalues come back as EWKT strings by default.execute()no longer has an implicit 600s timeout.The Python binding API is unchanged.
How is this tested?
Pin-only change;
kernel-e2eruns against the new revision.Related Tickets & Documents
databricks/databricks-sql-kernel#388
This pull request and its description were written by Isaac.