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
I haven't dug into the stack trace or the package-registry project/container much, but I just got this panic after rebuilding assets which resulted in me having to re-spin up my docker environment again (which, with kibana, can take awhile):
It appears to be trying to unlock a mutex that's not currently locked. While we should fix the bug in the underlying program, for now we should also set the docker-compose manifest to have restart: always for at least this container.
The text was updated successfully, but these errors were encountered:
I suspect this is the root cause (and the fix) for this problem: radovskyb/watcher#96 . Unfortunately it's not maintained anymore, I'm afraid we need to fork it.
I appears to be only in the development mode (in config: dev_mode: true) and should be fixed on the package-registry side.
I haven't dug into the stack trace or the package-registry project/container much, but I just got this panic after rebuilding assets which resulted in me having to re-spin up my docker environment again (which, with kibana, can take awhile):
It appears to be trying to unlock a mutex that's not currently locked. While we should fix the bug in the underlying program, for now we should also set the docker-compose manifest to have
restart: always
for at least this container.The text was updated successfully, but these errors were encountered: