-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New error: failed to resolve location #49
Comments
I have acknowledged this problem, I have created an issue HERE as it's related to the geo lookup library I use that uses openstreetmap. I don't have time now, but I will dig into this and see if I can find/fix the problem in that library dependency. |
I have figured out the problem, since we use nominatim to call out and get latitude and logitude. They have now changed their user policy for golang's http library. You must include a user-agent on the request. I will be fixing this and removing external packages which will fix this, give me some time as it might be later today or tomorrow once I can sit down and code the fix. |
No rush dude, your app is great and makes my life a little easier almost every day. Having it go down for a while was probably good to make me appreciate it more! 😁 |
Should be fixed @Weicocu with the new version I just pushed, let me know if you have any issues! |
It's working perfectly again, thank you!! |
This was working for me, but has stopped. It is giving the following error:
time="2024-05-29T16:41:30Z" level=fatal msg="failed to resolve location:invalid character '<' looking for beginning of value"
I assume this has something to do with the location I'm putting in, but even switching to the example "Seattle, WA" gives this same error.
I did not change anything between when it was working and when it stopped working.
The text was updated successfully, but these errors were encountered: