Fabio Cavalcante
Fabio Cavalcante
@jviau and @liliankasem thank you for the review on this! Had a sync with @mgravell this morning and since there's urgency to get this work in to align with validation...
As @ankitkumarr mentioned, this is a configuration setup issue, but the goo news is that there's a clear workaround. While the problem is not resolved, please add the following to...
@CasperWSchmidt I'm assuming you mean Functions V3 above, correct? Have you tried to move to 3.0 and remove the workaround?
@fabioleardini this is an old issue and I want to make sure what's described here applies to you. Would you be able to share your setup details and, ideally, a...
This has a dependency on https://github.com/Azure/azure-functions-language-worker-protobuf/pull/69 and we won't be able to complete the changes here until that work is merged.
This issue is unblocked now that @gavin-aguiar's PR has been merged. Moving to sprint 124 to track the completion of the remaining work.
@soninaren had to work on changes that will ensure the properties are populated as expected, but validation and tests will still be required for this issue.
@mgravell apologies for the delay on this. We'll get eyes on this ASAP. Would it be possible to have this rebased to deal with the conflicts? Thanks!
@mgravell indeed, this is high priority on our side, so whatever we can do to help, please let us know.
Thanks, @NickCraver. Good to have this merged once conflicts are resolved.