-
Notifications
You must be signed in to change notification settings - Fork 27
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
🐛 Hot-fix: Ensure synchronization between projects/workbench and projects_nodes #4617
🐛 Hot-fix: Ensure synchronization between projects/workbench and projects_nodes #4617
Conversation
Kudos, SonarCloud Quality Gate passed!
|
Code Climate has analyzed commit 669921c and detected 0 issues on this pull request. View more on Code Climate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm Thanks.
Codecov Report
@@ Coverage Diff @@
## master #4617 +/- ##
=========================================
- Coverage 86.8% 82.5% -4.3%
=========================================
Files 1049 310 -739
Lines 44557 15700 -28857
Branches 1016 0 -1016
=========================================
- Hits 38697 12962 -25735
+ Misses 5632 2738 -2894
+ Partials 228 0 -228
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
What do these changes do?
This PR fixes the issue with synchronization between the projects table workbench column and the projects_nodes table.
The problem arises due to the following issues:
On node creation the frontend does:
POST /projects/{project_id}/nodes
and does not wait for an answerPUT /projects/{project_id}
arrives soon after with the new node in the workbench --> works since 1. call is fastOn node deletion the frontend does:
DELETE /projects/{project_id}/nodes/{node_id}
and does not wait for an answer although that call is slow when a dynamic service needs to be removed (typically from .5s to several seconds).PUT /projects/{project_id}
arrives soon after with the node already removed from the workbench. the call is fast an changes projects/workbench.This is a quick fix that could be applied to production code. the long fix will come after this one.
Also it would make sense that the frontend waits for the node creation/deletion calls before sending PUT calls.
Related issue/s
How to test
DevOps Checklist