Metric graphs are not properly autoscaled according to data so data is often rendered outside of visible area.
Metric graphs are not properly autoscaled according to data so data is often rendered outside of visible area.
<img width="1100" height="444" alt="Image" src="https://github.com/user-attachments/assets/da7ad6b4-f482-409f-ba5a-b7d9a4af3880" />
<img width="706" height="456" alt="Image" src="https://github.com/user-attachments/assets/689dd379-02df-4734-a62a-131e33a4e137" />
<!-- github-sync-id:4223318182 -->
Safari 26.3.1 on MacOS Tahoe on a 2019 MacPro (Intel silicon)
Chrome 147.0.7727.138 (Official Build) (x86_64) on a 2019 MacPro (Intel silicon)
Safari 26.3.1 on MacOS Tahoe on a 2021 MacBook Pro M1 (Apple silicon)
I am running version 1.0.5.
I observe the same thing with
- Safari 26.3.1 on MacOS Tahoe on a 2019 MacPro (Intel silicon)
- Chrome 147.0.7727.138 (Official Build) (x86_64) on a 2019 MacPro (Intel silicon)
- Safari 26.3.1 on MacOS Tahoe on a 2021 MacBook Pro M1 (Apple silicon)
I am running version 1.0.5.
<img width="1676" height="614" alt="Image" src="https://github.com/user-attachments/assets/6f963af3-f561-4670-9042-8dc5fe12a78d" />
<!-- github-comment-id:4381989179 -->
FIrst of all, I really want to thank you for your excellent work. You've handled so many details well. The installer / upgrader makes this a dream to set up.
Before filing this bug, I ran an update, but it did not change the version (I was expecting 1.0.9 but it remained on 1.0.5). I am trying to figure out what I did wrong.
FIrst of all, I really want to thank you for your excellent work. You've handled so many details well. The installer / upgrader makes this a dream to set up.
Before filing this bug, I ran an update, but it did not change the version (I was expecting 1.0.9 but it remained on 1.0.5). I am trying to figure out what I did wrong.
<!-- github-comment-id:4382038751 -->
The upgrade script will:
Pull the latest code from the main branch
Update all application files
Upgrade Python dependencies if needed
Restart the service automatically
Preserve your existing configuration
My experience is that the upgrade script from the 1.0.5 installation does not pull the latest code. I did the pull manually and then ran sudo ./manage.sh -- this time, it installed 1.0.10.dev3 instead of re-installing 1.0.5
The new UI is terrific. Scaling seems to be working properly now (with limited testing on my part).
Upgrade instructions say
```
The upgrade script will:
Pull the latest code from the main branch
Update all application files
Upgrade Python dependencies if needed
Restart the service automatically
Preserve your existing configuration
```
My experience is that the upgrade script from the 1.0.5 installation does not pull the latest code. I did the pull manually and then ran `sudo ./manage.sh` -- this time, it installed 1.0.10.dev3 instead of re-installing 1.0.5
The new UI is terrific. Scaling seems to be working properly now (with limited testing on my part).
<!-- github-comment-id:4382113724 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Metric graphs are not properly autoscaled according to data so data is often rendered outside of visible area.
Hi @a1j what browser are you using? im not seeing this.
I observe the same thing with
I am running version 1.0.5.
do you mind updating? there have been many fixes since then.
Chrome on linux (debian).
FIrst of all, I really want to thank you for your excellent work. You've handled so many details well. The installer / upgrader makes this a dream to set up.
Before filing this bug, I ran an update, but it did not change the version (I was expecting 1.0.9 but it remained on 1.0.5). I am trying to figure out what I did wrong.
Upgrade instructions say
My experience is that the upgrade script from the 1.0.5 installation does not pull the latest code. I did the pull manually and then ran
sudo ./manage.sh-- this time, it installed 1.0.10.dev3 instead of re-installing 1.0.5The new UI is terrific. Scaling seems to be working properly now (with limited testing on my part).