Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable serialized python code execution #2607

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
+3 −3
Open

Enable serialized python code execution #2607

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
d932482
Enabling the serialized code execution feature
sacpis Feb 10, 2025
6f78dec
Fixing the remote-mqpu and nvqc links
sacpis Feb 11, 2025
412cf89
Merge branch 'main' into nvqc_serialized_python_code_execution
sacpis Feb 15, 2025
687bd79
Merge branch 'main' into nvqc_serialized_python_code_execution
sacpis Mar 11, 2025
7b280c7
Merge branch 'main' into nvqc_serialized_python_code_execution
sacpis Mar 13, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions tools/cudaq-qpud/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,8 @@ This file contains tips and tricks for when you are performing manual testing/
debugging for `remote-mqpu` or `nvqc` targets. This file is primarily intended
for **CUDA-Q developers, not end users**. See the user-facing docs here:

- [`remote-mqpu`](https://nvidia.github.io/cuda-quantum/latest/using/backends/platform.html#remote-mqpu-platform)
- [`nvqc`](https://nvidia.github.io/cuda-quantum/latest/using/backends/nvqc.html)
- [`remote-mqpu`](https://nvidia.github.io/cuda-quantum/latest/using/backends/sims/mqpusims.html#multi-qpu-other-backends)
- [`nvqc`](https://nvidia.github.io/cuda-quantum/latest/using/backends/cloud/nvqc.html)

## Fully local within `cuda-quantum-dev` container

Expand Down
2 changes: 1 addition & 1 deletion tools/cudaq-qpud/nvqc_proxy.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@
WATCHDOG_TIMEOUT_SEC = 0
RUN_AS_NOBODY = False # Expect this to be overridden to true for NVQC deployment
SUDO_FOUND = False
CUDAQ_SER_CODE_EXEC = False
CUDAQ_SER_CODE_EXEC = True
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to make this the default? It is currently "opt in", where you must set an environment variable in the deployment in order to activate this (see line 270). If we make this change, then it will become "opt out".

Copy link
Collaborator Author

@sacpis sacpis Feb 11, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I think we are planning to make it the default. @bettinaheim can confirm that. As there will be only one paid tier going forward.

So that even if we set the env variable to any value (True or False) it will take that value. If we don't, then the default will be True. So the env variable (if set) in the deployment will always takes precedence.



def build_command_list(temp_file_name: str) -> list[str]:
Expand Down
Loading