coldpass

DataDog/datadog-api-client-ruby

GitHub ↗ · How this check works

Per-setup public labels: Linux / Haiku: Works

Static status badge · SVG · read-only JSON. Embed with ![Coldpass status](https://coldpass.dev/badge/DataDog--datadog-api-client-ruby.svg).

datadogdatadog-apiopenapiruby

Works

Only older checks are saved; no current product test.

Answers apply to each recorded setup, revision and operation. Earlier observations remain in Run details.

Tested on Linux
PlatformHaikuLuna
Linuxyes

Linux / Haiku 5.5: yes · Oct 17, 2026 · c27245a63875 · claude-code / 2.1.300 (Claude Code)
Recorded operation: ruby -e 'require '"'"'datadog_api_client'"'"'; c = DatadogAPIClient::Configuration.new; c.http_proxyaddr = '"'"'192.0.2.1'"'"'; c.http_proxyport = '"'"'3128'"'"'; api =…

Needs keys or browser
None seen
Setup time
1 min 31 s to install, 9 s to first use
Issue
none found in recorded check

Safety: no observations were recorded for the selected revision. Functional results do not establish a safety result.

Repair history and test corrections
Current diagnosis: unknown · resolved

Atomic destroying+revoked cleanup reservations and removed-snapshot reconciliation prevent a concurrent teardown becoming a fresh attempt failure. Known creating config=null waits for exact ownership fields; resource waits defer before measurement. Streamed disk-derived source intake and pinned JSONL inventory replace incidental source/member/stdout ceilings.

Repair record fix-6abc973b8ccd3be85f67 · current status JSON. Original run outcomes remain unchanged.

Failed run: DataDog/datadog-api-client-ruby · Oct 16, 2026 · Our test failed; no repo verdict.

Test-repair rerun: DataDog/datadog-api-client-ruby · Oct 16, 2026 · Not tested.

Current diagnosis: unknown · resolved

Source archive and original-copy/JSONL manifest now live on VM disk /var/tmp, not the187484KiB /run tmpfs. Streamed source digest/copy/inventory use actual disk capacity and original remaining attempt deadline. Expired exact-owned teardown now queues new capacity wait; no fresh-target lease failure. Shared resource wait defers before native/model calls.

Repair record fix-2810700ffa9a4158d4bc · current status JSON. Original run outcomes remain unchanged.

Failed run: DataDog/datadog-api-client-ruby · Oct 16, 2026 · Our test failed; no repo verdict.

Test-repair rerun: DataDog/datadog-api-client-ruby · Oct 16, 2026 · Not tested.

Current diagnosis: unknown · resolved

Coldpass condensed instruction text introduced newline controls rejected by the existing job schema before any model call. Job construction now normalizes instructional whitespace once, including repair context; exact original failure remains immutable. Default/repair schema regression passes.

Repair record fix-c0dd6958ec0b932fe065 · current status JSON. Original run outcomes remain unchanged.

Failed run: DataDog/datadog-api-client-ruby · Oct 16, 2026 · Our test failed; no repo verdict.

Test-repair rerun: DataDog/datadog-api-client-ruby · Oct 16, 2026 · Not tested.

Current diagnosis: unknown · resolved

The SDK explicitly passes config.http_proxyaddr/http_proxyport to HTTParty, so stock example ignores environment proxy and direct DNS cannot work in the Coldpass wall. README Configure proxy documents supported configuration. Task now permits a minimal real SDK consumer outside pinned source combining that documented configuration with the public IPRanges call; no product source patch, monkeypatch, TLS disabling or wall bypass.

Repair record fix-c84228a140e3d7342d0f · current status JSON. Original run outcomes remain unchanged.

Failed run: DataDog/datadog-api-client-ruby · Oct 16, 2026 · Our test failed; no repo verdict.

Test-repair rerun: DataDog/datadog-api-client-ruby · Oct 16, 2026 · Not tested.

Run details

Haiku 5.5

Native agent · Checked operation passed

Checked operation ruby -e 'require '"'"'datadog_api_client'"'"'; c = DatadogAPIClient::Configuration.new; c.http_proxyaddr = '"'"'192.0.2.1'"'"'; c.http_proxyport = '"'"'3128'"'"'; api = DatadogAPIClient::V1::IPRangesAPI.new(DatadogAPIClient::APIClient.new(c)); r = api.get_ip_ranges; puts "agents ipv4 prefixes: #{r.agents.prefixes_ipv4.length}"'

Agent-reported scope: Built the datadog_api_client gem per README 'Build a gem', installed it per 'Install the gem locally', and ran the README Getting Started call V1::IPRangesAPI#get_ip_ranges through the configured HTTP proxy (README 'Configure proxy'). Returned agents IPv4 prefixes (count 1, sample 3.233.144.0/20).

Run details
run
DataDog--datadog-api-client-ruby-claude-haiku-5-5-1792221457786820252
date
Oct 17, 2026
time to working
145.1s
product hosting / execution
Local command in the guest
recorded operation scope
product operation
model
claude-haiku-5-5
agent / version
claude-code / 2.1.300 (Claude Code)
platform
linux
reported cost
$0.007108
Recorded source
https://github.com/DataDog/datadog-api-client-ruby
Tool transport
mcp-assigned-vm
Test version
readme-d3659cd3f9210dfa5802d1e6a3b243d7ad5e3fc7dc58d619be334de899f21e50
revision
c27245a63875f0e5aa8d42c437f3f331b8e949ab
What the agent did

Built the datadog_api_client gem per README 'Build a gem', installed it per 'Install the gem locally', and ran the README Getting Started call V1::IPRangesAPI#get_ip_ranges through the configured HTTP proxy (README 'Configure proxy'). Returned agents IPv4 prefixes (count 1, sample 3.233.144.0/20).

apt-get install -y ruby-full build-essential (Ruby 3.2.3)
apt-get install -y git (needed by datadog_api_client.gemspec `git ls-files`)
cp -a /workspace /tmp/dd-build && git init && git commit (snapshot so the gemspec can run without touching /workspace)
gem build datadog_api_client.gemspec -o /tmp/gembuild/datadog_api_client.gem
gem install ./datadog_api_client.gem --no-document
ruby -e with DatadogAPIClient::Configuration http_proxyaddr/http_proxyport + V1::IPRangesAPI#get_ip_ranges (returncode 0)
Earlier attempts (1)

Haiku 5.5

Native agent · Not tested

Checked operation ruby -I/workspace/lib /tmp/sdk/sdk_example.rb

Agent-reported scope: Ruby SDK consumer (/tmp/sdk/sdk_example.rb) loads the pinned lib via -Ilib and calls DatadogAPIClient::V1::IPRangesAPI#get_ip_ranges against the public Datadog API; returns a populated IPRanges object (prefixes_ipv4/ipv6, modified timestamp).

Run details
run
DataDog--datadog-api-client-ruby-claude-haiku-5-5-1792199576346721300
date
Oct 16, 2026
time to working
173.5s
product hosting / execution
Local command in the guest
recorded operation scope
Public unauthenticated endpoint only; no API/app keys used. Requires outbound HTTPS to ip-ranges.datadoghq.com via the supplied proxy. Runtime gems httparty ~> 0.20 and zeitwerk ~> 2.6 installed; gem build/install and rubygems Gemfile bundle not exercised. Proxy set via documented http_proxyaddr/http_proxyport config because HTTParty did not honor HTTP_PROXY env.
model
claude-haiku-5-5
agent / version
claude-code / 2.1.300 (Claude Code)
platform
linux
reported cost
$0.005394
Recorded source
https://github.com/DataDog/datadog-api-client-ruby
Tool transport
mcp-assigned-vm
Test version
readme-d201a41f9397b39f48b24d522f8190f15e852aced1f84bea99ff6c182eb6d8a3
revision
c27245a63875f0e5aa8d42c437f3f331b8e949ab
Current diagnosis: unknown · resolved

The SDK explicitly passes config.http_proxyaddr/http_proxyport to HTTParty, so stock example ignores environment proxy and direct DNS cannot work in the Coldpass wall. README Configure proxy documents supported configuration. Task now permits a minimal real SDK consumer outside pinned source combining that documented configuration with the public IPRanges call; no product source patch, monkeypatch, TLS disabling or wall bypass.

Repair record fix-c84228a140e3d7342d0f · current status JSON. Original run outcomes remain unchanged.

Failed run: DataDog/datadog-api-client-ruby · Oct 16, 2026 · Our test failed; no repo verdict.

Test-repair rerun: DataDog/datadog-api-client-ruby · Oct 16, 2026 · Not tested.

Double-checks failed run: DataDog/datadog-api-client-ruby · Oct 16, 2026.

Fix: fix-c84228a140e3d7342d0f.

What the agent did

Ruby SDK consumer (/tmp/sdk/sdk_example.rb) loads the pinned lib via -Ilib and calls DatadogAPIClient::V1::IPRangesAPI#get_ip_ranges against the public Datadog API; returns a populated IPRanges object (prefixes_ipv4/ipv6, modified timestamp).

Requirements: Ruby 2.6+ -> apt-get install ruby-full (Ruby 3.2.3)
Installation > Include the Ruby code directly: ruby -Ilib example.rb (lib from pinned source, no build)
Installation runtime deps from datadog_api_client.gemspec: gem install httparty -v '~> 0.20'; gem install zeitwerk -v '~> 2.6'
Getting Started: IPRangesAPI.new / get_ip_ranges (run via /tmp/sdk/sdk_example.rb)
Configure proxy: http_proxyaddr=192.0.2.1, http_proxyport=3128 (from supplied HTTP_PROXY)

No product verdict. Run record.

No product verdict. Run record.

No product verdict. Run record.

No product verdict. Run record.

No product verdict. Run record.