You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Seems like the python AST bridge is a bit too lax in identifying calls to cudaq.dbg.ast. Or is it cudaq.ast.dbg? Currently, it doesn't matter, as long as there is cudaq, ast and dbg, anything goes. Perhaps someone can argue that this is a feature.
Required prerequisites
Describe the bug
Seems like the python AST bridge is a bit too lax in identifying calls to
cudaq.dbg.ast
. Or is itcudaq.ast.dbg
? Currently, it doesn't matter, as long as there iscudaq
,ast
anddbg
, anything goes. Perhaps someone can argue that this is a feature.Steps to reproduce the bug
Result:
Expected behavior
Only accept
cudaq.dbg.ast
Is this a regression? If it is, put the last known working version (or commit) here.
Not a regression
Environment
Suggestions
No response
The text was updated successfully, but these errors were encountered: