You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/architecture/native-interop.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,6 +85,6 @@ Multiple V3 clients share the same process-wide Tokio runtime. This reduces thre
85
85
86
86
## Error Handling
87
87
88
-
Native failures are surfaced as managed exceptions that include operation context and the native last-error message when available. Agents should preserve these messages in diagnostics and not replace them with generic errors.
88
+
Native failures are surfaced as managed exceptions that include operation context, the native last-error message, and the native error code when available. Agents should preserve these messages in diagnostics and not replace them with generic errors.
89
89
90
-
The native ABI also exposes stable integer error codes for engine-level last errors and async operation failures. `0` means success/no error; non-zero values distinguish invalid requests, missing tables, Delta/DataFusion/Arrow/JSON failures, internal failures, and cancellation. Managed code still includes the native message in exceptions, but cancellation detection should prefer the typed async error code and use message matching only as a compatibility fallback.
90
+
The native ABI exposes stable integer error codes for engine-level last errors and async operation failures. `0` means success/no error; non-zero values distinguish invalid requests, missing tables, Delta/DataFusion/Arrow/JSON failures, internal failures, and cancellation. Managed code maps these values to an internal `NativeServiceErrorCode` enum for diagnostics and control flow. Cancellation detection uses the typed async error code first and message matching only as a compatibility fallback.
0 commit comments