Alex Robbin

@icelynjennings if you use Sidekiq through Active Job, then it is sort of fixed. *Most* logs are correlated through Active Job integration. If, however, you're using Sidekiq "natively", then unfortunately...

@icelynjennings it'd be great if the functionality could be expanded, but I don't think the solution in https://github.com/mperham/sidekiq/commit/90535ab104b6540104af548d15baacd1291ffb5f actually does anything to make that easier. It broadcasts any `Rails.logger` output...

Yeah I'm honestly not sure what the ideal option is here. The workaround we have makes sense in an entirely Webpacker-world, but since the gem needs to support both Webpacker...

@Noip1 I am not a maintainer of this gem, and contributed #70 more than 7 years ago, so I don't know what my review will add, but I have left...

Keeping in mind that I am not a maintainer of this gem, and contributed #70 more than 7 years ago, I think what's bitten this gem from my earlier change...

@bolandrm would it be possible to release a new version to get the fix from #158 into our hands? We have started running into this issue as well, and are...

@allmarkedup thanks for the thoughtful response! My only follow-up here is to elaborate a bit on the use case I have for Lookbook. While it's definitely possible the usage may...

@oreoshake I thought it worth mentioning that I just opened rails/rails#46859, which allows modification of Rails' global CSP. It is a much simpler implementation than what you describe in your...

@allmarkedup that is great to hear! I've just taken a (quick) look at the 2.0 beta on my application, and things are looking great. I also took a brief look...

OK that's helpful @pakrym-stripe, thanks! Should I leave this issue open while that design process plays out?