buck2 icon indicating copy to clipboard operation
buck2 copied to clipboard

feat: support configuring the manifold URL

Open lf- opened this issue 6 months ago • 7 comments

I have a highly trivial Manifold implementation internally at Mercury for which I would like to set up for buck2 to receive rage and all that at. This allows for fully implementing the build logs feature mentioned in https://github.com/facebook/buck2/issues/441.

There's still a buck2_core::facebook_only() or two that need removed and some more tidying.

lf- avatar May 28 '25 01:05 lf-

@facebook-github-bot has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. (Because this pull request was imported automatically, there will not be any future comments.)

facebook-github-bot avatar May 28 '25 01:05 facebook-github-bot

This is neat, taking a look

iguridi avatar May 30 '25 20:05 iguridi

One thing missing here is that it won't work when downloading logs via --trace-id .

It actually does work for this, but only because I simply implemented the curl URL structure in locally-euclidean. It is a little goofy but it works.

How would you like to proceed with fixing this after landing this PR though? Should buck2 just fetch them from the fbcdn (and equivalent) URLs in ManifoldClient? Should it implement the actual Manifold GET API (in which case I can't help you because I don't know what it is)?

lf- avatar Jun 04 '25 22:06 lf-

Looks like a bogus CI failure (or at least one I have nothing to do with). Surprised it builds internally at Facebook given that I suspect I broke a usage of the API I replaced (ManifoldClient::new), but shrug! Whatever works!

lf- avatar Jun 05 '25 00:06 lf-

@JakobDegen would you be able to take a look at this PR?

lf- avatar Jun 17 '25 18:06 lf-

Can you take another look? @iguridi

lf- avatar Jul 07 '25 21:07 lf-

Rebased.

lf- avatar Sep 13 '25 00:09 lf-