Skip to content

refactor: unify framework error codes and boundary logging - #198

Merged
chamsechan merged 3 commits into
mainfrom
refactor/unified-error-codes
Oct 14, 2026
Merged

chamsechan merged 3 commits into
mainfrom
refactor/unified-error-codes

Conversation

@chamsechan

Copy link
Copy Markdown
Owner

Verified by the repository's canonical local quality gate.

chamsechan and others added 3 commits October 14, 2026 18:16
Encode, AppendTokenBytes and Decode now return error::kOk or a specific
framework code (kInvalidArgument, kInvalidUtf8, kInvalidInput,
kInvalidState, kInternalException, kUnknownException) instead of -1,
following doc/dev_guide/error_handling.md. Internal not-found sentinels
are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Operator boundary logs record only operation, stage, framework code and
  platform code; the full detail stays in GetOperatorLastError(), since
  details such as JSON parse errors can quote request content.
- Kite backend returns failure-semantic framework codes (inference,
  allocation, invalid output, invalid input/argument) via a private
  exception type instead of mapping every vendor failure to
  INTERNAL_EXCEPTION.
- AlgBase_setLogLevelByName keeps its documented public -1 return;
  public C interfaces never return framework codes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chamsechan
chamsechan merged commit 435e8dd into main Oct 14, 2026
6 checks passed
@chamsechan
chamsechan deleted the refactor/unified-error-codes branch October 14, 2026 11:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant