Skip to content
This repository has been archived by the owner on Jul 28, 2023. It is now read-only.

IBM Quantum Provider API Reference TOC doesn't match with the code #1165

Open
y4izus opened this issue Feb 2, 2022 · 1 comment
Open

IBM Quantum Provider API Reference TOC doesn't match with the code #1165

y4izus opened this issue Feb 2, 2022 · 1 comment

Comments

@y4izus
Copy link

y4izus commented Feb 2, 2022

Informations

It's a documentation related issue so no need of Qiskit or Python versions nor Operating System

What is the current behavior?

The TOC on the documentation page for IBM Quantum Provider API Reference doesn't match the code

  1. Links on the page:
  • ibmq_provider ✔
  • ibmq_job ✔
  • ibmq_managed ✔
  • ibmq_credentials ✔
  • ibmq_utils ✔
  • ibmq_random ❌
  • ibmq_experiment ✔
  • ibmq_runtime
  1. Links on the code:
  • ibmq_provider ✔
  • ibmq_job ✔
  • ibmq_managed ✔
  • ibmq_credentials ✔
  • ibmq_visualization ❌
  • ibmq_jupyter ❌
  • ibmq_utils ✔
  • ibmq_experiment
  • ibmq_runtime ✔

Steps to reproduce the problem

Go to the links above and compare

What is the expected behavior?

Contents should match

Suggested solutions

I thought that after this commit we didn't deploy the docs, but I have checked and we did, so I have no idea why the info is not matching

Notes

This issue is related with this one, but I've opened it because, as far as I know, we stopped using Travis in favor of GitHub actions and also there is a new line that doesn't match

@jakelishman
Copy link
Member

The first point is because the metapackage pulls from its requirements, so it won't update until IBM Q provider puts out a new patch release, and we include it in the metapackage. We can arrange to do that soon - Terra is going to do a patch release today or tomorrow as well.

@1ucian0 1ucian0 transferred this issue from Qiskit/qiskit-metapackage Mar 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
No open projects
Status: Backlog
Development

No branches or pull requests

2 participants