Anton Whalley

Found the problem - The default time out for the thread is 120 seconds and the zip for 512M is taking longer than that. I've bumped the timeout to 600...

Thanks for the change. Can you apply the signoff for DCO please Instructions in this link. https://github.com/IBM/core-dump-handler/pull/114/checks?check_run_id=9292246336 I'll look to merge this over the weekend.

You've probably realized `error!` goes to std.err not std.out. Don't forget to sign it so the DCO passes. I want to get my patch to log4rs in the next release...

Hey @timbuchwaldt The test for timeout is failing now. Can you take a look when you have a minute.

Hi @asraro From the error message that looks like curl isn't parsing your command properly ``` curl: (6) Could not resolve host: application curl: (6) Could not resolve host: application...

Hi @leoterry-ulrica The version of node that you are using is No longer supported I would suggest upgrading to a supported version I.e. 6.x or above

Thanks for highlighting this. If you have time to PR this it would be great.

Hi @chzgustavo Thanks for the feedback really appreciate it. Do you have pods with the same name running in different namespaces? ### Background The information from crio is currently queried...

Sorry I'm not aware of another possible solution. Statefulsets intentionally label the pods with ordinal numbers https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#pod-identity. If you're using helm you can add the namespace to the statefulset name...

Hey @fresheneesz I would love for this to happen and I am not aware of it being discussed. It would be great if the core technical committee could share some...