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

Eng 2724 enable usage tracking for code spaces #1154

Merged
merged 5 commits into from
Apr 3, 2023

Conversation

likawind
Copy link
Contributor

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

  • I have created a descriptive PR title. The PR title should complete the sentence "This PR...".
  • I have performed a self-review of my code.
  • I have included a small demo of the changes. For the UI, this would be a screenshot or a Loom video.
  • If this is a new feature, I have added unit tests and integration tests.
  • I have run the integration tests locally and they are passing.
  • I have run the linter script locally (See python3 scripts/run_linters.py -h for usage).
  • All features on the UI continue to work correctly.
  • Added one of the following CI labels:
    • run_integration_test: Runs integration tests
    • skip_integration_test: Skips integration tests (Should be used when changes are ONLY documentation/UI)

@likawind likawind requested review from vsreekanti and cw75 March 30, 2023 22:27
// 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)
Copy link
Contributor Author

@likawind likawind Mar 30, 2023

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?

Copy link
Contributor Author

@likawind likawind Mar 30, 2023

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

Copy link
Contributor

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)
Copy link
Contributor

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.

@likawind likawind added the skip_integration_test Skips required integration test (only documentation/UI changes) label Apr 3, 2023
@likawind likawind added run_integration_test Triggers integration tests skip_integration_test Skips required integration test (only documentation/UI changes) and removed skip_integration_test Skips required integration test (only documentation/UI changes) run_integration_test Triggers integration tests labels Apr 3, 2023
@likawind likawind merged commit 9eab748 into main Apr 3, 2023
@likawind likawind deleted the eng-2724-enable-usage-tracking-for-code-spaces branch April 3, 2023 23:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip_integration_test Skips required integration test (only documentation/UI changes)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants