arch1v1st

Experiencing the same issue here; also using Leaflet.markercluster and the latest 1.0-beta3 of Leaflet. I experimented with changing the moveToLocation option for Leaflet.search between setView/panTo/flyTo to no avail - this...

After rolling back to the original Leaflet Search example code and testing, this error did not occur. I managed to squash the issue with my custom map code by including...

@louislam - I appreciate your time at looking at this further so quickly. I also found it strange that one of the worlds largest DNS providers (CloudFlare) had these sort...

@chakflying - Running only a handful of DNS monitors overall, and all have been reconfigured to use 8.8.8.8 Started to notice the resolution problems with only 2 at the time...

I had hoped @rezzorix suggestion would work, but it seems that the mxtoolbox page uses JavaScript to render the blacklist DIV hence a keyword check can't see the values. Does...

@Computroniks - thanks! I came across that github project too from my research after posting this as well. @rezzorix - Appreciated, and I also came across multirbl.valli.org along the way...

Had the same problem/error, though after following the standard Ubuntu 16.04 instructions (not using docker) the website directory did exist in '/srv/nominatim/Nominatim/build/website' which was properly mapped in my apache conf...

Running Windows 10, Docker Destop with WSL2. My api-cuda-guff container starts up as expected, but then gets stuck in a loop of throwing these 'code 139's. ``` llama-gpt-llama-gpt-ui-1 | [INFO...

Got it working with all code models. In /cuda/gguf.Dockerfile, came to find this line was causing my startup issues with any llama code model while using CUDA by forcing v0.1.80...

@jimlee - it happens automatically upon starting the docker container and totally depends on your internet download speeds. See this for a sense of the size: https://github.com/getumbrel/llama-gpt#supported-models On Windows, I...