Skip to content

[WIP] Correctly retrieve jobs from retired backends - #3020

Draft
diego-plan9 wants to merge 5 commits into
mainfrom
fix/job-from-retired-backend
Draft

[WIP] Correctly retrieve jobs from retired backends#3020
diego-plan9 wants to merge 5 commits into
mainfrom
fix/job-from-retired-backend

Conversation

@diego-plan9

Copy link
Copy Markdown
Member

Summary

Revise the handling of jobs from retired backends (by having an inner function raise when their configuration could not be accessed), so the job() and jobs() methods produce an IBMRetiredBackend in that case.

Details and comments

Fixes #3012

AI/LLM disclosure

  • I didn't use LLM tooling, or only used it privately.
  • I used the following tool to help write this PR description:
  • I used the following tool to generate or modify code:

@diego-plan9

Copy link
Copy Markdown
Member Author

Issued this one against main for extra confidence via integration tests.

@diego-plan9
diego-plan9 had a problem deploying to ibm-cloud-production July 9, 2026 12:52 — with GitHub Actions Failure
@diego-plan9 diego-plan9 changed the title Correctly retrieve jobs from retired backends [WIP] Correctly retrieve jobs from retired backends Jul 10, 2026
@diego-plan9
diego-plan9 marked this pull request as draft July 10, 2026 07:51
@diego-plan9

Copy link
Copy Markdown
Member Author

Moving to draft to further inspect some potential issues with ._active_api_client.

@diego-plan9
diego-plan9 temporarily deployed to ibm-cloud-production July 10, 2026 07:56 — with GitHub Actions Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow querying jobs from retired backend

1 participant