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

Updates stop working after some time #81

Closed
aserafin opened this issue Feb 19, 2017 · 6 comments
Closed

Updates stop working after some time #81

aserafin opened this issue Feb 19, 2017 · 6 comments

Comments

@aserafin
Copy link

aserafin commented Feb 19, 2017

Hi,

I have issue with your latest gem release

gem 'ldclient-rb', '2.0.5'
gem 'ld-celluloid-eventsource', '0.8.3'

what I'm seeing is that is starts working correctly, I'm getting information about waiting for heartbeats for 300s, I can see messages when I change flag value from the ui but after some time I get this in logs

[EventSource] Didn't get heartbeat after 300 seconds. Reconnecting.

and after this message none of the changes made in ui are passed to the application. I have to restart entire ruby process to make it work again.

I'm not seeing this issue with this combination

gem 'ldclient-rb', '2.0.3'
gem 'ld-celluloid-eventsource', '0.5.0'

but I've noticed that a lot off stuff changed regarding ld-celluloid-eventsource between the releases.

@drichelson
Copy link
Contributor

@aserafin Thanks for reaching out. Do you mind emailing support@launchdarkly.com and we can continue troubleshooting there?

@drichelson
Copy link
Contributor

Conversation switched to support@launchdarkly.com. Closing this issue

@aserafin
Copy link
Author

@drichelson you said on the support email that this problem is happening to you and that you were working on a fix but not messages from you since. Could you please get back to me on that topic?

@atrakh
Copy link

atrakh commented Oct 31, 2017

Hey @aserafin - the Ruby SDK has since been updated. Are you still experiencing this issue on ruby-client versions >= 2.1.0?

@atrakh atrakh reopened this Oct 31, 2017
@atrakh atrakh closed this as completed Dec 11, 2017
@aserafin
Copy link
Author

@atrakh it looks like we still have this issue - we should be getting around with updating to the latest client version that hopefully will solve it but if not I will post here so maybe you can reopen again.

@atrakh
Copy link

atrakh commented Dec 12, 2017

Hi @aserafin - thanks for the update.

I'm reopening this ticket so that we can pick up where we left off. Let us know if you still run into this issue after updating your client.

@atrakh atrakh reopened this Dec 12, 2017
@atrakh atrakh closed this as completed Sep 27, 2018
eli-darkly added a commit that referenced this issue Oct 15, 2018
fix logic for whether a flag is tracked in all_flags_state
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