Handle status code Uncertain according to the specification

[larws]

Proposed changes

If a method call returns Uncertain as a status code the output arguments values should be set as specified in the specification.

Related Issues

• Fixes MethodState Call method does not assign output arguments when status Uncertain is returned #2896

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply. You can also fill these out after creating the PR.

• Bugfix (non-breaking change which fixes an issue)
• Enhancement (non-breaking change which adds functionality)
• Test enhancement (non-breaking change to increase test coverage)
• Breaking change (fix or feature that would cause existing functionality to not work as expected, requires version increase of Nuget packages)
• Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc.
• I have signed the CLA.
• I ran tests locally with my changes, all passed.
• I fixed all failing tests in the CI pipelines.
• I fixed all introduced issues with CodeQL and LGTM.
• I have added tests that prove my fix is effective or that my feature works and increased code coverage.
• I have added necessary documentation (if appropriate).
• Any dependent changes have been merged and published in downstream modules.

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

[CLAassistant]

All committers have signed the CLA.

[codecov]

Codecov Report

Attention: Patch coverage is 75.00000% with 2 lines in your changes missing coverage. Please review.

Project coverage is 55.44%. Comparing base (0777bbd) to head (951beb2).
Report is 4 commits behind head on master.

Files with missing lines	Patch %	Lines
Stack/Opc.Ua.Core/Types/Utils/ServiceResult.cs	33.33%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2898   +/-   ##
=======================================
  Coverage   55.43%   55.44%           
=======================================
  Files         352      352           
  Lines       67602    67605    +3     
  Branches    13849    13851    +2     
=======================================
+ Hits        37477    37483    +6     
  Misses      26021    26021           
+ Partials     4104     4101    -3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[romanett]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mregen]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@larws please sign the contributor agreement

[larws]

@mregen, @mrsuciu do you happen to know if there is any chance that this fix will end up in the next release? If it won't what would be a realistic release date?

[mrsuciu]

@mregen, @mrsuciu do you happen to know if there is any chance that this fix will end up in the next release? If it won't what would be a realistic release date?

@larws Yes it will end up in the next release which will be most probably sometime at the beginning of next year