-
Notifications
You must be signed in to change notification settings - Fork 18
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
Eng 2724 enable usage tracking for code spaces #1154
Conversation
// This call generates a unique hash of the host device in a privacy-preserving fashion. | ||
// Details can be found here: https://github.com/denisbrodbeck/machineid | ||
var err error | ||
machineID, err = machineid.ProtectedID(hashKey) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cw75 For non-codespace testing, I should be able to hit this line if I run aqueduct clear
followed by aqueduct start
right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If that's the case, my local testing looks good. I also ran an instance inside code space, so as long as you can see likawind
ID in our usage stats (in code_space
env), we should be good to go
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I saw your id.
// This call generates a unique hash of the host device in a privacy-preserving fashion. | ||
// Details can be found here: https://github.com/denisbrodbeck/machineid | ||
var err error | ||
machineID, err = machineid.ProtectedID(hashKey) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I saw your id.
…g-2724-enable-usage-tracking-for-code-spaces
Describe your changes and why you are making these changes
This PR enables usage tracking for codespaces by checking codespace specific env vars. We also added some documentation improvements to various observed issues when using code spaces.
Related issue number (if any)
ENG-2724
Loom demo (if any)
Checklist before requesting a review
python3 scripts/run_linters.py -h
for usage).run_integration_test
: Runs integration testsskip_integration_test
: Skips integration tests (Should be used when changes are ONLY documentation/UI)