-
Notifications
You must be signed in to change notification settings - Fork 185
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
for MPP-3467: add googlecloudprofiler to PrivateRelayConfig.ready #4321
Conversation
acba5ce
to
225d16b
Compare
225d16b
to
86bc582
Compare
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.
Thanks @groovecoder! I didn't see any blockers for merging this, since it represents working code in local dev and Heroku (which took a lot of effort!). I imagine we'll need more changes to get it running in GCP.
I was able to load get_version_info
from it's original spot by importing inside the function rather than at the top level. If you want to do that in this PR, please do, but I can also do it in my next PR (#4347) which touches all these files again.
86bc582
to
3658fb9
Compare
Also moves get_version_info to privaterelay.apps
3658fb9
to
24187e0
Compare
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
Google Cloud Profiler
https://cloud.google.com/profiler/docs
https://cloud.google.com/profiler/docs/profiling-python
Screenshot (if applicable)
How to test
Follow the steps in https://github.com/mozilla/fx-private-relay/pull/4321/files#diff-01748e8486974d80818eb9b8c9f623769f0ddb0821f867644d6e113f0dc008d3 for local server setup.
Checklist (Definition of Done)
Product Owner accepted the User Story (demo of functionality completed) or waived the privilege.All acceptance criteria are met.Jira ticket has been updated (if needed) to match changes made during the development process.All UI revisions follow the coding standards, and use Protocol tokens where applicable (see/frontend/src/styles/tokens.scss
).l10n changes have been submitted to the l10n repository, if any.