Describe the bug
On creation of a driver, the systemd snippet shown for python (could also be for other languages) does not
upgrade/downgrade an already existing qpi-driver and thus it raises errors if the expected version is incompatible with the pre-existing one.
To Reproduce
Steps to reproduce the behavior:
- Install an older version of qpi-driver e.g.
uv tool install --python 3.12 "qpi-driver[cli,aer]==0.0.36"
- As admin, go to 'http://127.0.0.1:8090/#drivers'
- Click on 'Register Driver'
- Feed in details including language: 'python', kind: 'qiskit_aer ( Aer Simulator)'
- Click the submit button
- In the snippets that are shown, copy the one for systemd
- Go to your terminal if you are on a systemd enabled computer and run the snippet.
- Check the logs of the driver installed
journalctl -u <name-of-service> -n 25
- You will see errors like 'No such command 'process'. ' which is true for qpi-driver v0.0.35
Screenshots
N/A
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
N/A
Additional context
It seems QPI_DRIVER_VERSION which was probably originally passed as part of that snippet is no longer passed.
It is supposed to be got from /api/op/version GET to the go server, I think.
Describe the bug
On creation of a driver, the systemd snippet shown for python (could also be for other languages) does not
upgrade/downgrade an already existing qpi-driver and thus it raises errors if the expected version is incompatible with the pre-existing one.
To Reproduce
Steps to reproduce the behavior:
uv tool install --python 3.12 "qpi-driver[cli,aer]==0.0.36"journalctl -u <name-of-service> -n 25Screenshots
N/A
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
N/A
Additional context
It seems
QPI_DRIVER_VERSIONwhich was probably originally passed as part of that snippet is no longer passed.It is supposed to be got from
/api/op/versionGET to the go server, I think.