Owen Stephens

Thanks @rocket-turtle. My main concern is the "only sometimes works" aspect of this issue, rather than particularly allowing plain boolean attribute references at the top-level of a `where.has` block. That...

Similarly to this comment https://github.com/CanCanCommunity/cancancan/pull/663#issuecomment-1141121182 adding this before the test "fixes" the test: ```ruby CanCan::RulesCompressor.class_eval do def compress(array) # Don't compress... array end end ```

This seems like intentional behaviour according to this suggested test: https://github.com/CanCanCommunity/cancancan/pull/689#discussion_r638352513 My expectation also seems to be somewhat at odds with the expectation set out in another issue: https://github.com/CanCanCommunity/cancancan/issues/771 My...

Hi @gregnavis - just following up on this again - any further progress since your last comment?

I agree that the existing implementation isn't particularly robust (see #386 for example), but wouldn't this also unsubscribe unrelated listeners, for example the one powering a gem such as https://github.com/steventen/sql_tracker

@davetron5000 what output do you see with Rails 7.0.8? I suspect that the "Rendering" lines are the same cause as #385 but I'm not sure if the other lines are...

For me it inverts between `18446744073709551615` and `18446744073709551616` (i.e. `2**64 - 1` and `2**64`), which makes sense given the linked PR description https://github.com/ruby/bigdecimal/pull/178 "Implement special conversions for 64-bit integers" So...

After further investigation, I can see the (likely) cause - [`1.6.7-x86_64-linux`](https://rubygems.org/gems/sqlite3/versions/1.6.7-x86_64-linux) has `REQUIRED RUBY VERSION: >= 2.7, < 3.3.DEV` so is incompatible with Ruby 3.3. It looks like the first...

> Maybe we could print this debug output by default. Thanks @deivid-rodriguez - this sounds sensible. I'm not sure about debug output in general, but certainly some warning that the...

Oops, thanks for the ping @lfittl - I think my eyes read the gemspec requirement as already being `>= 3.25.3` rather than `>= 3.22.3` 🤦