Git not committing, gpg stuck in database_open waiting for lock

When I attempt to commit in Git through R, I continuously get revoked access.

The error is:

gpg: Note: database_open 134217901 waiting for lock (held by 9857) ..

1. I have pushed.
2. I have pulled.
3. I have set a new token.
4. I have cloned the project.

I'm expecting the commit to send but I'm getting the full error:

gpg: Note: database_open 134217901 waiting for lock (held by 9857) ... [GNUPG:] FAILURE sign 134250628 gpg: signing failed: Operation timed out

I'm attempting to commit a R script to GitHub through R. When I use the commit option through the panel, it will not push. I have tried to reset my credentials, put a new personal token on, and other tactics. It is not working. Not sure where to go from here. I'm expecting for the code to enter the repo and it is not.

I am stuck in a loop:

--list-keys
gpg: Note: database_open 134217901 waiting for lock (held by 9857) ...
gpg: Note: database_open 134217901 waiting for lock (held by 9857) ...
gpg: Note: database_open 134217901 waiting for lock (held by 9857) ...
gpg: Note: database_open 134217901 waiting for lock (held by 9857) ...
gpg: Note: database_open 134217901 waiting for lock (held by 9857) ...

Figured out the problem. Thanks to anyone who has taken a look. There appeared to be a merge problem and a local gpg on the file that was not needed. Removed the gpg signature and this fixed the issue.

For anyone who needs the solution:

git config --unset commit.gpgsign
git config --unset user.signingkey
git config --global commit.gpgsign false

Found another work around that allows for a permanent fix, you want to dig out the file and remove the GPG lock issues: Git Commit Freeze Due to GPG Lock Issue