Hoping to adapt a few PRs addressing some bugs

[madejejej]

In 2021 at Castle we worked with @ioquatix because we found a few bugs and stability issues with the Ruby client. Unfortunately at the time we did not submit most of our changes to upstream. Would you be willing to take a look at these PRs and adapt them to the current codebase in some form or another?

• Do not fail when scan cannot be scheduled castle/aerospike-client-ruby#8
• Only apply timeout on a socket level castle/aerospike-client-ruby#7
• Use proper Ruby syntax for raising errors castle/aerospike-client-ruby#6
• More aggressive retry handling. castle/aerospike-client-ruby#5
• Improve robustness of retry mechanism. castle/aerospike-client-ruby#4

[khaf]

Of course. We'll take a look and integrate the reasonable changes.

[khaf]

@madejejej Are you still using the Ruby client with Aerospike server? May I ask what is your use case?

[madejejej]

Yeah, we're still using the Ruby client. We're in the fraud prevention industry and we're computing key-value aggregates in Aerospike