hotcell-client 0.3.1 → 0.4.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a32972e8446655b4a96f79706c3baa794419a421e3743ec6113677349e35141e
-  data.tar.gz: aa259b26182d98e1d08fc3c9545c64987446c0f80ba009896e21d3db7ff02b17
+  metadata.gz: f524eeac7887b27aef5f6c8da2c64f12156d8bf53b0182eaeee8586f3caea2fa
+  data.tar.gz: 23cc072de4878e911ee6a20a2fdd1f0272f21ffac66805b15d31534bd57a20ef
 SHA512:
-  metadata.gz: e9bc0f3f71fe67241ba74d057cf86ada551198f014c090c7e4078cd5409f9f5e52ad0dae07c2c276a4f4fc8bd49275001aa94f908a0167c68b94feb5b6c7ddcc
-  data.tar.gz: 3c1d53fd03133df6bf461309207dca60ade0a8454e8a5e590a59ae612fc9176976ad2fb39ea051aeb380cc9b428ad2e25dd64ce94e2791f7f32e3d5b52bf3a6b
+  metadata.gz: baeec88b90cd8601136b0c1260e8e0f4dc9879ded64c78d76298fde0d774ac00226221a1f4efce6071435c062089e39686e587f3b787a082a3588a25d82c707f
+  data.tar.gz: 549dd9b192b20a5a96d43f71907d06eaa0466eea01a7bb2da385ba7344caeed12490dba6aa03b02ccd8471b861229b9b77873c342d3b2ce5583f4d72e9000832

data/lib/hot_cell/client/version.rb

@@ -3,6 +3,6 @@
 module HotCell
   # A class and not a module: this file loads before hot_cell/client.rb opens the same name.
   class Client
-    VERSION = "0.3.1"
+    VERSION = "0.4.0"
   end
 end

data/lib/hot_cell/client.rb

@@ -160,6 +160,11 @@ module HotCell
       # the code filed every fsize kill as transient. `permanent` is the Failure's own answer, so no
       # subscriber re-derives it.
       #
+      # `stderr` is the diagnosis of a crash — `libgomp: Thread creation failed` — and the event is the only
+      # place a subscriber can log it: the exception's message carries it too, but only a retry logs that,
+      # and a discarded failure loses it. It is text a tool wrote while processing a hostile file, bounded
+      # by `Failure.sanitize` on the way in, and a subscriber should write it to a log field and nowhere else.
+      #
       # A subscriber's own duration minus perform_ms is transport plus queueing, and those want separate
       # metrics: a rising perform_ms means the work got more expensive, and a rising difference means the
       # cell is saturated.
@@ -171,6 +176,7 @@ module HotCell
         event[:code] = failure&.code
         event[:cause] = failure&.cause
         event[:signal] = failure&.signal
+        event[:stderr] = failure&.stderr
         event[:permanent] = failure&.permanent?
         event[:bytes_in] = byte_count(inputs)
         event[:bytes_out] = byte_count(outputs)

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: hotcell-client
 version: !ruby/object:Gem::Version
-  version: 0.3.1
+  version: 0.4.0
 platform: ruby
 authors:
 - Mike Dalessio
@@ -15,14 +15,14 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.3.1
+        version: 0.4.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.3.1
+        version: 0.4.0
 - !ruby/object:Gem::Dependency
   name: activesupport
   requirement: !ruby/object:Gem::Requirement
@@ -67,8 +67,8 @@ licenses:
 - MIT
 metadata:
   homepage_uri: https://github.com/basecamp/hotcell
-  source_code_uri: https://github.com/basecamp/hotcell/tree/v0.3.1/hotcell-client
-  changelog_uri: https://github.com/basecamp/hotcell/blob/v0.3.1/CHANGELOG.md
+  source_code_uri: https://github.com/basecamp/hotcell/tree/v0.4.0/hotcell-client
+  changelog_uri: https://github.com/basecamp/hotcell/blob/v0.4.0/CHANGELOG.md
   bug_tracker_uri: https://github.com/basecamp/hotcell/issues
   rubygems_mfa_required: 'true'
 rdoc_options: []