Publishing is failing possibly due to timeout validating quantum_transformer.ipynb
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.1k
- Forks
- 456
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 165
Description
Required prerequisites
- Consult the security policy. If reporting a security vulnerability, do not report the bug using this form. Use the process described in the policy to report the issue.
- Make sure you've read the documentation. Your issue may be addressed there.
- Search the issue tracker to verify that this hasn't already been reported. +1 or comment there if it has.
- If possible, make a PR with a failing test to give us a starting point to work on!
Describe the bug
The publishing pipeline is getting a context cancelled which is usually related to timeouts when validating the newly added quantum_transformer.ipynb in https://github.com/NVIDIA/cuda-quantum/actions/runs/13640844145/job/38132888363#step:5:1361. This notebook was recently added in https://github.com/NVIDIA/cuda-quantum/pull/2614
Steps to reproduce the bug
Run the publishing pipeline
Expected behavior
Publishing passes
Is this a regression? If it is, put the last known working version (or commit) here.
Not a regression
Environment
- CUDA-Q version: latest
- Python version:
- C++ compiler:
- Operating system:
Suggestions
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the publishing pipeline run linked in the issue, especially the validation step that reports context cancelled, and inspect quantum_transformer.ipynb and PR 2614. Determine whether notebook validation is timing out, then verify the publishing pipeline completes successfully without weakening validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, python
- Domain
- ci-cd, documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100