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

APIGOV-01234 remove mutex in healthchecker.go #468

Merged
merged 7 commits into from
Jun 30, 2022
Merged

APIGOV-01234 remove mutex in healthchecker.go #468

merged 7 commits into from
Jun 30, 2022

Conversation

tsjohns9
Copy link
Contributor

No description provided.

dfeldick
dfeldick previously approved these changes Jun 29, 2022
vivekschauhan
vivekschauhan previously approved these changes Jun 29, 2022
@tsjohns9 tsjohns9 dismissed stale reviews from vivekschauhan and dfeldick via a9aeae2 June 29, 2022 21:24
dfeldick
dfeldick previously approved these changes Jun 29, 2022
vivekschauhan
vivekschauhan previously approved these changes Jun 29, 2022
@tsjohns9 tsjohns9 changed the title APIGOV-01234 update APIGOV-01234 remove mutex in healthchecker.go Jun 30, 2022
@rbissey-axway
Copy link
Contributor

Hi guys,

Thanks for your quick fix!
With this branch I'm not able to reproduce our issue (https://jira.axway.com/browse/STREAMS-2838) regarding the blocked healthchecks.

I've just a little comment related to this MR: now, the statusMutex attribute of the struct statusCheck (in healthcheck/definition.go) seems to be useless and could be removed (correct me if I'm wrong).

When your validation process will be passed for this fix (integrated on the main branch), could you publish a new Agent-SDK release with this fix to allow us to use a public release?

Best regards,

Romain BISSEY.

@tsjohns9 tsjohns9 merged commit dfa1642 into main Jun 30, 2022
@tsjohns9 tsjohns9 deleted the APIGOV-01234 branch June 30, 2022 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants