search

Qiskit / qiskit-metapackage

Qiskit is an open-source SDK for working with quantum computers at the level of circuits, algorithms, and application modules.
https://qiskit.org
Apache License 2.0
3.04k stars 753 forks source link

Failed to load model class 'CircuitComposerModel' from module '@quantum/ibm-q-lab-widgets' #1703

Closed TheFlightSimsOfficial closed 1 year ago

TheFlightSimsOfficial commented 1 year ago

Information

What is the current behavior?

Failed to open quantum composer. 

Failed to load model class 'CircuitComposerModel' from module '@quantum/ibm-q-lab-widgets'
Error: No version of module @quantum/ibm-q-lab-widgets is registered

Steps to reproduce the problem

  1. Start a Jupyter Lab Server
  2. Create a notebook file
  3. Use these codes to open Circuit Composer 
    from ibm_quantum_widgets import CircuitComposer
editor = CircuitComposer()
editor
  4. The error happened

image

What is the expected behavior?

The Circuit Composer must start as I tested on IBM Quantum Lab

image

Detail logs

[Open Browser Console for more detailed log - Double click to close this message]
Failed to load model class 'CircuitComposerModel' from module '@quantum/ibm-q-lab-widgets'
Error: No version of module @quantum/ibm-q-lab-widgets is registered
    at f.loadClass (http://localhost:8000/user/administrator@theflightsims.tfs/lab/extensions/@jupyter-widgets/jupyterlab-manager/static/134.c61b95b04e00f8487eeb.js?v=c61b95b04e00f8487eeb:1:74856)
    at f.loadModelClass (http://localhost:8000/user/administrator@theflightsims.tfs/lab/extensions/@jupyter-widgets/jupyterlab-manager/static/150.267f129ae5fd6a33b390.js?v=267f129ae5fd6a33b390:1:10729)
    at f._make_model (http://localhost:8000/user/administrator@theflightsims.tfs/lab/extensions/@jupyter-widgets/jupyterlab-manager/static/150.267f129ae5fd6a33b390.js?v=267f129ae5fd6a33b390:1:7517)
    at f.new_model (http://localhost:8000/user/administrator@theflightsims.tfs/lab/extensions/@jupyter-widgets/jupyterlab-manager/static/150.267f129ae5fd6a33b390.js?v=267f129ae5fd6a33b390:1:5137)
    at f.handle_comm_open (http://localhost:8000/user/administrator@theflightsims.tfs/lab/extensions/@jupyter-widgets/jupyterlab-manager/static/150.267f129ae5fd6a33b390.js?v=267f129ae5fd6a33b390:1:3894)
    at _handleCommOpen (http://localhost:8000/user/administrator@theflightsims.tfs/lab/extensions/@jupyter-widgets/jupyterlab-manager/static/134.c61b95b04e00f8487eeb.js?v=c61b95b04e00f8487eeb:1:73393)
    at b._handleCommOpen (http://localhost:8000/user/administrator@theflightsims.tfs/static/lab/jlab_core.48a41b637653e18e773e.js?v=48a41b637653e18e773e:2:1039756)
    at async b._handleMessage (http://localhost:8000/user/administrator@theflightsims.tfs/static/lab/jlab_core.48a41b637653e18e773e.js?v=48a41b637653e18e773e:2:1041746)
mtreinish commented 1 year ago

The ibm-q-lab-widgets package isn't part of qiskit, as far as I know it's a closed-source/proprietary package that doesn't have a public issue tracker or a direct contact email address to report any issues. I'll ask people inside IBM for the current status of the package and will leave a comment here if I have any update.

But, I am going to close this issue as there isn't anything we can do in Qiskit about this because the package is not part of the qiskit project.

TheFlightSimsOfficial commented 1 year ago

The ibm-q-lab-widgets package isn't part of qiskit, as far as I know it's a closed-source/proprietary package that doesn't have a public issue tracker or a direct contact email address to report any issues. I'll ask people inside IBM for the current status of the package and will leave a comment here if I have any update.

But, I am going to close this issue as there isn't anything we can do in Qiskit about this because the package is not part of the qiskit project.

Thank you. I hope you will contact them soon.

I really like composing quantum circuits on Jupyter Lab, instead of on Jupyter Notebook.

mtreinish commented 1 year ago

I did reach out to the team inside IBM that maintained the package. They confirmed that the published version of the package did not work with recent versions of jupyter, they also said that nobody is maintaining the published package any more and it's not on their development roadmap to continue supporting it. It looks like they have deleted the pypi package (or at least I don't see it on pypi anymore) since.

TheFlightSimsOfficial commented 1 year ago

I did reach out to the team inside IBM that maintained the package. They confirmed that the published version of the package did not work with recent versions of jupyter, they also said that nobody is maintaining the published package any more and it's not on their development roadmap to continue supporting it. It looks like they have deleted the pypi package (or at least I don't see it on pypi anymore) since.

Thanks for the reply. I am just asking about using only CLI in my lab, and all members accepted this, so using the GUI composer is no longer required.

Anyways, hope the project will have the GUI on the web early. Still, the GUI is better.