bugfix: fix conn busy err #436
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
choffmann
force-pushed
the
bugfix/fix-conn-busy-err
branch
from
fecaf8d to
7b0c259
Compare
choffmann
force-pushed
the
bugfix/fix-conn-busy-err
branch
from
7b0c259 to
960de13
Compare
xk0niR
approved these changes
Feb 24, 2025
There was a problem hiding this comment.
What I tested:
Fill my database with tbz trees: OK
--- Easy Tests
vehicle: create/update/delete: OK
tree: create/update/delete: OK
treecluster: create/update/delete: OK
watering plan: create/update/delete: OK
sensors: There is no create or update (except manually editing database)
I deleted a sensor successfully with swagger: OK
--- Extended tests
Created treecluster t1 and treeclusgter t2
Tree from t1 to t2:
- gets removed from t1: OK
- gets added to t2: OK
I have also tested other functions without any error. 🥇
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Close #427
Close #429
This issue fixes common issues with multiple users working on the same object at the same time