David Wessman

https://discuss.rubyonrails.org/t/cve-2022-32224-possible-rce-escalation-bug-with-serialized-columns-in-active-record/81017 It is mentioned that you can allow specific classes with: ```ruby config.active_record.yaml_column_permitted_classes = [Symbol, Date, Time] ``` Does that help?

I have an app with both `Symbol` and `HashWithIndifferentAccess`, have anyone solved how do limit the dangerous behaviour without destroying old data?

I am a bit worried about what data is accepted inside `ActiveSupport::HashWithIndifferentAccess`.

I am experiencing the same bug. For me it will only happen when I do `create_index!(force: true)` on an index that does not exist. - `create_index!` - works - `create_index!(force:...

I tried running the specs locally, in the test for the method that fails I get: ```ruby client.transport => # # #

> Any news on this? I'm still having this issue with `elasticsearch-rails` `7.2.1`. > > > > In the meantime, I was able to workaround it with this: > >...

I might take a look at this tomorrow, really looking forward to metrics 😍

Should we use the existing live-poll-functionality, hard refresh or something custom? If we are using the live-poll, we need to - remove chart - replace content - initialize new chart...

Will look into reworking the table to fit with that vision.

@mperham What branch should I base my changes on now until version 7 is released?