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
Expected behavior (A description of what you expected to happen) :
When you call /status it shoudn't have any errors by default. Currently we workaround this with the the URL
/status/?skip=watchman.checks.storage but it would be nice it it worked.
Describe the bug (Tell us what happens instead of the expected behavior) :
There's a stacktrace in the storage section and it returns an error. It would be nice to fix this so we don't have to workaround it.
"storage": {
"ok": false,
"error": "Could not find config for 'default' in settings.STORAGES.",
"stacktrace": "Traceback (most recent call last):\n File \"/usr/local/lib/python3.10/site-packages/django/core/files/storage/handler.py\", line 35, in __getitem__\n return self._storages[alias]\nKeyError:
I think this might be fixed by just configuring a placeholder InMemoryStorage like. The better if the watchman library checked to see if this was configured or handled the exception and just didn't print anything for storage. But this should work for us
Expected behavior (A description of what you expected to happen) :
When you call
/status
it shoudn't have any errors by default. Currently we workaround this with the the URL/status/?skip=watchman.checks.storage
but it would be nice it it worked.Describe the bug (Tell us what happens instead of the expected behavior) :
There's a stacktrace in the storage section and it returns an error. It would be nice to fix this so we don't have to workaround it.
I think this might be fixed by just configuring a placeholder InMemoryStorage like. The better if the watchman library checked to see if this was configured or handled the exception and just didn't print anything for storage. But this should work for us
Steps to Reproduce :
/status
and/status/bare_status
. You should get a 200 response and no errors.The text was updated successfully, but these errors were encountered: