Robert Pankowecki

Point 1: Circular sync handlers is rarely a good idea imho so I am leaning towards _won't fix_.

Point2: I was thinking about more optimistic approach. Current code: ```ruby def store(stream_name = @loaded_from_stream_name, event_store: default_event_store) event_store.publish_events(unpublished_events, stream_name: stream_name, expected_version: version) @version += unpublished_events.size @unpublished_events = nil end ```...

My workaround for serialized list of integers: ```ruby class Package < ApplicationRecord serialize :ids ransacker :ids_raw, type: :string do Arel.sql('packages.ids') end ``` ```ruby Ransack.configure do |config| config.add_predicate 'yaml_array_cont', arel_predicate: 'matches',...

@pmq20 Would you accept a PR changing to build on older Ubuntu? I commented on https://github.com/pmq20/ruby-packer/commit/08059fc198308531cbbac62594972e21dda11fe3 what could have failed there potentially.

@weshatheleopard that might also be a good solution. I could test it for you if you don't have Windows.

I believe it is important to comply with the specs here. From the perspective of the client it should be transparent that a request is going through a gateway. I...

This is currently working when using signals for running application. However the additional usecase that I have in mind is that someone might be running a handler in separate thread....

I think we do not need a reproducible benchmark env. Just something that can be executed for every release in current env. I hope it is clear. It would be...

Compared to what ? I have no idea what you are talking about. Sorry :( If I execute benchmark of three releases on my local computer then those values can...

@marcotc I think you meant `Net::SMTP` in the previous message.