This is part three of our Git Error Codes series. You can see all the topic in the series below…
- Git Error Codes - Definitions & Solutions (Part 1)
- Git Error Codes - Definitions & Solutions (Part 2)
- Git Error Codes - Definitions & Solutions (Part 3) → We’re here
- Git Error Codes - Definitions & Solutions (Part 4)
The error codes in this topic include:
Illegal character in schema name at index → This post
Git clone “Filename too long”
git-upload-pack Not Found
Today we will take a look at the Illegal character in schema name at index
Definition
There is some special character such as # @ in the git URL so TestOps could not detect the correct repo on it
Stage
Integration
Root Cause
You are using the invalid git URL to connect with TestOps
Solution
You can follow this guide.
1 Like
Today we will look at the error Git clone “Filename too long”
Definition
When doing a git clone from remote repositories during Runtime Engine or TestOps execution, the problem “Filename too long” occurs.
Stage
Execution
Root Cause
Git is compiled using MSYS. It utilizes an earlier version of the Windows API, therefore filenames are limited to 260 characters.
Solution
Run “git config --system core.longpaths true” as admin to fix the error in 3 ways:
- Git Global Level
- Git-specific Project
- Git Clone Command
For more information, visit this article on our Help Center
1 Like
Today we’ll take a look at the error: git-upload-pack Not Found
Definition
TestOps cannot detect the Git Repo to connect as the URL does not exist.
Stage
Integration
Root Cause
You have inputted an incorrect Git Repo URL.
Solution
- Access the URL to make sure if it’s existed.
- Paste the correct URL into the Repository URL field.
