Opened 16 years ago
Closed 16 years ago
#7524 closed defect (duplicate)
resync w/o repository should be a no-op
Reported by: | anonymous | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | admin/console | Version: | 0.11.1 |
Severity: | normal | Keywords: | |
Cc: | geoff+trac@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
A resync operation on a project without a repository_path defined results in a fatal error that the repository provider cannot be found. This happens because the built-in repository providers are not loaded when the repository path is empty. Resync ought to detect that there is no repository configured and should either print a warning that there is no repository configured or just do nothing. My preference is to do nothing, but in any case the command should be successful rather than raising an exception.
Attachments (0)
Change History (2)
comment:1 by , 16 years ago
Cc: | added |
---|
comment:2 by , 16 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Probably addressed in new resync code of #7723.