We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Right now, there are several opportunities for the telemetry upload/aggregation process to leave behind artifacts that will never be cleaned up:
upload/<date>.json.lock
load/<date>.json
Furthermore, we never delete local reports, though they cause the local folder to grow, and are likely to become obsolete over time.
local
The rate of growth of these files is slow, but at some point (1.24 or 1.25), we should design a system for cleaning up automatically.
CC @golang/telemetry
The text was updated successfully, but these errors were encountered:
Related Issues and Documentation
(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)
Sorry, something went wrong.
Closing as a dupe of #63884. Thanks gaby.
No branches or pull requests
Right now, there are several opportunities for the telemetry upload/aggregation process to leave behind artifacts that will never be cleaned up:
upload/<date>.json.lock
lock files, if the process is killed during uploadload/<date>.json
files, if the process is killed during uploadFurthermore, we never delete local reports, though they cause the
local
folder to grow, and are likely to become obsolete over time.The rate of growth of these files is slow, but at some point (1.24 or 1.25), we should design a system for cleaning up automatically.
CC @golang/telemetry
The text was updated successfully, but these errors were encountered: