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

The YouTube operational API may generate warnings while providing the correct output #23

Open
Benjamin-Loison opened this issue Sep 4, 2022 · 5 comments
Labels
enhancement New feature or request epic A task that is going to take more than a day to complete. medium priority A high-priority issue noticeable by the user but he can still work around it.

Comments

@Benjamin-Loison
Copy link
Owner

Benjamin-Loison commented Sep 4, 2022

The API was initially badly designed by ignoring warnings.

Note that this StackOverflow answer removes the warnings displayed when fetching a YouTube operational API endpoint.

Once done, having done #24 would help to make sure that this issue is completely solved.

@Benjamin-Loison Benjamin-Loison added the enhancement New feature or request label Sep 4, 2022
@Benjamin-Loison Benjamin-Loison added epic A task that is going to take more than a day to complete. medium priority A high-priority issue noticeable by the user but he can still work around it. labels Oct 19, 2022
@Benjamin-Loison
Copy link
Owner Author

As reduced the error logs (cf #18), should reconsider this by for instance looking at official instance error logs.

@Benjamin-Loison
Copy link
Owner Author

Could add a notification system if an error happen, as none should happen.

@Benjamin-Loison
Copy link
Owner Author

Benjamin-Loison commented Nov 11, 2022

As described in #48, proceeded at 11:40 PM UTC+1 to logrotate --force /etc/logrotate.d/apache2.

Can filter the interesting errors by using:

grep -vE 'icon|429|robots' yt.lemnoslife.com-ssl--error.log

Should verify that 429 Too many requests can't be solved with a captcha, as I had the feeling last time I saw the error. Related to #11.

@Benjamin-Loison
Copy link
Owner Author

Temporarily I should propose instructions to hide these warnings from end-user perspective.

If I remember correctly WampServer on Windows show by default these errors and Mac OS seems to too.

As a first step knowing how to add these warnings on apache2 on Linux may help to propose the final solution.

Benjamin-Loison added a commit that referenced this issue Jan 4, 2023
…g the correct output

Add a temporary patch to disable displaying PHP warnings (notably in
WampServer).
Benjamin-Loison added a commit that referenced this issue Feb 1, 2023
@Benjamin-Loison
Copy link
Owner Author

Benjamin-Loison commented Feb 8, 2023

On nginx

commentThreads?part=snippet,replies&pageToken=4qmFsgLJAhIYVUNXZWcyUGthdGU2OU5GZEJldVJGVEF3GqwCRWdsamIyMXRkVzVwZEhuS0FTZXlBU1JWWjJ0NFdXbEZRVzg1TFdJeGRsZFFZWE40Um5reE0yWTVOVGx5Y21OMFVYQmFkMWZxQWdRUUFSZ0JxZ09jQVJwcEVocFZaM3BLYmtoVWEzUnlTRlEzV1ZKUExVZHdORUZoUVVKQlp5SUNDQUFxR0ZWRFYyVm5NbEJyWVhSbE5qbE9SbVJDWlhWU1JsUkJkMEFCU0FwNkpGVm5hM2haYVVWQmJ6a3RZakYyVjFCaGMzaEdlVEV6WmprMU9YSnlZM1JSY0ZwM1Y0SUJBZ2dDUWk5amIyMXRaVzUwTFhKbGNHeHBaWE10YVhSbGJTMVZaM3BLYmtoVWEzUnlTRlEzV1ZKUExVZHdORUZoUVVKQlp3JTNEJTNE

errors are such that we need to modify nginx.conf to keep it running correctly (in fact I multiplied by two these values, as I suffered another crash by just applying Stack Overflow answer, let's give instead a try to proxy_buffering off; as we're giving shots in the dark, as still have the issue I'm trying to disable PHP notices which seem to spam logs otherwise, it seems to do the job, at least it did for @LofiGirl).

Reproduce this problem quickly by using YouTube captions search engine with removing everything performed by this while loop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request epic A task that is going to take more than a day to complete. medium priority A high-priority issue noticeable by the user but he can still work around it.
Projects
None yet
Development

No branches or pull requests

1 participant