Up to [cvs.NetBSD.org] / pkgsrc / devel / ruby-io-event
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
devel/ruby-io-event: update to 1.22.3 1.22.2 (not released) 1.22.3 (2026-10-18) * Sign releases with the shared Socketry certificate. #237
devel/ruby-io-event: update to 1.13.0 1.13.0 (2025-09-01) * Add IO::Event::PriorityHeap#empty?. * Update context documentation on release.
devel/ruby-io-event: update to 1.12.1 1.11.1 (2025-07-02) * Fix read_nonblock when using the URing selector, which was not handling zero-length reads correctly. This allows reading available data without blocking. 1.11.2 (2025-07-02) * Fix Windows build. 1.12.0 (2025-07-13) * Ensure work can be cancelled while still in the queue. * 100% documentation coverage. * Remove deprecated code. * Fix Ruby version support + more tests. * Fix Windows non-block IO. 1.12.1 (2025-07-23) * Forward **options in raise.
devel/ruby-io-event: update to 1.11.0
1.11.0 (2025-06-13)
Introduce IO::Event::WorkerPool for off-loading blocking operations.
The {ruby IO::Event::WorkerPool} provides a mechanism for executing blocking
operations on separate OS threads while properly integrating with Ruby's
fiber scheduler and GVL (Global VM Lock) management. This enables true
parallelism for CPU-intensive or blocking operations that would otherwise
block the event loop.
# Fiber scheduler integration via blocking_operation_wait hook
class MyScheduler
def initialize
@worker_pool = IO::Event::WorkerPool.new
end
def blocking_operation_wait(operation)
@worker_pool.call(operation)
end
end
# Usage with automatic offloading
Fiber.set_scheduler(MyScheduler.new)
# Automatically offload `rb_nogvl(..., RB_NOGVL_OFFLOAD_SAFE)` to a background thread:
result = some_blocking_operation()
The implementation uses one or more background threads and a list of pending
blocking operations. Those operations either execute through to completion
or may be cancelled, which executes the "unblock function" provided to
rb_nogvl.
devel/ruby-io-event: update to 1.10.0 1.10.0 (2025-03-12) * IO::Event::Profiler is moved to dedicated gem: fiber-profiler. * Perform runtime checks for native selectors to ensure they are supported in the current environment. While compile-time checks determine availability, restrictions like seccomp and SELinux may still prevent them from working.
devel/ruby-io-event: update to 1.9.0 1.9.0 (2025-02-10) * Improved IO::Event::Profiler for detecting stalls.
devel/ruby-io-event: update to 1.8.4 1.8.0 (2025-02-05) Detecting fibers that are stalling the event loop. A new (experimental) feature for detecting fiber stalls has been added. This feature is disabled by default and can be enabled by setting the IO_EVENT_SELECTOR_STALL_LOG_THRESHOLD to true or a floating point number representing the threshold in seconds. When enabled, the event loop will measure and profile user code when resuming a fiber. If the fiber takes too long to return back to the event loop, the event loop will log a warning message with a profile of the fiber's execution. > cat test.rb #!/usr/bin/env ruby require_relative "lib/async" Async do Fiber.blocking do sleep 1 end end > IO_EVENT_SELECTOR_STALL_LOG_THRESHOLD=true bundle exec ./test.rb Fiber stalled for 1.003 seconds /home/samuel/Developer/socketry/async/test.rb:6 in '#<Class:Fiber>#blocking' (1s) /home/samuel/Developer/socketry/async/test.rb:7 in 'Kernel#sleep' (1s) There is a performance overhead to this feature, so it is recommended to only enable it when debugging performance issues. 1.8.1 (2025-02-05) * Fix macOS build issues. * Initial rework of call tracking. 1.8.2 (2025-02-05) * Rename event -> call. * Fix profiling. 1.8.3 (2025-02-05) * Output profile log as JSON if !istty. 1.8.4 (2025-02-05) * Correctly calculate total duration in output formatting.
devel/ruby-io-event: update to 1.7.5 1.7.5 (2024-12-15) * Fix process_wait race condition on EPoll that could cause a hang.
devel/ruby-io-event: update to 1.6.0 1.6.0 (2024-06-03) * Fix IO_Event_Selector_EPoll -> KQueue typo. * Increase duration of select to avoid issues on slow systems. * Add priority heap and timers implementation. (#100)
devel/ruby-io-event: update to 1.3.2 1.3.0 (2023-08-23) What's Changed * Rename data -> selector. by @ioquatix in #67 * Spurious wakeups by @ioquatix in #66 * Don't use EPOLLONESHOT for the wakeup event. by @Math2 in #68 * Failing test case for waiting on a reused FD. by @Math2 in #69 * Always re-register epoll descriptor. by @ioquatix in #71 * Fix potential race conditions in io_uring backend. by @ioquatix in #70 * NetBSD/OpenBSD compatibility for KQueue selector, some FreeBSD fixes by @Math2 in #72 * Introduce correct support for compacting GC. by @ioquatix in #73 * Fix external tests by @ioquatix in #75 * Add more external tests. by @ioquatix in #74 * Run coverage tests on more Ruby versions. by @ioquatix in #76 1.3.1 (2023-08-24) What's Changed * Fix a weird bug with duplicate CQEs. by @ioquatix in #78 1.3.2 (2023-08-24) What's Changed * Ensure that every io_uring_get_sqe is used correctly. by @ioquatix in #80 * Add tests for cancellation and update pure Ruby implementation. by @ioquatix in #79
devel/ruby-io-event: add package version 1.1.2 Required by ruby-async package. IO::Event Provides low level cross-platform primitives for constructing event loops, with support for select, kqueue, epoll and io_uring. Motivation The initial proof-of-concept Async was built on NIO4r. It was perfectly acceptable and well tested in production, however being built on libev was a little bit limiting. I wanted to directly built my fiber scheduler into the fabric of the event loop, which is what this gem exposes - it is specifically implemented to support building event loops beneath the fiber scheduler interface, providing an efficient C implementation of all the core operations.