iqm_error#
Full path: exa.common.errors.iqm_error
Shared error definitions for the IQM ecosystem.
This module provides the unified exception hierarchy used by both client and server components. By centralizing these definitions in a shared library, we ensure that error states are communicated and handled consistently across the network.
Architectural Context#
Symmetric Logic: Components like
SettingNodeorExperimentuse these errors for local validation. Sharing them ensures that a Validation failure on the client feels identical to one on the server.Type Preservation: Server-side errors (e.g.,
InternalServerError) are included here so the client can deserialize them into specific Python types rather than generic catch-all exceptions.Wire Compatibility: These exceptions map directly to HTTP status codes and the
IQMServerErrorPydantic data model.
Client-Relevant Errors#
While all errors can be received from the server, the following are most commonly raised or handled specifically in client-side logic:
ValidationError: Local input/parameter checks before transmission.NotFoundError: Handling missing resources in lookups.ConflictError: Managing state-machine or concurrency issues.
Exceptions
|
Raised when the caller is not authenticated or credentials are missing. |
|
Raised when an invalid or unintelligible response is received from a dependency. |
alias of |
|
|
Raised when a failure occurs during the physical execution of a circuit. |
|
Raised when a circuit cannot be transpiled, typically due to hardware constraints. |
|
Raised when a circuit is well-formed but violates hardware or logical constraints. |
|
Raised when an operation conflicts with the current state of the system. |
|
Raised when the provided data exceeds the allowed size limits. |
|
Raised when an empty list is given as components for running an experiment. |
|
Raised when the station control engine fails to initialize. |
|
Raised when the user is authenticated but lacks permission for the operation. |
alias of |
|
|
Base exception for the IQM ecosystem logic. |
alias of |
|
|
Raised when an unexpected internal failure occurs. |
|
Raised when the operation parameters are invalid or the action is unsupported. |
|
Raised when a requested resource or data point was not found. |
|
Raised when an operation or a call to a dependency fails to complete in time. |
alias of |
|
|
Raised when the operation frequency exceeds the allowed limit in a given timeframe. |
alias of |
|
|
Raised when a required system component is temporarily unable to operate. |
alias of |
|
alias of |
|
|
Raised when an observation name is syntactically correct but contains unknown elements. |
|
Raised when a SettingNode attribute is not found. |
|
Raised when data is well-formed but semantically invalid. |