I did, because I know they weren’t relevant. They were part of Jellyfin itself and not the plugin. It’s just a warning saying that the query was slow (12ms). Since I wasn’t doing much on the server for the past few days, half the log was the warning (not an error).
So no, they weren’t part of the problem. I know they aren’t.
Davel23@kbin.social 1 year ago
Text editor or not, when you're asked for log files provide THE LOG FILES. Don't edit out lines you think are irrelevant. You don't know what's irrelevant or not. If you did, you could fix the problem yourself.
Rootiest@lemm.ee 1 year ago
Yeah this is one of my pretty peeves.
When I ask you for the logs I don’t mean cut out the one or two lines you might think are relevant.
Please provide the entire log file unless instructed otherwise.
I have no reason to believe the bits OP removed were relevant. In fact it sounds as though none of it was. But that’s not always the case and support people or the actual developers are just as capable of using the search function to locate the relevant parts of a log file as anyone else is.
Please provide the entire log, this “helping” concept causes now issues than it solves, trust.
Okalaydokalay@lemm.ee 1 year ago
This so much. I have so many users who include a screenshot and cut off parts of the screen. Sometimes the time is relevant, sometimes the URL is relevant, sometimes the web browser is relevant. I get if you have confidential stuff, you can block that out, but leave everything else in.
aksdb@feddit.de 1 year ago
Sorry, but log files can contain any amount of PII that is absolutely unsuited to be sent over an unencrypted channel to a person/company that should not even need some details.
I sure as hell also skim over logs before I send anything out and remove anything that I don’t want to leak.