Skip to content

feat: string job names #643

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.

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

Closed
wants to merge 1 commit into from

Conversation

Ziinc
Copy link

@Ziinc Ziinc commented Jul 3, 2025

This PR adds in string names for quantum jobs.
Using atom names is inherently not scalable due to memory concerns when dealing with large number of alerts.

@maennchen
Copy link
Member

@Ziinc Thanks for your PR. This topic has come up before and we decided not to implement this.

  • Named Jobs (atom) are designed for static jobs
  • For everything else, you get a ref for the name. It is the users job to track those dynamic jobs.

Adding this now, would be a breaking change since it is handled by the Storage Behaviours. For those reasons, I'm closing this PR.

@maennchen maennchen closed this Jul 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants