Comment

That’s not helpful, these are developers… even if you think those lines are useless they can inform the code-path the devs need to trace through or help them understand why you’re facing this issue.

source

Sort:hotnew top

CeeBee@lemmy.world ⁨1⁩ ⁨year⁩ ago
I know how debugging works. I’ve been a developer for a couple decades.

I know for a fact that the lines I removed are normal verbose messages and entirely unrelated to my issue. I know not only because I’m a developer and understand the messages, but also because those lines show up every second of every minute of every day. They are some of the most verbose lines in the logs. The scheduled task for the subtitles only runs once a day and finishes within a few minutes.

Also, they weren’t indicative of any code path because of how frequent they were. At such a high frequency it becomes impossible to determine which line came first in multi-threaded or asynchronous tasks.

source
- IAm_A_Complete_Idiot@sh.itjust.works ⁨1⁩ ⁨year⁩ ago
  The last bit isn’t strictly true - there’s ways to trace such tasks by generating IDs and associating it per task / request / whatever, letting you associate messages together even in a concurrent environment. You can’t just blindly print but there’s libraries and the like to help you do it.
  
  source
  - CeeBee@lemmy.world ⁨1⁩ ⁨year⁩ ago
    I know, but that’s not the case here.
    
    source