dracula
Weather feature is broken
The weather feature is not fully operation for a long time. It works sometimes, sometimes does not. Today, it completely broke. It does not recognizes cities or coordinates anymore. Also it just initializes on its own. The statements related to weather are commented out, but still the popup or error shows up.
The weather feature is not fully operation for a long time. It works sometimes, sometimes does not. Today, it completely broke. It does not recognizes cities or coordinates anymore. Also it just initializes on its own. The statements related to weather are commented out, but still the popup or error shows up.
The difficulty seems to be coming from the weather API wttr.in. I had the same message but fiddling with the fixed location, sourcing tmux, opening closing sessions it seemed to start working again even though I didn't really change anything.
Scripts just need to be able to handle the new error gracefully and return the unavailable message.
Edit: And by the new "error" I mean what I'm guessing is a 200 response now rather than 4XX or 5XX
Edit2: Id love to understand how the location payload gets sent to wttr.in because I can't figure out where that variable is getting populated from, but I assume its geolocation of the user's IP?
@agentduckman I thought so too about wttr.in. But i check for API requests for my location, both absolute and coordinates, and the API works fine. I don't know any other 3rd party apps to check it with, but manual request works just fine.
After following another answer, the "Unknown location..." alert is gone, but it still shows weather unavailable, even when there are no lines for weather in tmux.conf. And I am afraid to add it again as it might break again.
I'm also having this issue. I can format the curl to wttr.in like the script does and I don't have any issues, but the section in tmux still reads Weather Unavailable.
Also getting this, both in tmux and if I go to the built out URL directly in the browser. Toying with it locally to see if it's resolvable easily, but also just adding an anecdote that it's not a one off.
Seems relevant: https://github.com/chubin/wttr.in/issues/638#issuecomment-937039061