Micah Geisel

@jeffvincent It sounds like maybe this situation could be addressed in the README? What do you think?

@jeffvincent Yes, please do!

@parndt Hmm, my first thought is curiosity about the motivation behind the PR. @sampatbadhe did you find yourself in a situation where `lft` and `rgt` were outside of the max...

Hi @adicco, I completely agree that scroll position should be preserved! We're on the cusp of releasing v0.5.0, and the next development cycle is going to focus specifically on preserving...

I also ran into this today. Thankful for this thread for helping figure out what the heck was happening! Agree that it would be nice to have this work by...

We've been hitting htis for a while too, and I finally dug into it. It looks like its likely a race condition with the use of a concurrent map. Looks...

This happened to me today with Rails 7.1.3 and ANS 3.6.0. I have worked around the issue by switching the order in the model: ```ruby class Record < ActiveRecord::Base #...

Digging deeper, it appears that the various calls to `AR::Base#reload` in `awesome_nested_set/model.rb` are to blame. Commenting them out resolves the issue. It looks like `#reload` resets some ActiveStorage hooks?

Turns out this is expected behavior?? ```ruby # lib/active_storage/attached/model.rb module ActiveStorage::Attached::Model def reload(*) # :nodoc: super.tap { @attachment_changes = nil } end end ``` Also perhaps related: https://github.com/rails/rails/issues/40630 Do we...

I have successfully worked around this issue by undoing the attachment reset behavior in ActiveStorage: ```ruby class Record < ActiveRecord::Base has_one_attached :attachment # must come before acts_as_nested_set acts_as_nested_set # undo...