Lilian Kasem

> @bhugot builds seem happy but I don't have permissions to trigger them. @liliankasem @brettsam could you please poke this build please? (or can we tweak perms on AppVeyor?) I...

@brettsam @mathewc Do we still have concerns about changing this behaviour?

Closing unless there is a strong case proposed for this change

@fabiocav @brettsam do we need to publish the 3.1.1 package or is it unlisted for a reason?

> @CooperLink following up on stale ope PRs here. If this requires additional validation/discussions, can you either flag as a draft or close and reopen when ready for a review?...

It doesn't look like any of the language workers are utilizing this in their worker.config files. The default value for `UseStdErrorStreamForErrorsOnly ` is false, meaning logs from **stderr** are written...

> That's great! If noone is writing all msgs to stderr stream then we can just switch the default to "true" and noone needs to make any changes. I'll wait...

I agree that we should encourage the right behaviour around logging these issue + improved error detection, but I also think that the right approach here is to log stderr...

Ahh that is very interesting and makes sense, thank you for sharing!

Have spoken to several language owners on this topic and it appears that this will be beneficial in catching issues that have been missed in our kusto logs. Will need...