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

Jump to bottom

Surge++ should handle error condition of multiple nodes better #1358

Closed
baconpaul opened this issue Dec 1, 2019 · 1 comment
Closed

Surge++ should handle error condition of multiple nodes better #1358

baconpaul opened this issue Dec 1, 2019 · 1 comment

Comments

@baconpaul
Copy link
Collaborator

Right now each guiid can have between 0 and 1 nodes and, if there is 1 node, 0 or more readonly nodes. We do not enforce this at parse time though. So

  1. If at parse time we find two nodes for the same guiid issue an error
  2. If at parse time we find a readonlynode for a guiid and no node, issue an error.
@baconpaul baconpaul added this to the Surge++ alpha 1 milestone Dec 1, 2019
@baconpaul
Copy link
Collaborator Author

Re-tooling the S++ plan so closing these issues.

@bobobo199733 bobobo199733 mentioned this issue Mar 5, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mkruselj @baconpaul