Handle nullptr from getTimekeeperSingleton
Summary: According to folly::Singleton::try_get(), https://fburl.com/23wqby9i, the caller is responsible for handling a nullptr return. In this case, we handle it poorly, via a crash both in production and debug code. This diff opts for handling the nullptr more gracefully, via a future loaded with an exception. Reviewed By: yfeldblum Differential Revision: D6006864 fbshipit-source-id: e8fde57ed161b33fa1f157ce663ed85e69640c25
Showing
Please register or sign in to comment