You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2024. It is now read-only.
It's possible that the user sets cadence really low i.e. 1 second and the date range very high, such as 1 year.
This would result in roughly 31,540,000 requests to construct all the textures needed to create this scene. This is too much and should not be allowed. (Maybe it can be allowed when #2 is implemented, but probably still no.)
We should validate the input and not allow any query that we expect to return more than some arbitrary amount of frames that we set in the configuration.
For now, default this to 60, since there are 3 API queries per frame, this already results in 180 API requests. We can increase this limit when #2 is implemented.
The algorithm is:
Get the current cadence.
Count how many cadences exist between the start and end range
If this number is greater than the amount set in the configuration, then fail the request and alert the user.
The text was updated successfully, but these errors were encountered:
It's possible that the user sets cadence really low i.e. 1 second and the date range very high, such as 1 year.
This would result in roughly 31,540,000 requests to construct all the textures needed to create this scene. This is too much and should not be allowed. (Maybe it can be allowed when #2 is implemented, but probably still no.)
We should validate the input and not allow any query that we expect to return more than some arbitrary amount of frames that we set in the configuration.
For now, default this to 60, since there are 3 API queries per frame, this already results in 180 API requests. We can increase this limit when #2 is implemented.
The algorithm is:
The text was updated successfully, but these errors were encountered: