Skip to content
This repository was archived by the owner on Mar 19, 2026. It is now read-only.
This repository was archived by the owner on Mar 19, 2026. It is now read-only.

streaming: emit response when stream received metadata event failed #260

Closed

Description

@flaky-bot

This test failed!

To configure my behavior, see the Flaky Bot documentation.

If I'm commenting on this issue too often, add the flakybot: quiet label and
I will stop commenting.


commit: 324ff49fe059e1453bf751247e07e460d11c281a
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:311:24)
    -> /workspace/test/unit/streaming.ts:363:16
    at StreamProxy. (build/test/unit/streaming.js:324:13)
    -> /workspace/test/unit/streaming.ts:377:7
    at Immediate._onImmediate (build/test/unit/streaming.js:289:19)
    -> /workspace/test/unit/streaming.ts:334:11
    at processImmediate (internal/timers.js:461:21)

Activity

  1. added
    flakybot: issueAn issue filed by the Flaky Bot. Should not be added manually.
    priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    flakybot: flakyTells the Flaky Bot not to close or comment on this issue.
    on Dec 25, 2022
  2. flaky-bot commented on Dec 26, 2022

    @flaky-bot
    Author

    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 (324ff49fe059e1453bf751247e07e460d11c281a), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

  3. bcoe commented on Jan 3, 2023

    @bcoe

    Last 8 builds are green, closing.

  4. added
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.
    flakybot: issueAn issue filed by the Flaky Bot. Should not be added manually.
    flakybot: flakyTells the Flaky Bot not to close or comment on this issue.
    on Nov 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    flakybot: flakyTells the Flaky Bot not to close or comment on this issue.flakybot: issueAn issue filed by the Flaky Bot. Should not be added manually.priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions