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

fix: send analytics on a best effort basis #254

Merged
merged 2 commits into from
Jan 11, 2021
Merged

fix: send analytics on a best effort basis #254

merged 2 commits into from
Jan 11, 2021

Conversation

hbagdi
Copy link
Member

@hbagdi hbagdi commented Jan 6, 2021

With this patch, analytics is sent only on a best-effort basis.
Failure to send analytics doesn't result in any slowdown for the end
user.

Fix #253

cmd/root.go Outdated Show resolved Hide resolved
cmd/root.go Outdated Show resolved Hide resolved
cmd/root.go Outdated Show resolved Hide resolved
Co-authored-by: Michał Flendrich <michal@flendrich.pro>
@rainest rainest mentioned this pull request Jan 11, 2021
@mflendrich mflendrich merged commit 739e49c into main Jan 11, 2021
@mflendrich mflendrich deleted the fix/analytics branch January 11, 2021 16:27
rainest pushed a commit that referenced this pull request Apr 21, 2021
With this patch, analytics is sent only on a best-effort basis.
Failure to send analytics doesn't result in any slowdown for the end
user.

Fix #253
AntoineJac pushed a commit that referenced this pull request Jan 23, 2024
With this patch, analytics is sent only on a best-effort basis.
Failure to send analytics doesn't result in any slowdown for the end
user.

Fix #253
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.

decK analytics noticeably slow down commands which should complete fast
3 participants