-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
[xhamster] No video format found again with patch #26254 and possible workaround #26353
Comments
Hi, i checked my xhamster.py and could not find any reference of window.initials to fix the problem ! I am on UBUNTU 18.04 LTS ! |
Hi hitam4450. It's line 141 in the latest xhamster.py. Some changes have been made here in the last weeks. Search in the line range 130-150. Search for the block in the def _real_extract(self, url): |
This i found on line 117 r'window.initials\s*=\s*({.+?})\s*;\s*\n', webpage, 'initials', |
line 115 to 123 |
Yes that is the line without patch #26254. |
I applied the patch..but NO Success! |
Do you have the no video format found OR the unsupported url error. |
Seems to have really been a temporary problem. I just messed up with the original xhamster.py and it's working again for now. |
I applied the patch..but NO Success! |
Maybe you have another problem. I think it will be best if you open a new issue with your own log. |
Today the error occurs again. If there are more cases, maybe a patch should be written. WARNING: [XHamster] xhJqAVs: Failed to parse JSON Unterminated string starting at: line 1 column 21345 (char 21344) Abort of the script with error. With the above mentioned workaround it works again. |
Checklist
Verbose log
Description
I noticed a problem again with the RegEx for the site initials. As it looks like the web server has problems to deliver the line completely. On the other hand, the character ; appears more often in the line now. Maybe just a temporary problem.
Workaround:
I changed the line 141 of the xhamster.py from:
r'window.initials\s*=\s*({.+?})\s*;', webpage, 'initials',
to
r'window.initials\s*=\s*({.+?})\s*;<', webpage, 'initials',
But this time it is really only a workaround. I think it would be better to adjust the regular expression to parse everything from <script id='initials-script'> to the next </script> and not to use the ; character at the end of the regex.
The text was updated successfully, but these errors were encountered: