Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Quantum engine job URLs
See original GitHub issueIs your feature request related to a use case or problem? Please describe.
URLs to the webpage showing jobs scheduled on the quantum engine requires knowing details of the structure of the URLs that users are unlikely to remember. Context: #3304.
Describe the solution you’d like
Add an easily discoverable function that returns the URL for a given quantum engine job, i.e. URL like
https://console.cloud.google.com/quantum/programs/PROGRAM_ID/jobs/JOB_ID/overview?project=PROJECT_ID
What is the urgency from your perspective for this issue? Is it blocking important work?
P3 - I’m not really blocked by it, it is an idea I’d like to discuss / suggestion based on principle
Issue Analytics
- State:
- Created 3 years ago
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Great suggestion, thanks. What do you think of adding a
console_url()method to each of the Engine resources? Specifically, EngineProgram, EngineJob, and EngineProcessor?SGTM. I marked this as “before” because it was expected to be small, but there’s nothing in it that’s breaking.