The worker runs just fine, but after it finishes I can not see all the debug info prints that I put in my code. Seems like it stops logging at a random point.....saw something about logging dropped if too verbose, could that be it?
#Logging stoppas at a random point
smoky hornet
dull elk
Im not sure about that, possibly could be but in my experience i log kind of alot too but i think most of em still get to the log when the worker's running
like when i start a process of something
dull elk
The worker runs just fine, but after it finishes I can not see all the debug inf...
If you need debug logs you can also like attach it to the response too so you can use them later
smoky hornet
Hmmm, but if the log is not saved I wonder if it helps to send it in response. How do you guys debug on runpod?
grand nacelle
Your logs do get dropped if your logging is too verbose so its definitely that if you're logging too much
dull elk
Hmmm, but if the log is not saved I wonder if it helps to send it in response. H...
saved? where do you want to save it? you can upload logs to s3 too ofc