You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 7, 2024. It is now read-only.
First, if you use a girder_worker task with .delay, it is using the Celery app loaded from the girder_worker config files NOT the settings in the girder_worker.girder_plugin values. The app is instantiated by girder_worker.app not girder_worker.girder_plugin.celery.
Second, when the settings are changed in Girder, the event handler in girder_worker/girder_plugin/event_handlers.py will reset a local _celeryapp value, but I don't think this will reset it in the girder_worker.girder_plugin.celery module.
@kotfic Either I've misconfigured things, or girder_worker on girder with a non-local rabbitmq instance requires the worker.*.cfg to be configured on both the worker and girder machines.
@manthey Sorry i'm having a little trouble refreshing on the origin of this issue. Is it possible to link to the code where you're seeing the unexpected behavior?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
No description provided.
The text was updated successfully, but these errors were encountered: