Curators need a gateway restart after a chat model is configured.
When the gateway starts with no default model alias, it disables curators and never re-checks. Setting the alias in Settings > Models does not bring them back until the gateway restarts, which breaks the rule that settings apply end to end without a server login. The Curators page now shows the reason as an apply failure.
Done when: setting the default model alias enables curators in the running gateway, and the Curators apply status turns current without a restart.
Curators need a gateway restart after a chat model is configured.
When the gateway starts with no default model alias, it disables curators and never re-checks. Setting the alias in Settings > Models does not bring them back until the gateway restarts, which breaks the rule that settings apply end to end without a server login. The Curators page now shows the reason as an apply failure.
Done when: setting the default model alias enables curators in the running gateway, and the Curators apply status turns current without a restart.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Curators need a gateway restart after a chat model is configured.
When the gateway starts with no default model alias, it disables curators and never re-checks. Setting the alias in Settings > Models does not bring them back until the gateway restarts, which breaks the rule that settings apply end to end without a server login. The Curators page now shows the reason as an apply failure.
Done when: setting the default model alias enables curators in the running gateway, and the Curators apply status turns current without a restart.
Fixed in
c7fabbee2, on main and deployed.