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

Write tests to ensure that tracking is detached when leaving service functions #1977

Open
andchiind opened this issue Jan 24, 2025 · 0 comments
Labels
epic feature New feature or request

Comments

@andchiind
Copy link
Contributor

andchiind commented Jan 24, 2025

Describe the new feature you would like to see
We have historically had issues with database objects being tracked in places they shouldn't, which has caused exceptions when updating the database. Currently the system is stable, but it would be easier to maintain in the future if we had tests to detect when issues occur.

Describe the solution you'd like
Any function which reads or writes to the database should clean up after itself, unless the "readonly: false" flag is set. The test itself should have access to the same context used in the functions it is testing, so we can check the tracking status of the database objects after the function is done running.

How will this feature affect the current Threat Model?
It will avoid a potential vulnerability.

@andchiind andchiind added epic feature New feature or request labels Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant