influxdata / influxdata/influxdb
OSS 2.1.1 Auto refresh is not working properly
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
Auto refresh stops refreshing seemingly randomly.
Auto refresh is not sticky, has to be set each time.
The auto refresh service does not allow indefinite without any activity timeout.
__Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.
1. Select "Enable Auto Refresh" from a dashboard
2. Turn on "Indefinite"
3. Set inactivity timeout for a time at least 24 hours. Almost anytime setting does the same thing.
4. Walk away for a while, usually at least 10 minutes
5. Return and auto refresh has turned off
__Expected behavior:__
Refresh to continue indefinitely
__Steps to reproduce:__
Indefinite setting with long inactivity timeout fails.
1. Select "Enable Auto Refresh" from a dashboard
2. Turn on "Indefinite"
3. Set inactivity to 29 days
4. Select confirm
5. Immediately the reset dialog will appear
`Your dashboard auto refresh settings have been reset due to inactivity`
__Expected behavior:__
Refresh unless there is 29 days of inactivity.
__Actual behavior:__
Stops refreshing
__Environment info:__
* System info: Run `uname -srm` and copy the output here
`Linux 5.13.0-28-generic x86_64`
* InfluxDB version: Run `influxd version` and copy the output here
`InfluxDB 2.1.1 (git: 657e1839de) build_date: 2021-11-09T03:03:48Z`
* Other relevant environment details: Container runtime, disk info, etc
Browser: `Google Chrome Version 98.0.4758.102 (Official Build) (64-bit)`
__Config:__
Copy any non-default config values here or attach the full config as a gist or file.
```toml
bolt-path = "/data1/influxdb/influxd.bolt"
engine-path = "/data1/influxdb/engine"
http-bind-address = ":8086"
```
Contributor guide
Research direction
Reproduce the dashboard auto-refresh behavior in InfluxDB 2.1.1 using Chrome, following both reported sequences and checking the inactivity timeout reset. No source files or tests are named; done means identifying and fixing the cause so indefinite refresh remains active until the configured inactivity period, and adding coverage for the reported settings.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100