Closed akama-aka closed 6 months ago
@akama-aka could you perhaps add a video of the issue? I wasn't able to reproduce it, I'm not running the exact same setup but an Alma 9.0 running on Windows WSL2
https://github.com/netdata/netdata-cloud/assets/82235632/df72e779-1a74-4b59-9edf-8a0ae6a11867
Linux hugo-pc 5.15.133.1-microsoft-standard-WSL2 #1 SMP Thu Oct 5 21:02:42 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
/etc/almalinux-release:AlmaLinux release 9.0 (Emerald Puma)
/etc/os-release:NAME="AlmaLinux"
/etc/os-release:VERSION="9.0 (Emerald Puma)"
/etc/os-release:ID="almalinux"
/etc/os-release:ID_LIKE="rhel centos fedora"
/etc/os-release:VERSION_ID="9.0"
/etc/os-release:PLATFORM_ID="platform:el9"
/etc/os-release:PRETTY_NAME="AlmaLinux 9.0 (Emerald Puma)"
/etc/os-release:ANSI_COLOR="0;34"
/etc/os-release:LOGO="fedora-logo-icon"
/etc/os-release:CPE_NAME="cpe:/o:almalinux:almalinux:9::baseos"
/etc/os-release:
/etc/os-release:ALMALINUX_MANTISBT_PROJECT="AlmaLinux-9"
/etc/os-release:ALMALINUX_MANTISBT_PROJECT_VERSION="9.0"
/etc/os-release:REDHAT_SUPPORT_PRODUCT="AlmaLinux"
/etc/os-release:REDHAT_SUPPORT_PRODUCT_VERSION="9.0"
/etc/redhat-release:AlmaLinux release 9.0 (Emerald Puma)
/etc/system-release:AlmaLinux release 9.0 (Emerald Puma)
@akama-aka could you perhaps add a video of the issue? I wasn't able to reproduce it, I'm not running the exact same setup but an Alma 9.0 running on Windows WSL2 chrome_v7VReIsfAc.mp4
Linux hugo-pc 5.15.133.1-microsoft-standard-WSL2 #1 SMP Thu Oct 5 21:02:42 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux /etc/almalinux-release:AlmaLinux release 9.0 (Emerald Puma) /etc/os-release:NAME="AlmaLinux" /etc/os-release:VERSION="9.0 (Emerald Puma)" /etc/os-release:ID="almalinux" /etc/os-release:ID_LIKE="rhel centos fedora" /etc/os-release:VERSION_ID="9.0" /etc/os-release:PLATFORM_ID="platform:el9" /etc/os-release:PRETTY_NAME="AlmaLinux 9.0 (Emerald Puma)" /etc/os-release:ANSI_COLOR="0;34" /etc/os-release:LOGO="fedora-logo-icon" /etc/os-release:CPE_NAME="cpe:/o:almalinux:almalinux:9::baseos" /etc/os-release: /etc/os-release:ALMALINUX_MANTISBT_PROJECT="AlmaLinux-9" /etc/os-release:ALMALINUX_MANTISBT_PROJECT_VERSION="9.0" /etc/os-release:REDHAT_SUPPORT_PRODUCT="AlmaLinux" /etc/os-release:REDHAT_SUPPORT_PRODUCT_VERSION="9.0" /etc/redhat-release:AlmaLinux release 9.0 (Emerald Puma) /etc/system-release:AlmaLinux release 9.0 (Emerald Puma)
Somehow it works right now again.
ok, closing as some potential temporary glitch let us know if you spot it again
I've this issue again :/
Tried to change the time frame from 05:00 to 06:30 (Its currently 09:25 CEST) and it directly changed it again to the current time in my location.
re-opening the issue with a recording to showcase it, this happens when users enter a specific timeframe and don't use the relative ones
https://github.com/netdata/netdata-cloud/assets/82235632/02990bea-e251-4bcf-ac64-60b32ae12a80
Should be fixed in latest release.
Bug description
Hello, every time I want to select a specific timeframe on the Netdata website, e.g. from [...] 19:40 to [...] 19:50 and then I try to save or click on something else, the "to" display goes straight back to the current time and date. And if I click directly on "Apply" then a timeframe from December 30 1996, 10:19 to December 30 1996, 10:20 is selected
Expected behavior
Das man den eingegebenen Timestamp speichert und dann auch angezeigt bekommt.
Steps to reproduce
1.Just normally download and setup Netdata on Device 2.Go to app.netdata.cloud/... 3.Click on Bar for changing the Timeframe and select a custom one
Installation method
kickstart.sh
System info
Netdata build info
Additional info
THe same thing happens at all hosts.