The Doctor
The Doctor
Let's try this again. Not working. I'm digging into it right now by going through the code in searxng/searx/engines/mysql_server.py and running through the query process. I get the same error...
I dumped my defaults (can post them if you like) and compared them to my research code. They appear to line up as expected; stuff that has no default is...
@return42 Nope, that's sorted. Thank you very much. It might be a good idea to have those config options in the searxng/searx/settings.yml file by default but that's just a QoL...
Yep, that did it.
@panique Or we're just using it every day and don't see a need to mention it. It's just another tool in the toolbox, like `awk` or `vi`.
Same. I plugged Manticore into my back-end database and interfaced it with SearxNG to get a decently usable search of my collection. It might be a limitation of MySQL's/MariaDB's full...
I just ran into this, too. I had to create some directories and copy over those Javascript files manually to make it work: ``` cd env/lib/python2.7/site-packages/realms/static/ mkdir -p wiki/js/collaboration/ cp...
I was able to recreate all of these errors. Arch Linux (20210819). Python v3.9.6 UPnPy v1.1.8 installed with Pip.
> Some additions, even if I use a version 2 years ago, this problem still occurs. But I found a solution, this problem will not occur if I don't connect...
I think the only solution any of us have really found was to prevent the database connections from dropping, because that seems to cause it. That's easier said than done...