Page MenuHomePhabricator

Unhandled Exception ("FilesystemException") - File system entity `/var/repo/PHABES/' does not exist.
Closed, DuplicatePublic

Description

I created two repository mirrors in our instance of Phabricator: Phabricator/PHAB and Phabricator-Extension-Sprint/PHABES. While the daemons are still pulling PHAB from upstream, they apparently did not yet create the repository for PHABES in the filesystem. I get following message when trying to access /diffusion/PHABES/:

Unhandled Exception ("FilesystemException")
File system entity `/var/repo/PHABES/' does not exist.

This is not ideal, because it does not allow me to edit the repository (e.g. add a project tag) for quite a while (PHAB is large).

Possible solution: Make repository pulling and repository creation two distinct tasks/queues (with proper dependency from "create" to "pull"), so that the basic creation can proceed while bigger repositories are still being pulled.

Event Timeline

devurandom raised the priority of this task from to Needs Triage.
devurandom updated the task description. (Show Details)
devurandom added projects: Diffusion, Daemons.
devurandom added a subscriber: devurandom.

Looking T9080: Service-based repositories in Phacility cluster fail too abruptly if cloning fails this isn't fixed for me. Until the UI allows you to configure the repository, I don't think this should be closed.

To reproduce:

  1. Import an Existing External Repository
  2. Give some bad credentials (lock them)
  3. Wait
  4. Reload

Result:

Unhandled Exception ("FilesystemException")	
File system entity `/var/repo/repo-name/' does not exist.

This prevents correcting the bad credentials using Diffusion's web UI. You can't load the edit page either.

I've experienced this too. When credentials are wrong, it should at least give an option to correct them.

I can't reproduce this:

Screen Shot 2015-10-07 at 6.30.51 AM.png (314×684 px, 34 KB)

Screen Shot 2015-10-07 at 6.30.59 AM.png (634×1 px, 113 KB)

Please file a new task with detailed reproduction steps if you're still experiencing an issue here.

Hi guys,
Same issue here!

  1. Import an Existing External Repository
  2. Give some bad credentials
  3. After seeing that the import failed, y navigated to other page in order to look where to edit the ssh keys.
  4. When I came back to "https://phabricator.example.com/diffusion/1" I got the error described here.
  5. To solve this I had to input manually in the browser "https://phabricator.example.com/diffusion/1/edit" and changed the repo source from git@gitexample.com/proyect.git to http://gitlab.example.com/proyect.git and enter my gitlab.example.com login credentials.

I hope this can help you guys.
+ Dumb question: The SSH Key I have to use when importing an existing external repo is the same I have in my SSH Keys at gitlab.example.com ? I would like to use SSH instead of http to import the repos.

Thanks in advance, and congratulations for the great work in this project!