Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed getting contents of http: Filesystem has no item svn: path not found #142

Closed
tapasalok opened this issue Mar 30, 2015 · 3 comments
Closed

Comments

@tapasalok
Copy link

We have created one review request but post that when I perform a Diff from eReviewBoard, I am getting the below error

Failed getting contents of http://_/svn/Path Trial @73571:
org.apache.subversion.javahl.ClientException: Filesystem has no item svn:
'/svn/!svn/bc/73602/http:/_
/svn/Path%20Trial/slider.js' path not found

image

Kindly find below information:

  1. Review Request was created using Eclipse or Review Board Web browser ?
    [Tapas]: Using Web browser
  2. We have to make sure your local checkout is up to date.
    [Tapas]: It is up to date
  3. Did the user directly created diff files / patch files from eclipse and upload them to review board UI tool or using svn command ?
    [Tapas]: using eclipse

Please let us know how to proceed.

@rombert rombert added the defect label Apr 9, 2015
@rombert rombert modified the milestone: 0.13.4 Apr 9, 2015
@selsemore
Copy link
Collaborator

I don't know if this is the problem here, but I submitted a pull request that fixes a problem like this in the case where the file existed in the revision at which the patch was created but does not exist in the HEAD revision.
#147

rombert pushed a commit that referenced this issue Jun 19, 2015
rombert pushed a commit that referenced this issue Jun 19, 2015
@rombert
Copy link
Owner

rombert commented Jun 19, 2015

@tapasalok - I have built a new pre-release based on @selsemore's fix. Can you please download it from https://github.com/rombert/ereviewboard/releases/tag/ereviewboard-0.13.4-pre-2 and let us know if this fixes the problem?

@rombert
Copy link
Owner

rombert commented Feb 19, 2017

No feedback, considering fixed.

@rombert rombert closed this as completed Feb 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants