Remove default JSON size limitation

[dhermanconsulting]

SUMMARY

Change allows JavaScriptSerializer to deserialize the largest possible JSON file. Otherwise large log files from chatty PowerShell scripts will exceed the default limit of 4MB and throw an exception.

No such limitation exists on async_status.py, so this brings the PowerShell script better in line with that

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

async_status.ps1

ADDITIONAL INFORMATION

If an async tasks output exceeds 4MB (The default size limit for System.Web.Script.Serialization.JavaScriptSerializer), the deserialization will fail, throwing an exception and failing the async task.

The limit is arbitrary, and is implemented by a simple integer value that the file length is compared against. There is no practical upper limit, except for system resources.

Microsoft documentation: https://learn.microsoft.com/en-us/dotnet/api/system.web.script.serialization.javascriptserializer.maxjsonlength?

Microsoft source code: https://referencesource.microsoft.com/#system.web.extensions/Script/Serialization/JavaScriptSerializer.cs

I can see no reason to maintain a hard limitation. The python equivalent of this module (async_status.py) uses Python's json library, which has no built-in hard limitation.

[jborean93]

Thanks for the fix, I've added a changelog fragment and integration test for this particular scenario.