Ref T2783. This method is kind of goofballs:
- We send a big list of paths to it.
- It sends back a giant blob of HTML.
Instead, just figure out the path we want locally, then fetch the content with diffusion.filecontentquery.
Details
Details
- Reviewers
btrahan - Maniphest Tasks
- T2783: Make working-copy operations service-oriented
- Commits
- Restricted Diffusion Commit
rPcae8c49745cc: Fix diffusion.readmequery to work in a cluster enviroment
- Viewed main view and directory view, saw a README.
- See screenshots.
Diff Detail
Diff Detail
- Repository
- rP Phabricator
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
Before, since we don't explicitly trust the wire response as HTML, we'd get this:
After, we get a proper rendering in a cluster:
We could have retained a more similar version of this query and trusted the response, but ugh.