Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 1.5 #59

Merged
merged 22 commits into from
Aug 29, 2022
Merged

Release 1.5 #59

merged 22 commits into from
Aug 29, 2022

Conversation

alexanderzobnin
Copy link
Collaborator

WIP for 1.5 release

@CLAassistant
Copy link

CLAassistant commented Jul 8, 2022

CLA assistant check
All committers have signed the CLA.

@alexanderzobnin alexanderzobnin marked this pull request as ready for review August 24, 2022 08:47
@alexanderzobnin alexanderzobnin changed the title WIP v1.5 Release 1.5 Aug 24, 2022
Copy link
Collaborator

@peterholmberg peterholmberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested and looks good!

Copy link
Member

@srclosson srclosson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love it!

README.md Outdated Show resolved Hide resolved
@@ -366,7 +366,7 @@ func (ds *StravaDatasourceInstance) StravaAPIQueryWithCache(requestHash string)
return nil, err
}
if query.Endpoint == "athlete/activities" {
ds.cache.SetWithExpiration(requestHash, response, time.Minute*5)
ds.cache.Set(requestHash, response)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be interested in a comment on why the expiration is no longer required

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, makes sense. Previously I used predefined cache TTL (5 min) for athlete/activities endpoint, but once I added cache TTL to data source config, I think it's better to use the same interval for all queries. My only concern is fetching recently added activities - it's not possible until cache is expired. Maybe I'll add some smart fetching in next release (always fetch data within cache TTL, like 1 hour, in separate query).

@peterholmberg peterholmberg merged commit 68870f7 into grafana:master Aug 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants