use stricter mutex policy to prevent installed.json corruption #635
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.
Please check if the PR fulfills these requirements
before creating one)
Bug fix, followup of #585
Sometimes the agent responds with a 500 error to
curl ‘http://127.0.0.1:8991/v2/pkgs/tools/installed’
with this payload{“name”:“fault”,“id”:“JOhq4y8g”,“message”:“invalid character ‘s’ after top-level value”,“temporary”:false,“timeout”:false,“fault”:true}
.This error should be caused by a race condition with the result that
installed.json
file gets corruptedThis PR should fix this behavior by adding a stricter mutex policy and releasing the mutex only after the file has been written
no