Replies: 1 comment 1 reply
-
|
Hi there 👋, Thanks for reaching out. This looks like an issue with your cache setup. You need to have a persistent cache setup, like Redis. If you haven't, please do so. If you have, please share your cache config here and I am happy to take a look. Best Johannes |
Beta Was this translation helpful? Give feedback.
-
|
Hi Johannes, Thanks for your reply. It seems to work now that I setup redis. I thought the LocMemCache was a persistent cache and that I should be good. But now that I think about it, gunicorn, that we use in production, spins off multiple worker processes, and I guess that cache is local to those worker processes. Perhaps it might be a good idea to update the documentation with a bit of extra warning? I know this all makes sense to seasoned devs, but for newbies like me... ;) |
Beta Was this translation helpful? Give feedback.
-
Bug Description
Hi!
I get intermittent 'field_id not found' errors. On my local machine, doing a manage.py runserver, everything works fine. However, in my docker container it only works once every few requests.
If I start typing in my autocomplete field, I see ajax requests going to /select2/fields/auto.json?term=ange&field_id=IjVkOTJjOTE.. for example. If I just start typing something that is in the list, then most of the time it'll say 'the results could not be loaded', but every now and then upon typing, it'll output a response.
If I open up my browser's network inspect tool, I see most requests return a 404 'field_id not found', and some will return a 200 with the json. But all the requests are identical, except for the search term.
I don't understand why it's throwing these errors!
running python 3.11 and:
Django==4.2.7
django-select2==8.1.2
gunicorn==21.2.0
These exact versions are the same in the docker image.
On my dev machine I run manage.py runserver. In the docker image I have a simple nginx config with gunicorn running. A single container, no balancing, no caching components, no caching configuration in django (so the default LocMemCache is used).
See this nginx output for example, you see a lot of 404's, with a few 200's in between:
p.s. I created a discussion as well, but that did not get any answers: #251
Steps to Reproduce
type stuff into the autocomplete field
Expected Behavior
I expect every request to /select2/fields/auto.json return a 200 instead of a 404.
Beta Was this translation helpful? Give feedback.
All reactions