zarqman

Results 20 issues of zarqman

Since #153, it seems that `task.stop` can no longer forcefully stop an HTTP server task. In testing, consider something like this: ``` ### async-http enabled app server = Async::HTTP::Server.new(...) server_task...

Calling `native` leaves the internal `@mask_addr` as its ipv6 mask instead of converting it to an ipv4 mask. This is most easily seen when calling `prefix`, but also breaks `to_range`...

In a Rails 7.1 app, empty responses are now missing the `content-length` header when used with Rack 3.1. On Rack 3.0, the header is present with the expected value of...

When using Rails, this changes the NATS reloader to use the Rails `executor` instead of the `reloader`. This continues to meet the objectives originally outlined in #120. Rails' reloader is...

This PR fixes a bunch of ruby warnings. There are no changes in behavior. Tested on Ruby 3.3. ``` gems/nats-pure/lib/nats/io/jetstream.rb:14: warning: gems/nats-pure/lib/nats/io/jetstream.rb:14: warning: loading in progress, circular require considered harmful...

`uri` is missing as a gem dependency. Fixes: (tested on ruby 3.3) ``` An error occurred while loading ./spec/client_threadsafe_spec.rb. Failure/Error: major_version, minor_version, _ = Gem.loaded_specs['uri'].version.to_s.split('.').map(&:to_i) NoMethodError: undefined method `version' for...

## Bug Report **Describe the bug** The `docker_events` input fails to wait for `retry_interval` between retries when `retry_limits` is `-1`. Retries are attempted as fast as fluent-bit can go. **To...

status: waiting-for-triage

**Summary**: Non-digested assets (including those _outside_ `/public/assets`) default to the same 1 year cache period in cache-control as digested assets. Since non-digested assets are mutable, a 1 year cache period...

With reproduction steps

Seeing an issue where this block yields a Response with all `nil` values: ```ruby Async::HTTP::Internet.post(metrics_url, headers:, body:) do |response| pp st: response.status, hdr: response.headers, bdy: response.body # => {st: nil,...

### Observed behavior It appears that the thread pool that manages a connection's subscriptions is not being closed/shutdown when the connection is closed. As a result, threads are endlessly added...

defect