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

[monitoring] Disable atproxy #126

Merged
merged 3 commits into from
Jul 12, 2023
Merged

Conversation

barroco
Copy link
Contributor

@barroco barroco commented Jul 12, 2023

Following up on #119 comments, the issue reported in #28 seems to be due to the atproxy. I would like to suggest to disable it for few days in the CI to see if the 999 timeout still occurs. If not, that would demonstrate that we isolated the cause of the problem. The atproxy client is replaced by an actual mock_uss when applicable. Please let me know if you would like to approach this differently.

@barroco barroco marked this pull request as ready for review July 12, 2023 13:32
Copy link
Contributor

@mickmis mickmis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, cheap way to rule out a cause for the timeout issue. We should just not forget to check this again later on.

Copy link
Member

@BenjaminPelletier BenjaminPelletier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm skeptical that atproxy is the cause of the timeout issue (rather than a cause) -- I initially assumed that was the case actually, but then I observed many timeouts from other services.

That being said, atproxy is not currently a critical tool and I agree with this troubleshooting step.

@barroco barroco merged commit 6aae027 into interuss:main Jul 12, 2023
@barroco barroco deleted the disable-atproxy branch July 19, 2023 22:27
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.

3 participants