gourlaysama / girouette Goto Github PK

The API at OpenWeather supports localized city names and weather descriptions, so we should expose that.

• add a language config item
• show localized city names and weather description
• rework the caching scheme to take language into account
• look into localizing ASCII icons (maybe?)

The config currently only allows 3 ways of describing a color:

• a color name as a string,
• a single number in 0-255,
• an array of RGB [12, 42, 56]

It would be much easier to specify an RGB color as a string like "#aa44ff" instead.

chrono doesn't appear to be maintained anymore.

It depends on a very old version of time which is affected by RUSTSEC-2020-0071 (#25), and itself is affected by the same thing (CVE-2020-26235: chronotope/chrono#602).

The API provides snowfall just like it does rainfall, so we should have a segment for that too.

Openweather provides a minutely forecast for the next hour, though only for precipitation data.

Add a segment to display precipitation data in a way that doesn't take too much space:

• collapse consecutive times into a single element when the precipitation doesn't change?
• collapse the whole segment into nothing when 0 (like the rain segment)?

Openweather provides alerts from a lot of national weather warning systems.

Add a segment that shows:

• alert name
• optional description
• optional sender (agency, ...)
• start/end datetime
• maybe an icon based on the tag (type of severe weather)?

The API always provides the current cloudiness in %, but we are currently doing nothing with it.

Metric units are currently hardcoded. Girouette should allow using imperial units (Fahrenheit instead of Celsius, miles/h instead of km/h).

Potential segfault in the time crate

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

The affected functions from time 0.2.7 through 0.2.22 are:

• time::UtcOffset::local_offset_at
• time::UtcOffset::try_local_offset_at
• time::UtcOffset::current_local_offset
• time::UtcOffset::try_current_local_offset
• time::OffsetDateTime::now_local
• time::OffsetDateTime::try_now_local

The affected functions in time 0.1 (all versions) are:

• at
• at_utc

Non-Unix targets (including Windows and wasm) are unaffected.

Patches

Pending a proper fix, the internal method that determines the local offset has been modified to always return None on the affected operating systems. This has the effect of returning an Err on the try_* methods and UTC on the non-try_* methods.

Users and library authors with time in their dependency tree should perform cargo update, which will pull in the updated, unaffected code.

Users of time 0.1 do not have a patch and should upgrade to an unaffected version: time 0.2.23 or greater or the 0.3. series.

Workarounds

No workarounds are known.

References

time-rs/time#293

See advisory page for additional details.

OpenWeather has an Air Pollution API with an Air Quality Index and concentrations of various gasses when available. Having at least the index visible would be useful.

This would require a second API call with the lat/lon coordinates from the first.

This requires using the new API. See One Call API.

It provides:

• Current weather
• Minute + Hourly + Daily forcast
• Weather alerts
• Weather of last 5 days

It is more rate-limited with the free API (1000 calls/day), so it would require caching to be active.