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
For recent data, such as the last PRs or issues, the data changes often. Therefore re-running the tool a few days later will quietly and unexpectedly return stale data.
How can one reproduce the bug?
Run ./bin/project prs stats --from=2022-01-01 --to=2022-XX-YY on Monday with XX and YY being Monday.
Run it again on Thursday with XX-YY being Thursday.
Observe identical results to Monday's.
What is the expected behavior?
In the example above data for this week should have been refreshed.
Do you have any additional context?
A probably fix is to set cache expiration to minutes/hours for recent data explicitly, or always fetch data that belongs to new dates without cache.
The text was updated successfully, but these errors were encountered:
What is the bug?
The cache implementation forces a cache hit via https://github.com/opensearch-project/project-tools/blob/main/lib/faraday/cache_control.rb as long as the URL is the same. This is because historical data rarely changes and making page long requests for old issues or PRs is typically wasteful. Users can always specify
--no-cache
to get fresh data.For recent data, such as the last PRs or issues, the data changes often. Therefore re-running the tool a few days later will quietly and unexpectedly return stale data.
How can one reproduce the bug?
./bin/project prs stats --from=2022-01-01 --to=2022-XX-YY
on Monday with XX and YY being Monday.What is the expected behavior?
In the example above data for this week should have been refreshed.
Do you have any additional context?
A probably fix is to set cache expiration to minutes/hours for recent data explicitly, or always fetch data that belongs to new dates without cache.
The text was updated successfully, but these errors were encountered: