#1998 [Core feature] No stacktraces Issue created by sonjaer Motivation: Why do you think this is important? I find it hard to debug/understand where these logged errors comes from without a stacktrace

json: {
exec_id: "cz7vntanluzg2fck4yim"
src: "protobuf_store.go:77"
}
level: "error"
msg: "Failed to write to the raw store [<gs://flyte-production-storage/metadata/payment-risk-datasets/production/cz7vntanluzg2fck4yim/inputs>] Error: Failed to write data [172b] to path [metadata/payment-risk-datasets/production/cz7vntanluzg2fck4yim/inputs].: googleapi: Error 409: The metadata for object "metadata/payment-risk-datasets/production/cz7vntanluzg2fck4yim/inputs" was edited during the operation. Please try again., conflict"
ts: "2021-12-27T05:33:19Z"

json: {
exec_id: "so5a7vr6wrndjvk7h3g7"
node: "ffum5wni"
src: "node_execution_manager.go:120"
}
level: "error"
msg: "failed to fetch node execution for the parent node: project:"daily-sessions" domain:"production" name:"so5a7vr6wrndjvk7h3g7"  fivcmqky with err%!(EXTRA *errors.flyteAdminErrorImpl=unexpected error type for: dial tcp 10.201.108.5:5432: connect: connection refused)"
ts: "2021-12-28T02:21:24Z"

``` I am not very familiar with Go but it would be great to see a stacktrace being logged. Goal: What should the final outcome look like, ideally? Stacktrace when logging the error Describe alternatives you've considered None Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#1998 [Core feature] No stacktraces Issue closed as not planned by github-actions[bot] flyteorg/flyte