Skip to content

Conversation

@PopFlamingo
Copy link
Contributor

I can't really easily reproduce the specific error that caused the logging, but as far as I can tell this is where it came from and I also didn't see this message anymore in my logs.

I was wondering if I should just drop it entirely or maybe still log it under the trace level for instance?

@ktoso
Copy link
Member

ktoso commented Jul 9, 2022

Ah this looks right, thank you -- would you mind merging this case with the one above it? It's the same intent between them (so that the handling has a comment)

@PopFlamingo
Copy link
Contributor Author

@ktoso Done! Should I also make the comment more generic?

@ktoso
Copy link
Member

ktoso commented Jul 9, 2022

Hm yeah, just that timeouts are an expected thing here really

@PopFlamingo
Copy link
Contributor Author

Ok, I modified it a bit.

@ktoso
Copy link
Member

ktoso commented Jul 9, 2022

LGTM thank you!

@ktoso
Copy link
Member

ktoso commented Jul 9, 2022

We have one very flaky test since recently, I'll get to it soon. Tests good other than that one

@ktoso ktoso merged commit 50cd99a into apple:main Jul 9, 2022
@PopFlamingo
Copy link
Contributor Author

Oops it looks like I missed something and the error was actually RemoteCallError.timedOut and not TimeoutError, will make another PR to fix it.

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.

Silence remote call timeout logging

2 participants