# The Git Hang and the Admin/Mod user Accs Oops Error Page Error

**URL:** <https://meta.discourse.org/t/the-git-hang-and-the-admin-mod-user-accs-oops-error-page-error/413475>\
**Category:** Self-hosting\
**Tags:** login, bug\
**Created:** [September 28, 2026, 1:24pm UTC](https://meta.discourse.org/t/the-git-hang-and-the-admin-mod-user-accs-oops-error-page-error/413475 "2026-09-28T13:24:02Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)\
**Post date:** [October 1, 2026, 7:38pm UTC](https://meta.discourse.org/t/the-git-hang-and-the-admin-mod-user-accs-oops-error-page-error/413475/13 "2026-10-01T19:38:36Z")

</div>

ok sorry turns out the llm gave me outdated info.

here are some commands I have tried and used.

tabulate the admin users and the value of their setting for upcoming changes:

```plaintext
# docker exec -it app rails r 'User.where(admin: true).each { |u| puts "#{u.id} #{u.username} #{u.user_option.enable_upcoming_change_available_notifications}" }'
-1 system true
-2 discobot true
1 AdminTeam false

```

for a given id - in my case 1 - flip the setting for that id:

```plaintext
# docker exec -it app rails r 'x=1;User.find(x).user_option.update!(enable_upcoming_change_available_notifications: !User.find(x).user_option.enable_upcoming_change_available_notifications)'

```

I rather prefer the one-liner from the root shell, of course one could enter docker and enter rails and then perform actions if one preferred.

---

_[View the full topic](https://meta.discourse.org/t/the-git-hang-and-the-admin-mod-user-accs-oops-error-page-error/413475)._