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

Decide what happens when response fails to deserialize... #700

Closed
source-of-truth bot opened this Issue Jan 24, 2019 · 2 comments

Comments

Projects
None yet
1 participant
@source-of-truth
Copy link

source-of-truth bot commented Jan 24, 2019

// TODO: Decide what happens when response fails to deserialize
Err(e) => info!("Failed to deserialize response: {:?}", e),

@D4nte

This comment has been minimized.

Copy link
Member

D4nte commented Feb 3, 2019

Now specified in RFC-001. (ignore) TODO can be removed.

@source-of-truth

This comment has been minimized.

Copy link
Author

source-of-truth bot commented Feb 13, 2019

Closed in commit 1c9f2ceeb620bd14997661d0bb99df4e8a99f0f7 pushed by @mergify[bot]

@source-of-truth source-of-truth bot closed this Feb 13, 2019

@wafflebot wafflebot bot removed the sprint-backlog label Feb 13, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.