mlr
New Member
Posts: 3
|
Post by mlr on May 22, 2024 13:10:09 GMT
Congratulations!
How did you discover that -- did they contact you or did you just keep checking? Ours still times out when we go there.
|
|
|
Post by Ben on May 22, 2024 14:03:35 GMT
Hi, whenever we access our projects we get You were using 41001.783 MB when the limit on your account was 40960.0 MB. we can't upgrade bec its payment subscription is not working anymore, we cant access our projects its like our projects are being held hostage. We need to export our projects. please help.
|
|
|
Post by SK on May 22, 2024 19:48:24 GMT
We are still getting 504 error. Is there a way to get a dump of our code if we can't access the repo?
|
|
|
Post by Josh on May 23, 2024 15:28:40 GMT
Is there any update on this? Repo is completely unresponsive.
|
|
|
Post by Tushar Shet on May 24, 2024 12:15:36 GMT
My account repo is working now
|
|
|
Post by FrankG on May 24, 2024 16:31:28 GMT
Good day. Again, sorry for your loss. One of the posts above said they were able to get into their repo and do a dump. We have tried and are still not able to get to the repo. Is it something you have to do on a case by case basis? If there's anything we can do to help, we'll be glad to do so. Just ask.
Thanks, again, in advance for all you're doing.
|
|
|
Post by Tim on May 25, 2024 9:57:15 GMT
Hi - we have not been able to access any of Roopinder's servers as we do not have access to his servers. We have approached some clients who have managed to do a dump - it seems that the servers may transiently reactivate for brief periods (we are not IT savvy, so we are taking all theories on board) to allow access.
We have no legal recourse currently (this seems to be a fairly complex process and will take weeks to months) to direct what happens to his company, or to make payments to his server hosts from his business account to make payments out to those companies to keep things going. This is in all honesty where we are at.
Our advice for now is to please keep trying from time to time, we really do hope that you all get your data back safely and move them to a different hosting site. Roopinder took great pride in the services he provided and would have wanted the same for you. We are keeping his voice and spirit in our minds, seeking advice where we are able. So far, our hands are bound due to legalities.
If any clients have advise for other clients, please keep updating in this forum. Please help one another as you are already doing, your input could help someone out. We are grateful for the community spirit here. Touched, to be honest. And you keep us going when we want to give up because it has been so frustrating for us.
|
|
|
Post by Jan on May 25, 2024 14:12:04 GMT
If you have a Git repository, you should already have the entire commit history (until the outage happened) on your Git client anyway. So you could just upload your local Git repo to a different host. If you have a Subversion repository, it gets (much) more complicated. But if you still have access to the "Browse Source" feature in xp-dev.com Trac Wiki, you could leverage this to "scrape" individual changesets in diff format (along with metadata about the committer and timestamp from the changeset page) and then commit them in order into a new local repository. This way you could reconstruct the entire history of the repository. Example of a link to retrieve a single changeset: xp-dev.com/trac/YOUR_XPDEV_COM_NAME/changeset/12345/YOUR_XPDEV_COM_SUBVERSION_REPO_NAME?format=diff&new=12345where 12345 is the changeset number (increasing monotonically from 1). Not sure how well this would work if you committed big binary files rather than just source code. If you wish to back up the contents of an xp-dev.com Trac wiki, you can do it using Trac's XMLRPC API to retrieve each entity type. Migrating dumps obtained that way it to a new Trac is more involved (some metadata cannot be simply recreated in a new installation through the same XMLRPC API, but needs to be updated in the target database, e.g. you can't recreate "old" tickets or set ownership and timestamps of attachments through the XMLRPC API).
|
|
|
Post by syed asad on May 26, 2024 5:37:15 GMT
still not accessing the url
|
|
arne
New Member
Posts: 3
|
Post by arne on May 27, 2024 8:06:36 GMT
Our repository is back, and we've been able to export a dump! So it seems that there is some progress I can log-in at xp-dev.com again but I cannot access my Subversion/SVN repositories -- neither through the xp-dev.com website nor through an SVN client @kath: how did you access your SVN(?) repos?
|
|
|
Post by Tushar Shet on May 27, 2024 8:24:22 GMT
Again I am not able to access the xp dev account
|
|
|
Post by MASR74 on May 27, 2024 21:57:59 GMT
We are so sorry for your loss. Using local copies, we have successfully migrated our xp-dev code repositories to a new platform. However we could really use help migrating our 15-year archive of TRAC information. Please let us know if we can help in any way. Hi, do you have a suggestion where to migrated code? that has the same functionality as xp-dev ? Help will be appreciated. Regards Manuel
|
|
|
Post by GavinF on May 28, 2024 2:35:21 GMT
Very sorry for the family's loss.
If anyone has had success getting access to their SVN repository, please let me know what steps you took. It appears I am unable to. I am hesitant to cancel my subscription until I archive the repository.
|
|
|
Post by Ben on May 28, 2024 3:03:43 GMT
In our case, we cannot access our projects because our project went over 40gb.. like 40.1 and xp-dev locked our project telling us we can only access if we upgrade to a higher tier. We could easily solve if you let us DELETE SOME FILES but they locked us out. Now I had no choice but to upgrade but PAYMENT SYSTEM IS DOWN because of what happened. We are trapped! we have years of files on the servers. I'm also afraid to cancel my subscription, do they have any legal obligations for this?
|
|
|
Post by syed on May 28, 2024 7:14:50 GMT
it is a long time we are unable to connect portal it is dragging our work please do needfull action on this please tell us the estimated time when it will be up
|
|