ytti/oxidized · error · ArgumentError

Exec: configuration invalid: invalid timeout value

Error message

Exec: configuration invalid: invalid timeout value

What it means

Error "Exec: configuration invalid: invalid timeout value" thrown in ytti/oxidized.

Source

Thrown at lib/oxidized/hook/exec.rb:14

class Exec < Oxidized::Hook
  include Process

  def initialize
    super
    @timeout = 60
    @async = false
  end

  def validate_cfg!
    # Syntax check
    if cfg.has_key? "timeout"
      @timeout = cfg.timeout
      raise "invalid timeout value" unless @timeout.is_a?(Integer) &&
                                           @timeout.positive?
    end

    @async = !!cfg.async if cfg.has_key? "async"

    if cfg.has_key? "cmd"
      @cmd = cfg.cmd
      raise "invalid cmd value" unless @cmd.is_a?(String) || @cmd.is_a?(Array)
    end
  rescue RuntimeError => e
    raise ArgumentError,
          "#{self.class.name}: configuration invalid: #{e.message}"
  end

  def run_hook(ctx)
    env = make_env ctx
    logger.debug "Execute: #{@cmd.inspect}"
    th = Thread.new do

View on GitHub (pinned to 687ed4262d)

When it happens

Trigger: Thrown at lib/oxidized/hook/exec.rb:14 when the library encounters an invalid state.

Common situations: See trigger scenarios.

Understand the failure class

• Timeouts: ETIMEDOUT, deadlines, and hung requests — what actually expires when a request times out.

AI-assisted analysis of ytti/oxidized@687ed4262d (2026-08-23). Data as JSON: /api/errors/aae9e6839aec329b. Report an issue: GitHub.