Michael FIG

> you could extend those to test round tripping for these too. I tested round tripping. Please take another look before I merge.

What is the desired behaviour to support Resource? If there is clear guidance, I should be able to implement it. I tried changing the PrometheusSerializer to append `record.resource.attributes` to the...

> @michaelfig any plans to release your fix to npm or get this merged into esm? Doesn't seem so. I think this upstream `esm` repo has been abandoned. Also, instead...

> @michaelfig Do you still maintain the agoric fork? I get [lots of deprecation warnings](https://github.com/mk-pmb/std-esm-node-ci/issues/1) and, more importantly, [a test failure](https://github.com/mk-pmb/std-esm-node-ci/issues/2). I posted them there because the agoric repo has...

Closing, but can still be used for future reference if the memory budget is implemented in Agoric SDK.

@kumavis, thanks for this and the other reports. I'll be giving SES some love over the coming week, and will link back to each of your issues when I have...

@kumavis, does Agoric/SES#150 (now merged to master, with the repair plan additions you specified in the comments) fix these cases for you?

Would it be possible to implement this reconnect-with-no-loss feature entirely in terms of the proxy_pass service? Does it just have to munge the last_message_id before sending the X-Accel-Redirect, and if...

@AdityaSripal, for async version negotiation in `ibc-go`, will I have to patch `core/keeper/msg_server.go`'s `ChannelOpenTry` with the following? ```go // Perform application logic callback version, err := cbs.OnChanOpenTry(ctx, msg.Channel.Ordering, msg.Channel.ConnectionHops, msg.PortId,...

I added more details to an [inconclusive WebKit bug that's been open since 2016](https://bugs.webkit.org/show_bug.cgi?id=160504#c16)