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.

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

Cannot load pulses if PulseStorage is default registry #301

Closed
lumip opened this issue Jul 12, 2018 · 1 comment
Closed

Cannot load pulses if PulseStorage is default registry #301

lumip opened this issue Jul 12, 2018 · 1 comment

Comments

@lumip
Copy link
Contributor

lumip commented Jul 12, 2018

Using a PulseStorage object as default pulse registry prevents pulses from being loaded with a "Pulse with name already exists" error. Upon creation of the deserialized PulseTemplate object, it will try to register with the default registry (the PulseStorage object), which already has a pulse registered with that name (the serialization of the just deserialized pulse).

@lumip lumip added the Bug label Jul 12, 2018
@lumip lumip added this to the New Serialization Routines milestone Jul 12, 2018
lumip added a commit that referenced this issue Jul 12, 2018
@lumip
Copy link
Contributor Author

lumip commented Jul 12, 2018

Demonstrated by new test in branch issues/301_pusle_storage_as_default_issue .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant