v2 couple of Bugs & Feature Requests
See original GitHub issueTodo
- USCS support
- lowest and highest temperature for each day
- v2 help with detailed explanation
- v2 png timestamp bug
- plotted diagram: the bug with vertical line at the beginning
- bug: strange temperature outbreaks
Details
I like v2 a lot, thanks for it! I have some feature requests, also i found some bugs.
Bugs:
-
The current time in the .png view contains a Placeholder
%{{NOW(Europe/Berlin)}}
instead of the time, see attachment -
On Ubuntu 18.04, in the default terminal, some Icons (current weather and Wind direction) are too close to the Text, see screenshot:
-
The plotted diagram seems to always start with a vertical line?
-
Sometimes, there are outbreaks, look at the pictures at 05 May, 6 o’clock
Feature Requests:
- Have a Wiki or some help, that explains the output. So far I’ve found these Explanations: a) Blue shades b) White lines at the bottom c) the row with Numbers seems to be the wind speed, the row before that the wind direction?
- In the plotted diagram its hard to guess what temperature it will be, lets say this afternoon. Could we have some Numbers in the Diagram? Or maybe add more numbers tho the axis on the left? I’ve made a Mock-Up for the first one.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:13 (7 by maintainers)
Top Results From Across the Web
Bugs and feature requests/ko - Fedora Project Wiki
A common practice is to file a bug first, then e-mail the list with a link to the bug report, asking for further...
Read more >Why Bug Reports and Feature Requests Don't Overwhelm Us ...
We were getting crushed under the weight of incoming tasks. Here's how we developed a simple system to manage feature requests and bug...
Read more >[bugs][feature request] A few bugs and feature ... - GitHub
Hello to everyone who is supporting and developing phpIPAM. I'm very glad for this project active developing. And I'm hoping there is a...
Read more >How to Report Bugs, Improvements, New Feature Requests ...
Clear and structured bug, improvement, and new feature request reports are always helpful for validating and fixing issues. In a few cases, ...
Read more >That's Not a Bug, It's a Feature Request - Coding Horror
There's no difference between a bug and a feature request from the user's perspective. If you want to do something with an application...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@mckaymatt I will add it, but you are right; currently USCS is not supported
Thank you for your comments, and for the interest to our gemütlichen service 😃 First of all, it is not yet finished, it is just a beta, or pre-beta, that we are playing with; it was published just to gather some feed back and criticism. So thank you for it.
The problem with the placeholder is known; it will be fixed soon. The problem here, is that because of the high load that the service has, it was partially rewritten from Python, in Go, and the PNG rendering part is still in Python. The go service is acting like a HTTP/HTTPS-frontend + it makes some caching where possible. Before PNG-rendering will be rewritten in Go, the best solution probably could be to switch the caching of the v2 PNGs off (whould should have no impact on the service).
Yes, I believe, spaces here would be a good solution (the problem is related to #433; @hern42 what do you think about it?)
It is a bug. It must be fixed.
It seems to be a bug too.
FR1. Yes, I agree, I think this information should be added to /:help and to the README file.
FR2. Not sure about this one. My idea was to mark the max and min values for each day, like it is done for rate.sx (check
curl rate.sx/btc
to see how it looks like).Other visual features, that are still not implemented (JFYI):