Update async-container 0.18.3 → 0.34.2 (major)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

↗️ async-container (indirect, 0.18.3 → 0.34.2) · Repo · Changelog

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ async (indirect, 2.23.0 → 2.36.0) · Repo · Changelog

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ console (indirect, 1.29.3 → 1.34.3) · Repo · Changelog

Release Notes

1.34.1 (from changelog)

• Add process_id to serialized output records for clarity (pid is still included for backwards compatibility).
  • Add object_id to serialized output records only when the subject is not a string or class/module.

1.34.0 (from changelog)

• Allow Console::Compatible::Logger#add to accept **options.

1.32.0 (from changelog)

• Add fiber_id to serialized output records to help identify which fiber logged the message.
• Ractor support appears broken in older Ruby versions, so we now require Ruby 3.4 or later for Ractor compatibility, if you need Ractor support.

1.31.0 (from changelog)

Ractor compatibility.

The console library now works correctly with Ruby's Ractor concurrency model. Previously, attempting to use console logging within Ractors would fail with errors about non-shareable objects. This has been fixed by ensuring the default configuration is properly frozen.

# This now works without errors:
ractor = Ractor.new do
require 'console'
Console.info('Hello from Ractor!')
'Ractor completed successfully'
end

result = ractor.take
puts result # => 'Ractor completed successfully'

The fix is minimal and maintains full backward compatibility while enabling safe parallel logging across multiple Ractors.

Symbol log level compatibility.

Previously, returning symbols from custom log_level methods in configuration files would cause runtime errors like "comparison of Integer with :debug failed". This has been fixed to properly convert symbols to their corresponding integer values.

# config/console.rb - This now works correctly:
def log_level(env = ENV)
	:debug  # Automatically converted to Console::Logger::LEVELS[:debug]
end

While this fix maintains backward compatibility, the recommended approach is still to use integer values directly:

# config/console.rb - Recommended approach:
def log_level(env = ENV)
	Console::Logger::LEVELS[:debug]  # Returns 0
end

Improved output format selection for cron jobs and email contexts.

When MAILTO environment variable is set (typically in cron jobs), the console library now prefers human-readable terminal output instead of JSON serialized output, even when the output stream is not a TTY. This ensures that cron job output sent via email is formatted in a readable way for administrators.

# Previously in cron jobs (non-TTY), this would output JSON:

# {"time":"2025-06-07T10:30:00Z","severity":"info","subject":"CronJob","message":["Task completed"]}

# Now with MAILTO set, it outputs human-readable format:
# 0.1s info: CronJob
# | Task completed

This change is conservative and only affects environments where MAILTO is explicitly set, ensuring compatibility with existing deployments.

1.30.0 (from changelog)

Introduce Console::Config for fine grained configuration.

Introduced a new explicit configuration interface via config/console.rb to enhance logging setup in complex applications. This update gives the application code an opportunity to load files if required and control aspects such as log level, output, and more. Users can override default behaviors (e.g., make_output, make_logger, and log_level) for improved customization.

# config/console.rb
def log_level(env = ENV)
# Set a custom log level, e.g., force debug mode:
:debug
end

def make_logger(output = $stderr, env = ENV, **options)
# Custom logger configuration with verbose output:
options[:verbose] = true

 <span class="pl-v">Logger</span><span class="pl-kos">.</span><span class="pl-en">new</span><span class="pl-kos">(</span><span class="pl-s1">output</span><span class="pl-kos">,</span> **<span class="pl-s1">options</span><span class="pl-kos">)</span>

end

This approach provides a standard way to hook into the log setup process, allowing tailored adjustments for reliable and customizable logging behavior.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 40 commits:

• Bump patch version.
• Fix `Console::Filter` dynamic class creation and severity chaining. (#83)
• Bump patch version.
• Make safe output a bit less likely to truncate data.
• Fix tests.
• Bump patch version.
• Modernize code.
• Improved serialized log format.
• Bump minor version.
• Allow options in compatible logger. (#79)
• Modernize code.
• Fix `Ractor` tests.
• Fix env handling in `Console::Output.new`.
• Bump minor version.
• Explicit support for GitHub actions.
• Bump minor version.
• 100% documentation coverage.
• Limit Ractor support to 3.4+.
• Modernize code.
• Log fiber_id in serialized output.
• Bump minor version.
• Fix Ractor compatibility by freezing default configuration
• RuboCop.
• Fix symbol log level handling in Filter initialization.
• Prefer text output when MAILTO is set for cron job email readability.
• `Terminal::Text` print style reset before newline (#76)
• Modernize code.
• Fix #78: Add missing to_hash method to Console::Event::Generic
• Bump patch version.
• Add missing require.
• Bump patch version.
• Update copyrights.
• Remove circular require
• Fix test.
• Bump minor version.
• Updated guides.
• More test coverage.
• Introduce `Console::Config` for better control over log setup. (#70)
• 100% documentation coverage. (#71)
• Add missing `logger` gem for tests on Ruby head.

↗️ fiber-storage (indirect, 1.0.0 → 1.0.1) · Repo

Sorry, we couldn't find anything useful about this release.

↗️ io-event (indirect, 1.9.0 → 1.14.2) · Repo · Changelog

Release Notes

1.14.0 (from changelog)

Enhanced IO::Event::PriorityHeap with deletion and bulk insertion methods

The {ruby IO::Event::PriorityHeap} now supports efficient element removal and bulk insertion:

• delete(element): Remove a specific element from the heap in O(n) time
• delete_if(&block): Remove elements matching a condition with O(n) amortized bulk deletion
• concat(elements): Add multiple elements efficiently in O(n) time

heap = IO::Event::PriorityHeap.new

# Efficient bulk insertion - O(n) instead of O(n log n)
heap.concat([5, 2, 8, 1, 9, 3])

# Remove specific element
removed = heap.delete(5) # Returns 5, heap maintains order

# Bulk removal with condition
count = heap.delete_if{|x| x.even?} # Removes 2, 8 efficiently

The delete_if and concat methods are particularly efficient for bulk operations, using bottom-up heapification to maintain the heap property in O(n) time. This provides significant performance improvements:

• Bulk insertion: O(n log n) → O(n) for adding multiple elements
• Bulk deletion: O(k×n) → O(n) for removing k elements

Both methods maintain the heap invariant and include comprehensive test coverage with edge case validation.

1.11.2 (from changelog)

• Fix Windows build.

1.11.1 (from changelog)

• 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.0 (from changelog)

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.

1.10.2 (from changelog)

• Improved consistency of handling closed IO when invoking #select.

1.10.0 (from changelog)

• 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.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 50 commits:

• Bump patch version.
• Prefer `self` over `poolval`.
• Revert "Update ext/io/event/worker_pool.c"
• Bump patch version.
• Mark the thread from the worker pool. (#152)
• Minor syntax tidy up.
• Bump minor version.
• Introduce `IO::Event::PriorityHeap` bulk insert and delete.
• Bump minor version.
• Update context documentation on release.
• Modernize code.
• Add `IO::Event::PriorityHeap#empty?`.
• Benchmark experimentation.
• Bump patch version.
• Forward `**options` in `raise`.
• Bump minor version.
• Set minimum Ruby version appropriately.
• Reduce permutation size for test.
• Fix Windows non-block IO.
• Fix Ruby version support + more tests.
• Remove deprecated code.
• 100% documentation coverage.
• Add agent context.
• Modernize code.
• Ensure work can be cancelled while still in the queue.
• Bump patch version.
• Fix usage of `errno`.
• Add release notes.
• Remove unused header file include due to fix build error (#142)
• Bump patch version.
• Add documentation to `blocked`.
• Fix handling of `read_nonblock`. (#143)
• Extract build task into separate step.
• Add worker pool external tests.
• Bump minor version.
• Introduce `IO::Event::WorkerPool` for `blocking_operation_wait`. (#139)
• Bump patch version.
• Handle closed IO while invoking `#select`. (#138)
• Bump patch version.
• Modernize code.
• Use append_cflags instead of modifying CFLAGS directly (#137)
• Drop Ruby v3.1 external tests.
• Whitespace.
• Cleanup benchmark code.
• Updated benchmark servers.
• Bump minor version.
• Validate selector support at run time. (#131)
• Fix readme title.
• `IO::Event::Profiler` is moved to dedicated `fiber-profiler` gem.
• Remove unused `<complex.h>` header.

↗️ json (indirect, 2.10.2 → 2.18.1) · Repo · Changelog

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ metrics (indirect, 0.12.1 → 0.15.0) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 13 commits:

• Bump minor version.
• Improved `Metrics::Tags.normalize(tags, into = nil)`.
• Bump patch version.
• Modernize code.
• Bump minor version.
• Add agent context.
• Don't call `prepare` in `metrics/provider.rb`.
• Bump minor version.
• Add `bake metrics:provider:list` command.
• Modernize code.
• Bump patch version.
• Modernize code.
• Fix warn log test.

↗️ traces (indirect, 0.15.2 → 0.18.2) · Repo · Changelog

Release Notes

0.18.1 (from changelog)

• Don't call prepare in traces/provider.rb. It can cause circular loading warnings.

0.18.0 (from changelog)

• W3C Baggage Support - Full support for W3C Baggage specification for application-specific context propagation.

New Context Propagation Interfaces

Traces#trace_context and Traces.trace_context are insufficient for efficient inter-process tracing when using OpenTelemetry. That is because OpenTelemetry has it's own "Context" concept with arbitrary key-value storage (of which the current span is one such key/value pair). Unfortunately, OpenTelemetry requires those values to be propagated "inter-process" while ignores them for "intra-process" tracing.

Therefore, in order to propagate this context, we introduce 4 new methods:

• Traces.current_context - Capture the current trace context for local propagation between execution contexts (threads, fibers).
• Traces.with_context(context) - Execute code within a specific trace context, with automatic restoration when used with blocks.
• Traces.inject(headers = nil, context = nil) - Inject W3C Trace Context headers into a headers hash for distributed propagation.
• Traces.extract(headers) - Extract trace context from W3C Trace Context headers.

The default implementation is built on top of Traces.trace_context, however these methods can be replaced by the backend. In that case, the context object is opaque, in other words it is library-specific, and you should not assume it is an instance of Traces::Context.

0.17.0 (from changelog)

• Remove support for resource: keyword argument with no direct replacement – use an attribute instead.

0.16.0 (from changelog)

• Introduce traces:provider:list command to list all available trace providers.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 20 commits:

• Bump patch version.
• Modernize code.
• Bump patch version.
• Don't call `prepare` in `traces/provider.rb`.
• Bump minor version.
• Missing documentation.
• Use test backend for testing.
• Modernize code.
• Add `Traces.current_context` and `Traces.with_context`.
• Bump minor version.
• Clean up bake task output.
• Drop support for `resource:` keyword argument.
• Bump patch version.
• Restore missing documentation.
• Bump patch version.
• Add missing bake files.
• Bump minor version.
• Modernize code.
• Add `traces:provider:list` bake command.
• Remove unused sus-fixtures-console test dependency.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.