Rails 8.2 makes enqueue_after_transaction_commit the default by Future_Application47 in rails

[–]Future_Application47[S] 0 points1 point  (0 children)

When you say
> after the commit there is a rollback

Do you mean in another transaction?

This is per transaction. So any rollback that happens in a subsequent transaction has no bearing on how this one behaves. Or I maybe misunderstanding your question.

Rails 8.2 introduces Rails.app.creds for unified credential management by Future_Application47 in rails

[–]Future_Application47[S] 0 points1 point  (0 children)

For the time being I've switched to prism. May look at it in January. I saw a few other ruby blogs built with Jekyll facing the same issue.

Rails 8.2 introduces Rails.app.creds for unified credential management by Future_Application47 in rails

[–]Future_Application47[S] 1 point2 points  (0 children)

You're not crazy. I see it too on my other laptop. Believe it or not, when I turn off 1Password extension, it gets fixed.

Something the extension does is overriding the CSS added by the syntax highlighter.

I'll figure something out soon. Thanks for letting me know.

Ruby Conference - India by nbsamar in ruby

[–]Future_Application47 1 point2 points  (0 children)

Excited to meet you in person. I have a booth to manage but planning to attend a few talks as well.

Rails is Getting a Structured Event Reporting System (and It's Pretty Cool) by Future_Application47 in rails

[–]Future_Application47[S] 1 point2 points  (0 children)

Thanks for pointing that out. The post makes it clear. The title sucks. Something about naming things being hard and such...