Skip to content

Async scheduler / execution expired #442

Closed

Description

@travisbell

Hey @ioquatix,

I'm kind of just looking for some validation for a timeout error I am seeing:

/usr/local/bundle/gems/async-2.35.3/lib/async/scheduler.rb:247:in 'IO::Event::Selector::URing#transfer': execution expired (Faraday::TimeoutError)
	from /usr/local/bundle/gems/async-2.35.3/lib/async/scheduler.rb:247:in 'Async::Scheduler#block'
	from /usr/local/bundle/gems/async-2.35.3/lib/async/condition.rb:22:in 'Thread::Queue#pop'
	from /usr/local/bundle/gems/async-2.35.3/lib/async/condition.rb:22:in 'Async::Condition#wait'
	from /usr/local/bundle/gems/async-http-0.94.2/lib/async/http/protocol/http2/response.rb:110:in 'Async::HTTP::Protocol::HTTP2::Response::Stream#wait'
	from /usr/local/bundle/gems/async-http-0.94.2/lib/async/http/protocol/http2/response.rb:155:in 'Async::HTTP::Protocol::HTTP2::Response#wait'
	from /usr/local/bundle/gems/async-http-0.94.2/lib/async/http/protocol/http2/client.rb:46:in 'Async::HTTP::Protocol::HTTP2::Client#read_response'
	from /usr/local/bundle/gems/async-http-0.94.2/lib/async/http/protocol/http2/client.rb:36:in 'Async::HTTP::Protocol::HTTP2::Client#call'
	from /usr/local/bundle/gems/protocol-http-0.58.1/lib/protocol/http/request.rb:87:in 'Protocol::HTTP::Request#call'
	from /usr/local/bundle/gems/async-http-0.94.2/lib/async/http/client.rb:143:in 'Async::HTTP::Client#make_response'
	from /usr/local/bundle/gems/async-http-0.94.2/lib/async/http/client.rb:101:in 'Async::HTTP::Client#call'
	from /usr/local/bundle/gems/async-http-faraday-0.22.1/lib/async/http/faraday/adapter.rb:216:in 'block (2 levels) in Async::HTTP::Faraday::Adapter#perform_request'
	from /usr/local/bundle/gems/async-http-faraday-0.22.1/lib/async/http/faraday/adapter.rb:253:in 'block in Async::HTTP::Faraday::Adapter#with_timeout'
	from /usr/local/bundle/gems/async-2.35.3/lib/async/scheduler.rb:626:in 'Async::Scheduler#with_timeout'
	from /usr/local/bundle/gems/async-2.35.3/lib/async/task.rb:137:in 'Async::Task#with_timeout'
	from /usr/local/bundle/gems/async-http-faraday-0.22.1/lib/async/http/faraday/adapter.rb:252:in 'Async::HTTP::Faraday::Adapter#with_timeout'
	from /usr/local/bundle/gems/async-http-faraday-0.22.1/lib/async/http/faraday/adapter.rb:202:in 'block in Async::HTTP::Faraday::Adapter#perform_request'
	from /usr/local/bundle/gems/async-http-faraday-0.22.1/lib/async/http/faraday/adapter.rb:244:in 'block (2 levels) in Async::HTTP::Faraday::Adapter#with_client'
	from /usr/local/bundle/gems/async-http-faraday-0.22.1/lib/async/http/faraday/clients.rb:107:in 'Async::HTTP::Faraday::PersistentClients#with_client'
	from /usr/local/bundle/gems/async-http-faraday-0.22.1/lib/async/http/faraday/adapter.rb:243:in 'block in Async::HTTP::Faraday::Adapter#with_client'
	from /usr/local/bundle/gems/async-2.35.3/lib/kernel/sync.rb:25:in 'Kernel#Sync'
	from /usr/local/bundle/gems/async-http-faraday-0.22.1/lib/async/http/faraday/adapter.rb:233:in 'Async::HTTP::Faraday::Adapter#with_client'
	from /usr/local/bundle/gems/async-http-faraday-0.22.1/lib/async/http/faraday/adapter.rb:176:in 'Async::HTTP::Faraday::Adapter#perform_request'
	from /usr/local/bundle/gems/async-http-faraday-0.22.1/lib/async/http/faraday/adapter.rb:167:in 'Async::HTTP::Faraday::Adapter#call'

I am trying to figure out what's really happening here... so there's a timeout value that is set as part of the Faraday adapter that is ultimately being used as the total time this request takes to return? What confuses me is that this ultimately times out with IO::Event::Selector::URing#transfer? Is that expected?

Activity

  1. ioquatix commented on Jan 24, 2026

    @ioquatix
    Member

    Yes, that looks correct. The timeout fires while the client is waiting for the response:

    	from /usr/local/bundle/gems/async-http-0.94.2/lib/async/http/protocol/http2/response.rb:110:in 'Async::HTTP::Protocol::HTTP2::Response::Stream#wait'
    	from /usr/local/bundle/gems/async-http-0.94.2/lib/async/http/protocol/http2/response.rb:155:in 'Async::HTTP::Protocol::HTTP2::Response#wait'
    

    are the two key lines.

  2. locked and limited conversation to collaborators on Jan 24, 2026
  3. converted this issue into a discussion #443 on Jan 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions