Glenn Matthews
Glenn Matthews
Also an issue: the rendered confirmation page is *not* paginated - so even if the pk_list isn't the issue, Django will probably tip over trying to render a non-paginated table...
For both "edit all" and "delete all" cases, instead of a secondary page, we could possibly use modals - a simple "confirmation" modal for "delete all", and a modal containing...
Alternately, instead of a modal, just skip rendering the table of related objects in the confirmation page in the "select all" case, and just list the filters and total count...
Related: #3441.
I don't think we want to remove this functionality - in fact IIRC we specifically restored it via #4224. If I'm reading the report correctly, the error specifically happens if...
Reopening as the initial UI work for this model is not yet completed.
Probably solvable at the job level by having the SSoT job call "ensure_git_repository()` or various lower-level code?
Ideas to pursue: - Profiling suggests that change logging overhead appears to be a significant contributor, perhaps with DRF as a key factor of that in turn - PRs like...
#5329 appears unnecessary to backport to ltm-1.6 because there `enqueue_job_hooks` is [using](https://github.com/nautobot/nautobot/blob/ltm-1.6/nautobot/extras/jobs.py#L1349-L1352) `ChangeLoggedModelsQuery().list_subclasses()`, which doesn't involve a database hit in the first place. I did an experimental cherry-pick of this...
After fixing #5782 we are so far unable to reproduce this issue locally either with Git or App Jobs. Closing this for now, but please let us know if you...