I am a newbie to git, so I made a grave mistake. On getting a new laptop, I accidentally pushed a commit that removed most of the files except the ones I edited in our repo.
In Android Studio, I attempted to fix this by clicking on the git log, and trying to "reset the current branch to here".
This gave me an error of:
Error downloading object: java_pid2812.hprof (58df4cf):
Smudge error: Error downloading java_pid2812.hprof
(58df4cfb920117556d8a695631aef8a75834d2e71ec360a7fbbc5c79e4fe84e2):
batch response: This repository is over its data quota.
Account responsible for LFS bandwidth should purchase more
data packs to restore access.
I purchased a data pack on my account, and this did not resolve this issue. How can I restore the repo to before that commit was pushed?
Thanks.
Related
enter image description here
I tried this, but there's an error
enter image description here
Error message says
No .platform/services.yaml file found in the repository.
No .platform/routes.yaml file found in the repository.
enter image description here
but It's definitely there.
i don't understand...
Without seeing your repository, my guess is that those two files haven't been committed to the repository (the ! next to each of them in your third image). You can double-check by doing git status. If they are definitely committed, hop into our slack workspace and/or submit a support ticket so we can take a look at what's happening.
It sounds like you use visual studio and you need to:
add the files to git
commit the files to git
push the file to platform.sh
If you have trouble with this, you may want to use one of the existing template https://docs.platform.sh/development/templates.html and the modify these files.
In general, it is easier to start from a functional solution than a non working one ;-)
I have permanently deleted a package from Artifacts.
Is there a way to restore it?
Now if I try to push I am getting this error:
Response status code does not indicate success: 409 (Conflict - The version 3.18.1 of Google.Protobuf has been deleted. It cannot be restored or pushed. (DevOps Activity ID: 014272E1-B940-428D-B3DF-4E67E5890D4B))
To add a Artifacts deleted nupkg
I am afraid there is no such way to restore it.
According to the document Understand immutability of packages:
Once you publish a particular version of a package to a feed, that version number is permanently reserved. You cannot upload a newer revision package with that same version number, or delete it and upload a new package at the same version.
That because many package clients, including NuGet, keep a local cache of packages on your machine. Once a client has cached a particular package#version, it will return that copy on future install/restore requests. If, on the server, you replace package#version (rev 1) with a new package#version (rev 2), the client is unable to tell the difference. This can lead to indeterminate build results from different machines.
So we could not overwrite all packages that have already been uploaded, even we could not delete them and re-uploaded. To resolve this issue, you could try to upload the packages with a new version or create a new feed to save the package.
I am currently doing an end of year project and we're using GitLab. This is the first time I am using this and was confident about it until the following problem occurred.
After creating the clone, I've been working on my project and committed quite a few files to the school server by using git push after doing the prerequisites of git add and etc.
Now, I've decided to completely start again. I deleted everything manually from GitLab and then all the files from within the folder where the clone directs to. I started working on my new work in a separate folder - while still working on my new file, I decided to move all the files to the previous file where I deleted everything, where the clone was originally set for GitLab to save my files within the schools server.
When typing git status, the following appears (Please excuse the picture instead of me inserting the code in here. I tried entering the output on the console in here but was having editing problems).
I don't understand how to fully delete everything. So, I want to get rid of all Changes to be committed: and Untracked files:.
If you want to push there nothing to do with git status . git status only shows what been added to your repository before commit.
I am not sure this is the right forum for this question.
I use Gitlab for storing all my codes, version control, etc. since I don' trust my PC. It suddenly dawned on me, will my account get deleted if I don't access it for a while or is there a limit to size of project that I can push there, etc. Basically use Gitlab for file storage also.
I didn't find any relevant answers on google. Can you please point me to these answers?
Gitlab has a maximum auf 10G/repo. If you have larger files you should use Git LFS otherwise git is for small code files. So i don't think that your account is deleted if you are inactive. Otherwise you should get an e-mail with a notification.
https://about.gitlab.com/blog/2015/04/08/gitlab-dot-com-storage-limit-raised-to-10gb-per-repo/
https://docs.gitlab.com/ee/administration/lfs/manage_large_binaries_with_git_lfs.html
In subversion I'm trying to commit a project but running into an issue.
The error I get is
Illegal repository URL ''
How come I can run update, but commit on the same tree shows that?
Try this, it worked for me:
Create a folder.
Right button over folder and create repo here.
When pop up appears select create folder structure and then open folder.
When repository browser appears you see tags branch etc, right button again and create folder but now with tool tortoise.
Update you file to folder.
After some hunting around it seems that a few other people have experienced some sort of local corruption at the top level their checked out project directory which is where I was committing from.
I followed the same procedure that was used to solve those cases which is to back up the sources. Check out the project again. Finally copy the changed files back over the freshly checked out copy. Check it builds correctly. And then commit that.
It seemed to solve it for me.