vitalif / grive2

Google Drive client with support for new Drive REST API and partial sync
http://yourcmc.ru/wiki/Grive2
GNU General Public License v2.0
1.52k stars 140 forks source link

Exception: The complexity of matching the regular expression exceeded predefined bounds. #216

Closed sguazt closed 6 years ago

sguazt commented 6 years ago

Hello, With the last version of Grive2 I get the following error:

exception: The complexity of matching the regular expression exceeded predefined bounds.  Try refactoring the regular expression to make each choice made by the state machine unambiguous.  This exception is thrown to prevent "eternal" matches that take an indefinite period time to locate.

Version information:

My system is Fedora 28 x86_64 with GCC 8.1.1 and Boost 1.66.

Here below are the log files generated with: -l grive2_log --log-http grive2_http:

grive version 0.5.1-dev Jul 25 2018 22:36:34
current time: 2018-07-26T11:47:29.399Z
config file name "/home/[removed]/GDrive/.grive"
logging HTTP response: grive2_http2018-07-26.114729.txt
HTTP POST "https://accounts.google.com/o/oauth2/token"
HTTP response 200
exception: The complexity of matching the regular expression exceeded predefined bounds.  Try refactoring the regular expression to make each choice made by the state machine unambiguous.  This exception is thrown to prevent "eternal" matches that take an indefinite period time to locate.
HTTP/1.1 200 OK^M
Content-Type: application/json; charset=utf-8^M
X-Content-Type-Options: nosniff^M
Cache-Control: no-cache, no-store, max-age=0, must-revalidate^M
Pragma: no-cache^M
Expires: Mon, 01 Jan 1990 00:00:00 GMT^M
Date: Thu, 26 Jul 2018 11:47:30 GMT^M
Content-Disposition: attachment; filename="json.txt"; filename*=UTF-8''json.txt^M
Server: ESF^M
X-XSS-Protection: 1; mode=block^M
X-Frame-Options: SAMEORIGIN^M
Alt-Svc: quic=":443"; ma=2592000; v="44,43,39,35"^M
Accept-Ranges: none^M
Vary: Accept-Encoding^M
Transfer-Encoding: chunked^M
^M
{
  "access_token" : [removed],
  "expires_in" : 3600,
  "id_token" : [removed],
  "scope" : "https://www.googleapis.com/auth/docs https://www.googleapis.com/auth/userinfo.profile https://www.googleapis.com/auth/userinfo.email https://www.googleapis.com/auth/spreadsheets",
  "token_type" : "Bearer"
}
vitalif commented 6 years ago

Do you use a complex griveignore?

sguazt commented 6 years ago

No, I don't have this file. In my Google Drive folder, I have:

sguazt commented 6 years ago

I recompiled grive2 with the last updates (that is, the ones you committed after July 25) and it seems that this issue has gone. Thank you for your time.