-
Notifications
You must be signed in to change notification settings - Fork 445
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
Unexpected token U #31
Comments
@ritcoder this error seems normally happened at JSON.parse, which getting a parameter is undefined.
Thanks for your reporting. And I can't repo in my machine by now |
I checked The ending of the file was "www.bing.com":{"/":{"SRCHUID":{"key":"SRCHUID","value":"V=2&GUID=85BD4FE597F142D3A3D390D8330436C6","expires":"2018-08-19T11:39:50.000Z","domain":"www.bing.com","path":"/","hostOnly":true,"creation":"2016-08-19T11:39:50.778Z","lastAccessed":"2016-08-19T11:39:50.778Z" } } } }UIDB":{"key":"MUIDB","value":"1B8CFC8E99BA69BD33C2F5F898DC68BA", "expires":"2018-08-19T11:39:50.000Z","domain":"www.bing.com","path":"/","httpOnly":true, "hostOnly":true,"creation":"2016-08-19T11:39:50.780Z","lastAccessed":"2016-08-19T11:39:50.780Z"}}}} Everything got back to normal after deleting the invalid part of the json.
It is working now. Do you have any idea of what could have caused the invalid json to be written to the file? |
Cool. Now that I think about it, I was using it from two tabs. Anyway, will see if I can reproduce it and check with the next update. Thanks. |
@ritcoder I have published the new version 0.7.3 which fixes the bug, you can have a try. 😃 |
Following this [issue](mitsuru/tough-cookie-filestore#3), it seems like `tough-cookie-filestore` has concurrency issues when saving to the file system resulting in incorrect JSON serialization [(see here)](Huachao/vscode-restclient#31). I used this README as a reference on how to persist cookies and ran into this concurrency bug as I used `tough-cookie-filestore` instead of `tough-cookie-file-store`. I'm proposing this change to prevent future users looking for the same functionality from encountering the same issue.
Steps to Reproduce:
GET http://wwww.bing.com HTTP/1.1
Ctrl
-Alt
-R
I get the error above. I was working find just a few minutes ago so not sure what could be the case.
R.
The text was updated successfully, but these errors were encountered: