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 16:11:59 UTC

[GH] (shardingsphere/fix-firebird-blob-error-handling): Workflow run "Required - Check" failed!

The GitHub Actions job "Required - Check" on shardingsphere.git/fix-firebird-blob-error-handling has failed.
Run started by GitHub user rishi-rana (triggered by rishi-rana).

Head commit for run:
a179526d7c8c769f295560d732a50c6b39323c00 / rishi-rana <ri...@hotmail.com>
Add error handling for unknown or closed BLOB handles and ids in Firebird Proxy

Fixes 4 of 5 sub-cases in #39052 (isc_blobtoobig split off to #39772
pending a design decision on the buffered-size limit):

- FirebirdOpenBlobCommandExecutor: throw InvalidSegstrIdException on an
  unknown BLOB id instead of registering an empty BLOB.
- FirebirdPutBlobSegmentCommandExecutor / FirebirdBatchBlobSegmentsCommandExecutor:
  check appendSegment()'s OptionalInt result and throw
  InvalidSegstrHandleException on an unknown or already-closed handle
  instead of silently reporting success. Covers both the "unknown
  handle" and "put after close" cases, since closeWrite() removes the
  cache entry either way.
- FirebirdExecuteStatementCommandExecutor.bindBlobParameters(): throw
  InvalidSegstrIdException for an unknown or unclosed BLOB parameter
  instead of silently binding null.

Adds InvalidSegstrHandleException/InvalidSegstrIdException and their
FirebirdVendorError/FirebirdDialectExceptionMapper wiring, following
the error-handling pattern established in #38927 (gdscodes and SQL
states verified against the jaybird client jar: isc_bad_segstr_handle
and isc_bad_segstr_id both map to SQLSTATE 42000).

Co-Authored-By: Claude Sonnet 5 <no...@anthropic.com>
Claude-Session: https://claude.ai/code/session_0126yyNgnn3J8br27eT4P5as

Report URL: https://github.com/apache/shardingsphere/actions/runs/34255171743

With regards,
GitHub Actions via GitBox