exceptions
Custom exceptions for the Bitfount codebase.
Classes
BitfountEngineError
class BitfountEngineError(*args, **kwargs):Exception for any issues relating to the backend engine.
Ancestors
BitfountError
class BitfountError(*args, **kwargs):Base exception class that all others should inherit from.
Subclasses
- MissingDICOMFieldError
- BitfountSchemaError
- DataCacheError
- DataNotAvailableError
- DataNotLoadedError
- DataSourceError
- DataStructureError
- DuplicateColumnError
- EncryptionError
- BitfountEngineError
- BitfountVersionError
- TaskValidationError
- UnsupportedCacheError
- FHIRR4APIError
- NextGenAPIError
- AuthenticationError
- AggregatorError
- AlgorithmError
- BatchResilienceAbortError
- BitfountTaskStartError
- DPNotAppliedError
- DPParameterError
- DataProcessingError
- EHRConnectionError
- EHRNotConfiguredError
- EHRTokenError
- MessageHandlerDispatchError
- MessageRetrievalError
- NoDataError
- NoNewDataError
- OrchestratorTokenEndpointError
- PodConnectFailedError
- PodNameError
- PodRegistrationError
- PodResponseError
- PrivateSqlError
- ProtocolError
- TaskAbortError
- WorkerProcessSpawnError
- PodConfigReloadError
- BitfountMessageServiceError
- AuthEnvironmentError
- ModelUploadError
- MultiPartUploadError
- NoModelCodeError
- PodDoesNotExistError
- SMARTOnFHIRError
- SchemaUploadError
- MultiPodSchemaMismatchError
- PlugInAlgorithmError
- PlugInProtocolError
- SchemaClassError
- AWSError
- MaxRetriesExceededError
BitfountVersionError
class BitfountVersionError(*args, **kwargs):Exception for issues related to version incompatibility.
Ancestors
TaskValidationError
class TaskValidationError(*args, **kwargs):Exception for a task that fails schema/content validation.
Distinct from BitfountVersionError: this signals that the task
configuration itself is invalid (e.g. a constraint violation or a missing
required field) rather than that the task targets an incompatible version.
Ancestors
UnsupportedCacheError
class UnsupportedCacheError(*args, **kwargs):Exception for a cache file whose physical schema this build cannot use.
Raised when a table is missing a column that the ORM for the version the table is recorded at declares. That is not a migration gap — a migration describes the delta between two settled versions, and this table never held a settled one — so there is nothing to migrate from and the cache file itself has to go.
Distinct from the KeyError ensure_types raises for a cache written by a
newer SDK: there the schema is fine and this build merely cannot describe
it. Here the schema is genuinely incomplete.