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

Accessing underlying TimedOutOperationStatus #57

Open
lloydmeta opened this issue Aug 18, 2017 · 0 comments
Open

Accessing underlying TimedOutOperationStatus #57

lloydmeta opened this issue Aug 18, 2017 · 0 comments
Assignees

Comments

@lloydmeta
Copy link
Collaborator

lloydmeta commented Aug 18, 2017

Currently there are 2 ways to get a TimedOutStatus from Shade:

  1. Timeout from the scheduler:

    Success(FailedResult(key, TimedOutStatus))

  2. Timeout from the Spymemcached layer translated into a TimedOutStatus

    case _: TimedOutOperationStatus =>
    TimedOutStatus

For the purposes of debugging, it would be nice to be able to distinguish between the two.

How

I think one way to do this is by turning the existing case object TimedOutStatus into a final case class TimedOutStatus(underlying: Option[TimedOutOperationStatus]).

The other way to do this might be to introduce a whole knew case object for either one of the aforementioned cases.

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

No branches or pull requests

2 participants