#4015 Unable to import svn repo on beta project [25103]
closed
General
2015-08-20
2012-04-05
No
https://sourceforge.net/apps/trac/sourceforge/ticket/25103
Importing SVN repos doesn't seem to be working, I tried importing a repo via the svn import tool, it displayed a notice saying it was importing, but the import didn't happen (code browser doesn't show "importing" like it used to).
bump
We should put logic in place to send an email to the original user, when an import completes (either successfully or with an error).
Error is:
File "/home/dbrondsema/dbrondsema-7024/forge/Allura/allura/model/repository.py", line 224, in init_as_clone self._impl.clone_from(source_url) File "/home/dbrondsema/dbrondsema-7024/forge/ForgeSVN/forgesvn/model/svn.py", line 181, in clone_from self._repo.refresh(notify=False) File "/home/dbrondsema/dbrondsema-7024/forge/Allura/allura/model/repository.py", line 320, in refresh refresh_repo(self, all_commits, notify) File "/home/dbrondsema/dbrondsema-7024/forge/Allura/allura/model/repo_refresh.py", line 38, in refresh_repo repo.refresh_commit_info(oid, seen, not all_commits) File "/home/dbrondsema/dbrondsema-7024/forge/Allura/allura/model/repository.py", line 199, in refresh_commit_info return self._impl.refresh_commit_info(oid, seen, lazy) File "/home/dbrondsema/dbrondsema-7024/forge/ForgeSVN/forgesvn/model/svn.py", line 307, in refresh_commit_info date=datetime.utcfromtimestamp(log_entry.date)) File "/var/local/env-allura/lib/python2.7/site-packages/pysvn/__init__.py", line 29, in __getattr__ raise AttributeError( "%s instance has no attribute '%s'" % (self.__class__.__name__, name) ) AttributeError: PysvnLog instance has no attribute 'date'Succeed/fail email is on allura js/4015. To test, create a new project with an svn repo. Try to clone http://projects.cs.kent.ac.uk/projects/co620_occblocks/svn/OccBlocks/ and you will get error emails (one sent to the user and one sent sf engr). Now clone an svn repo that works like https://easyitsp.svn.sourceforge.net/svnroot/easyitsp/ and you will get a success email. This is branched off [#4100] since there is related code in there waiting on related code in [#3679].
Related
Tickets:
#4100I don't think we should send the stack trace to the end user. Also, this doesn't address the actual error; seems like the story is intended to cover actually fixing the import?
I removed the traceback and prevented breakage around commits that are missing data. If you go to the commit you will see --none-- in some places and not be able to see what files were changed, but at least there aren't any errors. In this repo, only commit 2 and 3 seem to be affected.
Merged