Page MenuHomePhabricator

cannot upload diff using svn
Closed, DuplicatePublic

Description

I have used svn mv somefile otherfile
then tried to upload a new diff
then I got error (logs with trace)

svn: E200009: Could not cat all targets because some targets don't exist
svn: E200009: Illegal target for the requested operation
 at [<phutil>\src\future\exec\ExecFuture.php:416]
arcanist(head=master, ref.master=b32149495b85), phutil(head=master, ref.master=e8eaafe04d64)
  #0 ExecFuture::resolvex() called at [<phutil>\src\future\exec\execx.php:17]
  #1 execx(string, string, string) called at [<arcanist>\src\repository\api\ArcanistSubversionAPI.php:470]
  #2 ArcanistSubversionAPI::buildSyntheticAdditionDiff(string, string, string) called at [<arcanist>\src\repository\api\ArcanistSubversionAPI.php:393]
  #3 ArcanistSubversionAPI::getRawDiffText(string) called at [<arcanist>\src\parser\ArcanistDiffParser.php:86]
  #4 ArcanistDiffParser::parseSubversionDiff(ArcanistSubversionAPI, array) called at [<arcanist>\src\workflow\ArcanistDiffWorkflow.php:938]
  #5 ArcanistDiffWorkflow::generateChanges() called at [<arcanist>\src\workflow\ArcanistDiffWorkflow.php:495]
  #6 ArcanistDiffWorkflow::run() called at [<arcanist>\scripts\arcanist.php:382]

Revisions and Commits

Event Timeline

epriestley added a subscriber: epriestley.

I can't reproduce this. Here's what I did:

I used svn mv ... to move a file:

epriestley@orbital ~/dev/scratch/subversion $ svn mv README README.moved
A         README.moved
D         README

Here's the working copy state after the move:

epriestley@orbital ~/dev/scratch/subversion $ svn st
D       README
A  +    README.moved

Then I ran arc diff:

epriestley@orbital ~/dev/scratch/subversion $ arc diff
Linting...
No lint engine configured for this project.
Running unit tests...
No unit test engine is configured for this project.
 SKIP STAGING  Unable to determine repository for this change.
Created a new Differential revision:
        Revision URI: http://local.phacility.com/D112

Included changes:
  V       README
             to: README.moved
  V       README.moved
             from: README

This worked properly and created a revision.

What can I do differently to reproduce the problem you're experiencing?

which svn client do you use ?
i saw you have the file on the same folder. can you try moving the files between differnt folders ?
if it still working maybe we should upgrade phabricator.
which version of phabricator did you use ?

which svn client do you use ?

If this depends on a particular client, you need to tell me that as part of your reproduction steps.

i saw you have the file on the same folder. can you try moving the files between differnt folders ?

That also works fine.

if it still working maybe we should upgrade phabricator.

Yes, we ask you to upgrade before reporting a bug. Many bug reports we receive have already been fixed. See Contributing Bug Reports.

which version of phabricator did you use ?

HEAD of master.

which svn client do you use ?

If this depends on a particular client, you need to tell me that as part of your reproduction steps.

i saw you have the file on the same folder. can you try moving the files between differnt folders ?

That also works fine.

if it still working maybe we should upgrade phabricator.

Yes, we ask you to upgrade before reporting a bug. Many bug reports we receive have already been fixed. See Contributing Bug Reports.

which version of phabricator did you use ?

HEAD of master.

I have used the tortoiese svn.

Hi, I have upgraded both tortoiesesvn(1.9) and phabricator (server+client) and I still get this error.
I have tried to understand what happens to that and I think i have found the problem.
the problem is that arcanist run this command:

svn cat "http://subversion:8888/svn/main/pd/kyc/cdd/trunk/CDD 20Package/JAVA_AccessDataset.xml"@"550967"

while he should run :

svn cat "http://subversion:8888/svn/main/pd/kyc/cdd/trunk/CDD Package/JAVA_AccessDataset.xml"@"550967"

It seems like arcanist use '20' as a space charachter but url is not correct.

Is there any news about this issue ?