Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid UTF8 character #99

Open
canasdiaz opened this issue Dec 9, 2015 · 3 comments
Open

Invalid UTF8 character #99

canasdiaz opened this issue Dec 9, 2015 · 3 comments

Comments

@canasdiaz
Copy link
Member

Parsing log for /home/joomla/dashboards/joomla/scm/utilities (git)
/usr/local/lib/python2.7/dist-packages/cvsanaly2-2.1.0-py2.7.egg/pycvsanaly2/DBTempLog.py:133: Warning: Invalid utf8 character string: '800228'
  commits)
/usr/local/lib/python2.7/dist-packages/cvsanaly2-2.1.0-py2.7.egg/pycvsanaly2/DBTempLog.py:143: Warning: Invalid utf8 character string: '800228'
  statement("INSERT into _temp_log (rev, date, object) values (?, ?, ?)", self.db.place_holder), commits)
Executing extensions
Executing extension FileTypes
Executing extension CommitsLOC
[2015-11-27 04:25:57] /usr/local/bin/cvsanaly2 -u root -p '' -d jalonso_cvsanaly_joomla_6925 --extensions=CommitsLOC,FileTypes >> /home/joomla/dashboards/joomla//log/launch_cvsanaly.log 2>&1
@sduenas
Copy link
Member

sduenas commented Dec 14, 2015

In order to reproduce the error, I need to know which is the repository that you are analyzing.

@bvasiles
Copy link

bvasiles commented Dec 13, 2016

The Invalid utf8 character string: '800228' warning happens when analyzing CVSAnalY's repository.

@jorgechollet
Copy link

jorgechollet commented Sep 20, 2018

In DBTempLog.py, both INSERT statements on table _temp_log may need the keyword "_binary" before the third placeholder inside "values".

For example, current statement:
"INSERT into _temp_log (rev, date, object) values (?, ?, ?)"

May need to be changed to:
"INSERT into _temp_log (rev, date, object) values (?, ?, _binary ?)"

I made the change in both INSERT statements and I don't see the error message anymore. Not sure if this is the best way to solve this.

I got this from here: https://bugs.mysql.com/bug.php?id=79317

Cheers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants