Endless query loop after starting the web frontend locally, 'skip' parameter without effect
See original GitHub issuePreflight Checklist
- I have read the Contributing Guidelines for this project.
- I have searched the issue tracker for an issue that matches the one I want to file, without success.
Issue Details
- Operating System:
- macOS 12.5.12
- Browser:
- Chrome 104
- NodeJS:
- v16.12.0
Expected Behavior
Show whatever data the root URL of the web UI shows.
Actual Behavior
When opening the root URL of the web UI, I saw a permanent spinner showing something like “loading data”.
The API logged entries like this constantly:
[1] 2022-08-30T17:18:29.230Z [api] info: Footprint API request started.
[1] 2022-08-30T17:18:29.230Z [Cache] info: Using local cache file...
The browser’s network panel showed a fast sequence of requests to URLs like http://localhost:3000/api/footprint?start=2021-08-30&end=2022-08-30&ignoreCache=false&groupBy=day&limit=90&skip=257670
, with the skip
parameter being incremented with every request.
It looks like whatever numeric value I use as skip
parameter, the request always returns data. So I’m thinking that the frontend never reaches any exit condition.
skip = 0:
... "periodStartDate":"2022-08-29T00:00:00.000Z","periodEndDate":"2022-08-29T23:59:59.000Z" ...
skip = 10:
... "periodStartDate":"2022-08-29T00:00:00.000Z","periodEndDate":"2022-08-29T23:59:59.000Z" ...
skip = 100000000:
... "periodStartDate":"2022-08-29T00:00:00.000Z","periodEndDate":"2022-08-29T23:59:59.000Z" ...
To Reproduce
Screenshots
Additional Information
I set up the application locally using the guided install. I connected it to an Azure subscription.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top GitHub Comments
@marians No worries, we’ll go ahead and close this issue since there’s no action to take at the moment. But if you get a chance to retest and encounter the same or a different issue, feel free to reopen or a leave a new comment with the details!
I wasn’t able to test this since I reported the issue, sorry