KEMBAR78
Benchmarks dynamo update script to use ClickHouse instead of Rockset by clee2000 · Pull Request #140574 · pytorch/pytorch · GitHub
Skip to content

Conversation

@clee2000
Copy link
Contributor

@clee2000 clee2000 commented Nov 13, 2024

@clee2000 clee2000 marked this pull request as ready for review November 13, 2024 18:22
@pytorch-bot
Copy link

pytorch-bot bot commented Nov 13, 2024

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/140574

Note: Links to docs will display an error until the docs builds have been completed.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

✅ No Failures

As of commit f8c667e with merge base 2675ef8 (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

data=json.dumps(params),
headers={"Content-Type": "application/json"},
# This key can only access query endpoints, specifically the url above at the moment
auth=("eJBpUENTBQ4MdbHPYxrl", "4b1draOBY5zwva7QXTBgAwqbYrpNKFaXGNYqASt5a9"),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess this is a read-only key, but I think we should still keep it a secret as this looks like an open invitation to people trying to gain access or ddos our query endpoint

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How do you propose distributing the key to everyone who wants to run this script?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should make a request to CH to see if they allow no-auth read-only request to their API endpoint like what Rockset gives us. Another solution that doesn't block us is to create a simple API on HUD that forward the queries to CH and returns the results, we can then keep the read-only secret on Vercel

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't these solutions have the same problem as before?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed the credentials an put a link to them instead

@clee2000 clee2000 requested review from a team and huydhn November 15, 2024 17:08
@clee2000
Copy link
Contributor Author

@pytorchbot merge -f "no trunk needed"

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

pobin6 pushed a commit to pobin6/pytorch that referenced this pull request Dec 5, 2024
…ytorch#140574)

Query works but the part where it parses the job name is broken

Pull Request resolved: pytorch#140574
Approved by: https://github.com/huydhn
@github-actions github-actions bot deleted the csl/ch_benchmarks_update_expected branch December 19, 2024 02:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants