Due to a non null terminated buffer being used in string stream. It corrupts the response and then can't be parsed into a valid json object.
Difficult to reproduce. I was only able to reproduce it in one specific project with one specific mixer user (testing other users and other projects worked fine). Not entirely sure why it happens so rarely, but it was reproducible on my end and this fixes it.
Due to a non null terminated buffer being used in string stream. It corrupts the response and then can't be parsed into a valid json object.
Difficult to reproduce. I was only able to reproduce it in one specific project with one specific mixer user (testing other users and other projects worked fine). Not entirely sure why it happens so rarely, but it was reproducible on my end and this fixes it.