Ry Biesemeyer

Results 49 issues of Ry Biesemeyer

In order to accelerate the getting-started experience with self-secured Elasticsearch clusters, eliminate the requirement to side-load specifically-formatted CA files to disk by allow users to provide the _fingerprint_ of their...

enhancement
meta
status:needs-triage

## Release notes [rn:skip] ## What does this PR do? Adds an `HistoricMetric` implementation for tracking metric _rates_ (current/1m/5m/15m/lifetime), for eventual inclusion into the node stats API responses or for...

enhancement
status:work-in-progress

When troubleshooting throughput issues, it is often helpful to determine whether the bottleneck is the input's ability to _produce_ or the pipeline workers' collective ability to _consume_, because the location...

enhancement
discuss

Between [here](https://github.com/resque/resque/blob/887ab8eea3ba4ef1ea7915812f70176a40d247f6/lib/resque/worker.rb#L388) in `Resque::Worker#reserve` and [here](https://github.com/resque/resque/blob/887ab8eea3ba4ef1ea7915812f70176a40d247f6/lib/resque/worker.rb#L366) in `Resque::Worker#process_job`, anything that happens to the process will cause the job to lost into the ether. Granted there isn't much that happens in-between,...

Feature
Hard

Realistically, ActiveSupport's `Time.zone` being set and `Timecop.freeze`-ing with `Date` objects are not compatible. `Date` is a lossy representation of `Time` in Ruby anyway since it doesn't store offset, and the...

It would be helpful if this project would define a module manifest, so that I could avoid exporting java module internals to `ALL-UNNAMED` in Java 17+. I understand I would...

Supersedes #115 Supersedes #122

status:needs-review

I've run a number of performance tests to get the raw throughput _per-worker_ to determine how different variables affect the throughput of the grok, and determined that the changes to...

Since these are especially destructive (beyond the scope of the namespace) and rather surprising to anyone who would think that namespacing provides segregation, perhaps `#flushall` and `#flushdb` should be blocked...

The last 1.x version should support ALL of these changes when `Redis::Namespace#initialize` is called with `deprecations: true` OR the `REDIS_NAMESPACE_DEPRECATIONS` environment varible set, and should warn unless `Redis::Namespace#initialize` is called...