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.

Sign up for GitHub

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

Jump to bottom

Signal timeout when locking task in getLongRunningOpCalls #8511

Closed
wants to merge 1 commit into from
Closed

Signal timeout when locking task in getLongRunningOpCalls #8511

wants to merge 1 commit into from

Commits on Jan 24, 2024

  1. Signal timeout when locking task in getLongRunningOpCalls 

    Summary:
If there are some problem (e.g. deadlock) with the mutex in `Task`,
`getLongRunningOpCalls` would block forever waiting for it.  In this case we
should signal the error and let the caller to generate some form of alerts.
This is important as we rely on `getLongRunningOpCalls` to detect blocking and
the function itself should not block.

Differential Revision: D53048088
    @Yuhta @facebook-github-bot
    Yuhta authored and facebook-github-bot committed Jan 24, 2024
    Configuration menu
    Copy the full SHA
    6396b5f View commit details
    Browse the repository at this point in the history