Avoid logging an error when a player cache entry does not exist #6640
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Avoid logging an error when a player cache entry does not exist
Pull Request Type
Description
When a player cache entry doesn't exist, we currently log Node.js'
ENOENT
error, which just means "error no entry", which will occur every now and then, as the player IDs change when YouTube updates their player JavaScript. On various occasions users have seen these error messages and thought they meant that something was wrong, so lets not log them to avoid confusing users.Desktop