You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2026/09/16 00:05:05 UTC
[GH] (shardingsphere/fix-firebird-blob-error-handling): Workflow run "CI" is working again!
The GitHub Actions job "CI" on shardingsphere.git/fix-firebird-blob-error-handling has succeeded.
Run started by GitHub user rishi-rana (triggered by linghengqian).
Head commit for run:
2571d2193c4b450ff04b383a13d69534c8884970 / rishi-rana <ri...@hotmail.com>
Open a created and closed BLOB by its id in Firebird Proxy
A BLOB created by the client keeps its id and content in
FirebirdBlobWriteCache after close_blob, but open_blob only consulted the
result BLOB store, so create_blob -> put_segment -> close_blob ->
open_blob raised isc_bad_segstr_id for a known id instead of opening its
stored content. Firebird allows a created BLOB to be opened once closed.
Resolve the content by id: zero opens an empty BLOB, a negative id reads
the result BLOB store, and a positive id reads the write cache, which is
rejected when the id is unknown or still open.
Co-Authored-By: Claude Opus 5 <no...@anthropic.com>
Claude-Session: https://claude.ai/code/session_0126yyNgnn3J8br27eT4P5as
Report URL: https://github.com/apache/shardingsphere/actions/runs/35003053027
With regards,
GitHub Actions via GitBox