Logging

TypeBridge does not configure application logging. Python uses the standard logging hierarchy; Rust and Node surface structured errors and diagnostics at their public boundaries.

Python

Enable all facade logging:

import logging

logging.basicConfig(level=logging.DEBUG)
logging.getLogger("type_bridge").setLevel(logging.DEBUG)

Useful retained namespaces include:

type_bridge
├── type_bridge.session       connection and transaction facade
├── type_bridge.query         retained raw query facade
├── type_bridge.typed         retained typed-query compatibility facade
├── type_bridge.migration     V2 CLI and read-only archive recovery
└── type_bridge.proxy         remote proxy boundary

Generated package managers execute in the native Rust engine. Their failures carry canonical operation/model/field or role diagnostics; they do not depend on a public Python manager logger.

During tests:

uv run pytest -vv -s --log-cli-level=DEBUG

Native diagnostics

Use a Rust backtrace for a focused source-tree failure:

RUST_BACKTRACE=1 uv run pytest tests/integration/schema/test_generated_projection_live.py -vv -s

Application validation errors are stable public diagnostics and should be handled normally. A Rust panic/backtrace is an internal defect and should be reported with the smallest reproducible generated workspace and operation.

Sensitive data

Do not log passwords, tokens, credential-provider output, complete TLS private material, or unbounded query/result bytes. Projection fingerprints, schema labels, operation names, bounded diagnostics, TypeDB versions, and request identities are suitable for troubleshooting.