Puma initialization issue

[gingermusketeer]

I have setup the gem with the recommended initialization approach for rails apps but if there is an issue during startup It puts puma into a loop until it is able to connect to the unleash server.

This often has a result of requiring me to restart my computer as puma seems to create processes until this is successful.

Would it make sense for the initial connection to result in a warning instead?

Also is using the on_worker_boot required if using puma? The reason I ask is that it means that Rails.configuration.unleash is not present in the rails console. Having this available is handy for debugging.

[rarruda]

This is not a scenario I have tested.

But note, puma creates multiple workers by default. Unleash-client needs to have one client instantiated per worker, and each client (by default) has two threads per client.

Also note that the scheduled tasks will stop retrying after 3 exceptions in a row, to avoid errors getting thrown all the time, like you are mentioning. See https://github.com/Unleash/unleash-client-ruby/blob/master/lib/unleash/scheduled_executor.rb#L31

I will try to recreate your issue locally, and will get back to you soon.

[gingermusketeer]

I have tried to reproduce this problem again but have been unable to do so. I suspect that either upgrading to the latest version of puma or this gem has resolved the issue.