Code::Blocks Forums
User forums => General (but related to Code::Blocks) => Topic started by: gd_on on May 09, 2014, 03:11:27 pm
-
With some svn versions, I have a recurrent problem when I try to access : http://sourceforge.net/p/codeblocks/code/log/ (or http://sourceforge.net/p/codeblocks/code/HEAD/log/)
This link normally shows the last svn, but with some svn versions it does not work as expected : for example the last problems were with svn 9760 and 9763.
I obtain this error : Error 500, We're sorry but we weren't able to process this request.
But when a new svn version appears, for example here 9761, all is OK again.
The strange thing is that when this new version appears, the previous link like : http://sourceforge.net/p/codeblocks/code/9760/log/ works now correctly.
If I try directly http://sourceforge.net/p/codeblocks/code/9763/log/, this time it's an error 400 ! But I think this page exists.
Of course, there is a work around with biplab mirror : http://cb.biplab.in/websvn/log.php
A sourceforge problem ? something bad when some new svn is proposed ?
gd_on
-
I think someone reported this to SourceForge some time ago (but I do not recall what their response was).
From what I know, SourceForge has trouble displaying a log entry/the most recent log entry, if the timestamps between between it and the previous are "too close" (within a minute, or something, probably). This can happen when using git svn dcommit.
-
Yes, happens every time I commit something. Report it to sf.net, probably if enough people bother them, they'll try to do something. Last time I tried to talk to them about this they did nothing.
-
No problems with your last commit svn 9764. Maybe because, as told Alpha, it's an alone commit.
Looking at your previous commits where there was problems (9760 and 9763), shows that those commits are separated only by a few seconds from the previous ones (here 9759 and 9762 respectively).
So a suggestion : if you have several commits, try to push the last one, let say 1 or 2 minutes after the other ones.
gd_on
-
So a suggestion : if you have several commits, try to push the last one, let say 1 or 2 minutes after the other ones.
Sorry, won't happen... report the problem to sf.net devs if they think it is a serious problem they'll fix it.