streaming: forwards metadata and status failed

[flaky-bot]

Note: #355 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.

---

commit: 3717cd2f538dc2c885756094ada1f1ef2c20ddcc
buildURL: Build Status, Sponge
status: failed

Test output

Expected values to be strictly deep-equal:
+ actual - expected
{

code: 200,

details: '',

message: 'OK',


metadata: {


metadata: true



}

}

expected - actual

{

"code": 200

"details": ""

"message": "OK"

"metadata": {
"metadata": true
}

}



AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:


actual - expected
{

code: 200,

details: '',

message: 'OK',



metadata: {

metadata: true


}

}

at check (build/test/unit/streaming.js:197:24)

-> /workspace/test/unit/streaming.ts:238:16

at StreamProxy. (build/test/unit/streaming.js:205:13)

-> /workspace/test/unit/streaming.ts:247:7

at Timeout._onTimeout (build/test/unit/streaming.js:175:19)

-> /workspace/test/unit/streaming.ts:211:11

at listOnTimeout (internal/timers.js:554:17)

at processTimers (internal/timers.js:497:7)

[flaky-bot]

Looks like this issue is flaky. 😟

I'm going to leave this open and stop commenting.

A human should fix and close this.

---

When run at the same commit (3717cd2f538dc2c885756094ada1f1ef2c20ddcc), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

[alexander-fenster]

Closing this expecting some refactoring of the streaming processing code.