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

Try and come up with means to protect against introducing local stuff into global data areas #1238

Open
Tracked by #1508
AndrewSisley opened this issue Mar 27, 2023 · 0 comments
Labels
area/db-system Related to the core system related components of the DB area/testing Related to any test or testing suite

Comments

@AndrewSisley
Copy link
Contributor

We currently have leaks a local element into the DAG (spotted, but not introduced in: #1235), it can potentially be a very painful/expensive form of bug and they may require very expensive datafixes in order to correct once the leak has been fixed.

As stuff like P2P and Schema Updates expands and gets used more regularly, we should invest time into coming up with a means to protect against this class of issue - perhaps something similar to the change detector, although I do not know what the solution may look like.

@AndrewSisley AndrewSisley added area/db-system Related to the core system related components of the DB area/testing Related to any test or testing suite labels Mar 27, 2023
@AndrewSisley AndrewSisley added this to the DefraDB v0.5.1 milestone Mar 27, 2023
@AndrewSisley AndrewSisley changed the title Try and come up with means to protect against introducing local stuff into global areas Try and come up with means to protect against introducing local stuff into global data areas Mar 27, 2023
@fredcarle fredcarle removed this from the DefraDB v0.6 milestone May 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/db-system Related to the core system related components of the DB area/testing Related to any test or testing suite
Projects
None yet
Development

No branches or pull requests

2 participants