Open dcanuto opened 3 weeks ago
@dcanuto Thanks for reporting this. Looks like the session details response from the API doesn't return a backend so the first backend from the list of available backends is returned instead.
{'id': '4733121c-118f-4947-af83-dcc9c81a46bf', 'backend_name': '',
'interactive_ttl': 60,
'max_ttl': 28800, 'active_ttl': 28800,
'state': 'open', 'accepting_jobs': True, 'mode': 'dedicated'}
I follow up with the server side.
Describe the bug
The
Session.from_id
method is returning aSession
instance whosebackend
method returns a backend name different from the session whose ID was passed intofrom_id
.Steps to reproduce
Expected behavior
The
second_session
andsecond_session_copy
should both return"ibm_fez"
from theirbackend
method.Suggested solutions
Not sure, but perhaps there is a bug in the
session_details
method of theQiskitRuntimeService._api_client
attribute (used here inSession.from_id
)?Additional Information