Today, when switching to the main branch on the branch, a fatal: unable to create’d]/xxxxx /. Git/index. Lock ‘: file exists. Error occurred. Please record it here for future reference
The solution is: execute RM – f operation to switch to the main branch
The specific command is: RM – F D/XXXXXX /. Git/index. Lock
/usr/local/lib64/libcrypto.a(dso_dlfcn.o): In function `dlfcn_globallookup’:
dso_dlfcn.c:(.text+0x30): undefined reference to `dlopen’
dso_dlfcn.c:(.text+0x43): undefined reference to `dlsym’
dso_dlfcn.c:(.text+0x4e): undefined reference to `dlclose’
/usr/local/lib64/libcrypto.a(dso_dlfcn.o): In function `dlfcn_pathbyaddr’:
dso_dlfcn.c:(.text+0x9d): undefined reference to `dladdr’
dso_dlfcn.c:(.text+0xf9): undefined reference to `dlerror’
/usr/local/lib64/libcrypto.a(dso_dlfcn.o): In function `dlfcn_bind_func’:
dso_dlfcn.c:(.text+0x434): undefined reference to `dlsym’
dso_dlfcn.c:(.text+0x4de): undefined reference to `dlerror’
/usr/local/lib64/libcrypto.a(dso_dlfcn.o): In function `dlfcn_bind_var’:
dso_dlfcn.c:(.text+0x554): undefined reference to `dlsym’
dso_dlfcn.c:(.text+0x5fe): undefined reference to `dlerror’
/usr/local/lib64/libcrypto.a(dso_dlfcn.o): In function `dlfcn_unload’:
dso_dlfcn.c:(.text+0x65d): undefined reference to `dlclose’
/usr/local/lib64/libcrypto.a(dso_dlfcn.o): In function `dlfcn_load’:
dso_dlfcn.c:(.text+0x712): undefined reference to `dlopen’
dso_dlfcn.c:(.text+0x77b): undefined reference to `dlclose’
dso_dlfcn.c:(.text+0x7a8): undefined reference to `dlerror’
collect2: ld returned 1 exit status
make: *** [git-imap-send] Error 1
Open the Makefile directory, search for crypto, and add -ldl in front of it
ifdef NEEDS_SSL_WITH_CRYPTO
LIB_4_CRYPTO = $(OPENSSL_LINK) -ldl -lcrypto -lssl
else
LIB_4_CRYPTO = $(OPENSSL_LINK) -ldl -lcrypto
endif
Push to remote warehouse
git push -u origin masterThe following error occurred
! [rejected] master -> master (fetch first)
error: failed to push some refs to '[email protected]:qiyuebuku/WxRobot.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.The solution is to connect the changes of the local warehouse to the main branch of the remote warehouse before pushing to the remote server
git pull origin master
git push -u origin master //Push files from local repository to remote repository wenDone!
Today, I modified part of the project, and then used git push origin master to push it to the remote warehouse. The following error was reported:
error: failed to push some refs to 'https://github.com/ZJyoung1997/JZShop.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
The reason is that the files in the remote warehouse are different from our local warehouse. For example, your remote warehouse has a file readme. MD, but the local warehouse does not. This may happen. My problem is that there is a readme. MD file in the remote warehouse, but there is no such file in the local warehouse. Another reason is that usually in the association, we use the association’s computer to develop, and when we go back to the dormitory, we will use our own computer to develop. This may also be the reason for this problem. There is a solution to this situation, which is to kill the local warehouse directly, and then clone one from the remote, but this is obviously too cumbersome, you can use the method of merging branches
terms of settlement:
git pull --rebase origin master
Git pull command is used to obtain and integrate (consolidate) from another repository or local branch, retrieve the update of a branch of the remote host, and then merge with the local specified branch.
If the following error is reported, you can also use the git pull command
fatal: 'master' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
use git pull origin master --allow-unrelated-histories to fix
Record a git push error solution, rarely encountered, but forget how to solve it…
error: RPC failed; HTTP 403 curl 22 The requested URL returned error: 403
reason:
There is only one reason I have encountered here, that is, the password of GIT account is set to be remembered permanently, and then this problem is easy to occur when switching users, because the account password has changed
Solution:
Modify git configuration file . git/config As shown in the figure:
vim .git/config
Add the URL to the // After adding your user name and @ character;
When submitting again, the account password input box will pop up. After input, you can operate normally
I’m dizzy. I don’t know how this problem happened today
git config --global http.proxy http://127.0.0.1:1080
git config --global https.proxy http://127.0.0.1:1080The problem has been solved
Cancellation of agency
Cancel global proxy.
git config --global --unset http.proxy
git config --global --unset https.proxyI can’t remember how many times I’ve dealt with this kind of problem
failed to connect to github.com port 443
Solution: first switch the child to the global, then cancel, then cancel the global agent, and finally git pull or git push
What is the cause of the problem?
After many years (15:19:34, March 15, 2021), we encountered this problem again
(1) Cancellation of agency
git config –global –unset http.proxy
git config –global –unset https.proxy
(2) Success!
Contents of articles
Android studio git error reporting and Solutions
Pcharm git push error and solution push failed: unable to access’ https://github.com/BierOne/bottom-up-attention-vqa.git/ ‘: Could not resolve host: github.comPush failed Invocation failed Server returned invalid Response. Authentication failed for
Reference link
Android studio git error reporting and Solutions
after all, Android studio and pychar are the same family. However, there are many solutions to as found on the Internet. Here is a brief introduction</ mark>
Invocation failed Unexpected Response from Server: Unauthorized
resolvent:
AndroidStudio -> Preferences -> Git -> SSH Executable and changed from Native to Built-in and it started working.
Reason: SSH key pair protects the password. If you select native SSH executable, the as will not prompt you to enter the password, so the final authentication will fail. However, if build in is set, you will be prompted to enter the password, so the authentication is successful.
Pychar git push error report and solution
Push failed: Unable to access ‘ https://github.com/BierOne/bottom-up-attention-vqa.git/ ’: Could not resolve host: github.com
Solutions and reasons:
This error is obviously caused by network problems. It is recommended to connect to the network again. Generally, the avatar can be displayed normally at this position, that is, there is no problem with the network
Push failed Invocation failed Server returned invalid Response. Authentication failed for
Solution and reason: because there is no build in option in my pychar, the as method is not applicable. My solution is to check “use confidential helper” in the GIT column, which is the authentication assistant:
in this way, you will be prompted to enter your password during authentication, and you can pass the authentication normally. There are other solutions, but they are similar.
In addition, you can also try to use token when adding GitHub account. It should be done once and for all
In the settings page of the GitHub official website account, select create new token, and then copy it
I have a little problem today. Come here to share and record:
To solve the problem of authentication failed for ‘http:// * * *. Git’ in the pull project times, let’s share two solutions:
In the case of GIT permission and account password, the reason for this problem is the wrong user name and password
Solution 1:
reset the user name and password as follows:
Set Username
git config --global user.name test1
Set Password
git config --global user.password 123456
After setting, you can use git clone command or git fetch command to pull the project again.
Solution 2:
1) input the following command
git config --system --unset credential.helper
2) Pull the project through git clone or git fetch command, and re-enter the user name and password to successfully pull the project.
|–question
git clone Downloading a repository gives a warning that no related code is being generated
warning: The remote HEAD points to a reference that does not exist and cannot be detected.
warning: remote HEAD refers to nonexistent ref, unable to checkout.
|–solution
The .git directory .git/refs/heads does not have a file pointed to by HEAD
git branch -a
git checkout remotes/origin/Zoro
At this point, there is code in the project directory
git branch
prompt
(the header pointer is separated from origin/Zoro)
git checkout -b remotes/origin/Zoro
Switch to a new branch ‘remotes/origin/Zoro’
* remotes/origin/Zoro
create head
git branch -m remotes/origin/Zoro master
* master Switch to master branch
git branch -a
* master
remotes/origin/Zoro
attention：git help branch(command name) View help
In windows, the new line character is CRLF, while in Linux, the new line character is lf . The prompt: warning : LF will be replaced by CRLF in README . md . The file will have its original line endings in ；
$ git add .
warning: LF will be replaced by CRLF in text 1/README.md.
The file will have its original line endings in your working directory.
warning: LF will be replaced by CRLF in text 2/README.md.
The file will have its original line endings in your working directory.Settings core.autocrlf=true Post: when checking out, GIT will convert the newline character of the text file to CRLF (only convert the pure lf file). When submitting, GIT will convert the contents of the temporary storage area (that is, the changes we made to the workspace) to LF, and then put it into the version library. When converting the contents of the temporary storage, lf will be converted to CRLF if lf newline character is found in it, and a very important sentence is given below the warning: “LF will be replaced by CRLF”: warning: LF will be replaced by CRLF in.
the file will have its original line endings in your working In the workspace, this file will keep its original newline character
Simply put, set core.autocrlf=true After that, the files in our workspace should be wrapped with CRLF. If LF is introduced when the file is changed, or if the core.autocrlf Previously, the workspace already had lf newlines. When you submit changes, GIT will warn you which files are not pure CRLF files, but git will not modify those files in the workspace without authorization, but modify the temporary storage area (our changes to the workspace).
Direct setting core.autocrlf=false ；
Except Notepad editor, everything else is OK
git config -–global core.autocrlf false // Disable automatic conversion
git rm -rf cached . // Clear the cache added to the cache
git add .
git commit -m "Commit the notes"
git push origin master // Push to remote repository