Page MenuHomePhabricator

Remove call to "arcanist.projectinfo" from `arc export`
ClosedPublic

Authored by joshuaspence on May 21 2015, 9:11 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Nov 18, 5:22 PM
Unknown Object (File)
Thu, Nov 14, 9:55 PM
Unknown Object (File)
Mon, Nov 11, 5:53 AM
Unknown Object (File)
Fri, Nov 8, 8:55 PM
Unknown Object (File)
Thu, Nov 7, 1:06 AM
Unknown Object (File)
Thu, Oct 24, 6:16 AM
Unknown Object (File)
Oct 21 2024, 6:33 PM
Unknown Object (File)
Oct 21 2024, 5:55 AM
Subscribers

Details

Summary

Ref T7604. Remove a call to arcanist.projectinfo from arc export. This Conduit call was only used to detect the repository encoding, which we should be able to do locally anyway.

I was considering removing the $projectName from ArcanistBundle as well, but I'm not convinved that this is a good idea. Specifically, doing so would make it difficult to issue the "This patch is for the 'X' project, but the working copy belongs to the 'Y' project" error. We could potentially use the repository callsign for this purposes, but this isn't portable across installs.

Test Plan

I'm not quite sure how to test this. I suspect that this functionality isn't widely used anyway.

Diff Detail

Repository
rARC Arcanist
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

joshuaspence retitled this revision from to Remove "arcanist projects" from bundles.
joshuaspence updated this object.
joshuaspence edited the test plan for this revision. (Show Details)
joshuaspence edited edge metadata.

Further progress

joshuaspence retitled this revision from Remove "arcanist projects" from bundles to Remove call to "arcanist.projectinfo" from `arc export`.May 21 2015, 9:54 AM
joshuaspence updated this object.
joshuaspence edited the test plan for this revision. (Show Details)
joshuaspence added a reviewer: epriestley.
epriestley edited edge metadata.

I think removing the name from the bundle is reasonable. I don't think the warning is particularly important, and it would be fine to drop it entirely.

Shy of that, we could check remote URIs:

This patch was generated in a repository with origin ssh://mycompany.com/libphutil.git, but you are applying it in a repository which does not use this remote. You might be trying to patch the wrong working copy. Continue anyway? [Y/n]

This revision is now accepted and ready to land.May 24 2015, 1:19 PM

I don't think it's the simple. I just attempted to do arc patch with a differential that had a dependent diff in an other repository. The behavior seems unexpected to me, it attempts to patch the revision from the other repository.

I don't think it's the simple. I just attempted to do arc patch with a differential that had a dependent diff in an other repository. The behavior seems unexpected to me, it attempts to patch the revision from the other repository.

I filed T8307.

joshuaspence edited edge metadata.

Remove project name from bundle

This revision was automatically updated to reflect the committed changes.