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

Suggestion - Auto reconnect #49

Open
criptonauta opened this issue Dec 23, 2018 · 6 comments
Open

Suggestion - Auto reconnect #49

criptonauta opened this issue Dec 23, 2018 · 6 comments

Comments

@criptonauta
Copy link

Sometimes due to different reasons, internet gets disconnected, thus stopping service in Split Ticket Matcher. Would be possible to add auto re connection feature?

@matheusd
Copy link
Owner

Possibly. What exactly is the error you get when the internet goes out? A timeout against the matcher service or some other error?

@criptonauta
Copy link
Author

Dec 26 13:44:21: Error buying split ticket: error waiting for session: error while waiting to participate in session: rpc error: code = Unavailable desc = transport is closing

@rodrigondec
Copy link

rodrigondec commented Nov 21, 2019

Up! Is this planned to be implemented?

image

This error is raised on split ticket buyer main.go line 66. It could exist a force retry arg on CLI which could make a "for error != nil" statement on this line (or something more refined).

there are others possible errors which I would like to force retry, such as
image

@matheusd
Copy link
Owner

Probably should be done, yes.

@rodrigondec
Copy link

rodrigondec commented Nov 22, 2019

@matheusd where should I work on this? Branch master or release-v0.7?

I can only try this on branch release-v0.7. On master it's giving me a protocol version error

Error buying split ticket: error waiting for session: error while waiting to participate in session: rpc error: code = FailedPrecondition desc = server is running a different protocol version (4) than client (5)

@matheusd
Copy link
Owner

Yeah, master has a protocol change so probably better to base on release-v0.7

Repository owner deleted a comment Mar 4, 2024
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

3 participants