Skip to content

Git Troubleshooting Issues

Overview

This section describes some git issues and the steps that can be followed to resolve those issues.

Cannot push changes to the remote topic branch

You may get one of the below errors when you try to push a large amount of changes to a remote topic branch. This can happen when pushing large amount of changes using a bad network connection. Try using a better network connection to get rid of this error.

$ git push origin topic/ifs/SUUPD-2-Service_Update_21_2_3

error: RPC failed; HTTP 413 curl 22 The requested URL returned error: 413 send-pack: unexpected disconnect while reading sideband packet fatal: the remote end hung up unexpectedly Everything up-to-date

$ git push origin topic/ifs/SUUPD-2-Service_Update_21_2_3

error: RPC failed; HTTP 503 curl 22 The requested URL returned error: 503 send-pack: unexpected disconnect while reading sideband packet fatal: the remote end hung up unexpectedly Everything up-to-date

Cloning the Entire Repository is Time Consuming

During the process of applying the Release Update to the Customer Solution repository, you are not required to clone the repository each time a customization development is done. The repository which is already cloned can be used by following the steps mentioned in If the cloned customer-solution repository does not exist locally on the machine.

Else, another approach that can be followed is cloning the branch alone. If the need arise to only work in a specific topic branch, is it possible to clone only that branch. Ensure that the topic branch of the customer-solution repository created during the Customization Upliftment Preparation step is used for this purpose, as it contains the new release version updated in the version.txt file. The following git command can be used for this purpose:

git clone --branch <topic-branch-name> --depth 1 <customer-solution-repo-url>

However, there are a few limitations with this approach:

  1. You will be unable to checkout to other branches that exist in the remote repository.

  2. You will be unable to pull changes that exist in other branches of the remote repository.