Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Return IonQ failure code/error directly to user #437

Open
anthony-santana opened this issue Jul 18, 2023 · 2 comments
Open

Return IonQ failure code/error directly to user #437

anthony-santana opened this issue Jul 18, 2023 · 2 comments
Labels
good first issue Good for newcomers

Comments

@anthony-santana
Copy link
Collaborator

anthony-santana commented Jul 18, 2023

When a job submission to IonQ fails, we currently point the user to their IonQ account to actually return the error.

We need clarification on what any errors being returned from IonQ look like generally, then we can add an extra line of code for dumping the whole error code to the programmer.

For more context: #429 (comment)

@anthony-santana anthony-santana added the good first issue Good for newcomers label Jul 19, 2023
@anthony-santana
Copy link
Collaborator Author

Hi @splch, would you mind clarifying what the job failure map will look like in general? Here's an example that I've seen:

[{
    "failure":{"code":"PreflightError", "error":"Internal Server Error"},
    ...
    "status":"failed",
    "target":"simulator"
  }]

Will it always have just two keys; "code" and "error"? Does that hold true if there were multiple errors in the submission? Thanks!

@splch
Copy link
Contributor

splch commented Jul 20, 2023

Hi @splch, would you mind clarifying what the job failure map will look like in general? Here's an example that I've seen:

[{
    "failure":{"code":"PreflightError", "error":"Internal Server Error"},
    ...
    "status":"failed",
    "target":"simulator"
  }]

Will it always have just two keys; "code" and "error"? Does that hold true if there were multiple errors in the submission? Thanks!

Hi! We have 2 cases: first if the API request fails which is outlined in our API spec, and second where a job fails running which will always return code and error. So yes, you're correct that is how the failed jobs error will look 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants