Andrew Cholakian

@fearful-symmetry with the V2 protocol does the `output.elasticsearch` section still get written? https://github.com/elastic/beats/issues/32163 , which was merged recently, depends on it, reading back from ES to get the last known...

You can see where we set this up, and how, here: https://github.com/elastic/beats/blob/main/heartbeat/beater/heartbeat.go#L72

@fearful-symmetry I'm realizing it's only been tested on the beat, thanks a bunch for noticing that, I've opened https://github.com/elastic/beats/issues/33244 to track.

That's a great point @wasserman , re: combining those `httpjson` options into heartbeat. That said, it may be better at some point to just have first class support for API...

This was fixed in a previous release with #30632 and documentation just merged in #33466

+1 as well

@rinogo I think you may be confused between the versioning of https://github.com/elastic/synthetics which uses `playwright` and this repo which is for the playwright project itself. We have resolved our issue...

+1 on this, the cljs I'm running is straight from an example: (ns hello) (defn ^:export greet [n](str "Hello " n))

Oddly enough this doesn't seem to prevent execution _shrugs_ (for the record I'm on jruby as well).

We agree that this is a problem! What is your preferred solution here. First, if there are outputs that fail without blocking the whole pipeline, that is a bug and...