Unable to repo sync cyanogenmod source stuck at 99% - android

Fetching projects: 97% (505/520) Fetching project CyanogenMod/android_hardware_qcom_media
Fetching project CyanogenMod/android_hardware_qcom_audio
fatal: Couldn't find remote ref refs/heads/stable/cm-13.0-ZNH2KB
Unexpected end of command stream
Fetching project CyanogenMod/android_hardware_qcom_media
Fetching project CyanogenMod/android_hardware_qcom_audio
Fetching project CyanogenMod/android_hardware_qcom_media
Fetching projects: 98% (510/520) Fetching project CyanogenMod/android_hardware_qcom_audio
fatal: Couldn't find remote ref refs/heads/stable/cm-13.0-ZNH2KB
Unexpected end of command stream
Fetching project CyanogenMod/android_hardware_qcom_media
Fetching project CyanogenMod/android_hardware_qcom_audio
Fetching project CyanogenMod/android_hardware_qcom_media
Fetching projects: 99% (515/520) Fetching project CyanogenMod/android_hardware_qcom_media
fatal: Couldn't find remote ref refs/heads/stable/cm-13.0-ZNH2KB
Unexpected end of command stream
fatal: Couldn't find remote ref refs/heads/stable/cm-13.0-ZNH2KB
Unexpected end of command stream
error: Cannot fetch CyanogenMod/android_device_qcom_sepolicy
error: Cannot fetch CyanogenMod/android_vendor_qcom_opensource_dataservices
error: Cannot fetch CyanogenMod/android_vendor_qcom_opensource_time-services
error: Cannot fetch CyanogenMod/android_vendor_qcom_opensource_dpm
error: Exited sync due to fetch errors

Use--force-broken or -f to recover from network errors.
So, use repo sync like this:
repo sync -j8 -f
If you still get errors, add a comment.

Difficulties syncing the source tree (TCP issues)
Symptom: repo sync hangs while syncing, often when it's completed 99% of the sync.
Cause: Some settings in the TCP/IP stack cause difficulties in some network environments, so that repo sync neither completes nor fails.
Fix: On Linux, enter the command:
sysctl -w net.ipv4.tcp_window_scaling=0
On macOS, disable the rfc1323 extension in the network settings.
https://source.android.com/setup/build/known-issues

Related

Unable to make a pull in gradle file

i´m trying to make a task in Gradle for my Android project ( using Kotlin DSL ) where I need to do an automatic pull for my "develop" branch.
This are the commnand I want to run :
git pull origin develop:develop
In the terminal this works just fine.
I`m using "commandLine" with "exec" in my gradle file and I´m having this error message:
code:
tasks.register<ReleaseTask>("makePull") {
exec { commandLine("git", "pull", "origin develop:develop") }
}
error message:
ssh: Could not resolve hostname origin develop: nodename nor servname provided, or not known
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
FAILURE: Build failed with an exception.
I don´t have any issue if I try this commands in the terminal, do you know what i´m doing wrong ?
You haven't separated the origin and the develop:develop arguments in the gradle version. Use this instead:
commandLine("git", "pull", "origin", "develop:develop")

Github Push failed: Failed with error: RPC failed; curl 56 LibreSSL SSL_read: error:140943FC:SSL routines:SSL3_READ_BYTES:sslv3

When i am Trying to push my android project to GitHub i got this error
Failed with error: RPC failed; curl 56 LibreSSL SSL_read:
error:140943FC:SSL routines:SSL3_READ_BYTES:sslv3 alert bad record
mac, errno 0 The remote end hung up unexpectedly The remote end hung
up unexpectedly
It can be caused by large files in your repo. Github has 100 MB limit for a single file in a repo. You might want to check it by using git lfs migrate info.
I've had the same issue but this particular error was intermittent. I occasionally have seen "error: GH001: Large files detected. You may want to try Git Large File Storage". Also when I switched to SSH for remote origin instead of HTTPS it gave me broken pipe error message.
I already used LFS but my .gitattributes missed some large files so I've updated it and run git lfs migrate import --include="*.fileextension" then pushed to github without an error. See https://help.github.com/articles/moving-a-file-in-your-repository-to-git-large-file-storage/.

error while pushing to GitHub

i want to commit changes to GitHub
i can do it with GitHub desktop but i get this error when i try with android studio commit changes button :
"Failed with error: fatal: unable to access 'https://github. ... .git/': The requested URL returned error: 403"
You need to first find the correct SSH/ HTTP address to the repository that you would like to commit to then you can run this command in your terminal:
git remote add origin [remote repository URL]
once connected, you should be able to commit the changes.

12:44:45 PM Push failed: fatal: repository not found but it exists

I am using Github to sync my Android Studio Project.
I have been able to commit and push successfully for over a month.
After adding some files, I received this error.
12:44:45 PM Push failed: fatal: repository 'https://rrtigga#github.com/rrtigga.GetDisciplined1_0.git/' not found
However, the repo exists...
Here is a snippet from my terminal:
Rohits-MacBook-Air:GetDisciplined1_0 Spicycurryman$ git remote add origin rrtigga#github.com:rrtigga/GetDisciplined1_0.git
fatal: remote origin already exists.
Rohits-MacBook-Air:GetDisciplined1_0 Spicycurryman$
This is kind of an awkward error... I did some research and was unable to produce a solution.
GitHub: ERROR: Repository not found. fatal: The remote end hung up unexpectedly (different from similar posts apparently)
EDIT: It really exists:
https://github.com/rrtigga/GetDisciplined1_0
What is the problem here and how can I fix it?
You have a remote called origin which is configured to point to https://github.com/rrtigga.GetDisciplined1_0.git/, which is not the correct URL for your repository. You should be using either https://github.com/rrtigga/GetDisciplined1_0.git for access over HTTPS, or git#github.com:rrtigga/GetDisciplined1_0.git for SSH.
The error "remote origin already exists" means what it says: you're trying to add a remote with the same name as one that already exists. You need to either delete it first with git remote rm origin, or use git remote set-url to change the URL of the existing remote.

Repo Init Fatal: error unknown url type

I am using repo to sync my local android source code. I have followed the instructions on the android source website: http://source.android.com/source/downloading.html
When I try to do repo init:
repo init -u http://android.googlesource.com/platform/manifest
I get the following error:
fatal: Cannot get http://gerrit.googlesource.com/git-repo/clone.bundle
fatal: error unknown url type: https
I have followed multiple threads on google and have modified my repo scripts and changed the https to http in the REPO_URL but I am continuing to get the same error.
What else do I need to do?
Please help.
Markus
I have answered my own question.
Since I last did a repo sync I had cleared my HTTP_PROXY and HTTPS_PROXY variables.
export HTTP_PROXY=http://<proxy_user_id>:<proxy_password>#<proxy_server>:<proxy_port>
export HTTPS_PROXY=http://<proxy_user_id>:<proxy_password>#<proxy_server>:<proxy_port>
Running this for my company settings fixed the problem.
Markus

Categories

Resources