Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

unable to parse commit because commit message contains ASCII delimiter characters

See original GitHub issue

Description

When I open GitHub Desktop this error appears and keeps popping up:

screenshot 2019-02-13 at 10 19 36

The second part of the error message is a partial of a commit comment. The full commit looks like this:

commit <COMMIT_SHA>
Author: <Author Name> <HiddenName@users.noreply.github.com>
Date:   Fri Feb 8 14:50:24 2019 +0100

    Set queue_sid based on looked up queue (#546)

    Set queue_sid based on looked up queue
    Params sent by Twilio differ from usecase to usecase, so we need to make sure that a `^]queue_sid`^_ is always set, no matter how the call ended up in the queue.

This error also pops up whenever I click on the History tab or change the Mac OS Desktop to the one where GitHub Desktop is open.

Version

GitHub Desktop: 1.6.1

Operating system: Mac OS 10.14.2

Steps to Reproduce

I tried to reproduce it but this seems to only happen if another author commits with these characters in the commit message. Reproducing it locally wasn’t possible for me. Since this is a private repo I cannot share it with you.

Expected Behavior

No error message.

Actual Behavior

Error message keeps popping up.

Additional Information

Logs

Issue Analytics

State:
Created 5 years ago
Reactions:3
Comments:16 (10 by maintainers)

Top GitHub Comments

1reaction

muhammadahmadsaeedcommented, Sep 15, 2020

Because of this popup, I am unable to use github desktop. Other git clients work fine though.

1reaction

wrzwickycommented, Nov 29, 2019

Hello? Anyone here? Any plans to fix this? As was pointed out above, you’re parsing the string incorrectly, Can I trouble you to possibly parse it correctly?

I hate to play grumpy old man here, but you’re parsing a string I don’t control, from a file I don’t control, and you’re doing it wrong. I can’t even guess at how to work around such a thing, much less fix it.

Top Results From Across the Web

GitLogParser fails if commit message contains some special ...

GitLogParser fails if commit message contains some special ascii control characters. 2. Relates to 1 Is duplicated by 1. Relates to 1 issue...

Windows shared runners fail when processing commit messages ...

Summary Writing a commit message containing non-ASCII UTF-8 characters and then ... The cause appears to be an attempt to parse the commit...

How can I solve ORA-00911: invalid character error?

The statement you're executing is valid. The error seems to mean that Toad is including the trailing semicolon as part of the command,...

git-show Documentation - Git

Commit objects record the character encoding used for the log message in their encoding ... Options are parsed in the order given on...

Supported hooks - pre-commit

pretty-format-json - sets a standard for formatting json files. check-merge-conflict - checks for files that contain merge conflict strings. check-symlinks - ...