Skip to content

Error in storage - calling transform done when ws.length != 0 #805

Closed
Closed
Error in storage - calling transform done when ws.length != 0#805
Assignees
yoshi-automation
Labels
api: storageIssues related to the Cloud Storage API.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Description

@leibale
leibale
opened on Aug 17, 2015
/home/leibale/workspace/images-processor/node_modules/gcloud/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:204
    throw new Error('calling transform done when ws.length != 0');
          ^
Error: calling transform done when ws.length != 0
    at done (/home/leibale/workspace/images-processor/node_modules/gcloud/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:204:11)
    at DestroyableTransform.<anonymous> (/home/leibale/workspace/images-processor/node_modules/gcloud/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:139:7)
    at DestroyableTransform.g (events.js:199:16)
    at DestroyableTransform.emit (events.js:129:20)
    at DestroyableTransform.<anonymous> (/home/leibale/workspace/images-processor/node_modules/gcloud/node_modules/stream-forward/index.js:31:26)
    at DestroyableTransform.<anonymous> (/home/leibale/workspace/images-processor/node_modules/gcloud/node_modules/stream-forward/node_modules/on-everything/index.js:12:17)
    at DestroyableTransform.obj.(anonymous function) [as emit] (/home/leibale/workspace/images-processor/node_modules/gcloud/node_modules/stream-forward/node_modules/stubs/index.js:28:10)
    at finishMaybe (/home/leibale/workspace/images-processor/node_modules/gcloud/node_modules/retry-request/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:502:14)
    at endWritable (/home/leibale/workspace/images-processor/node_modules/gcloud/node_modules/retry-request/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:512:3)
    at DestroyableTransform.Writable.end (/home/leibale/workspace/images-processor/node_modules/gcloud/node_modules/retry-request/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:477:5)

i don't know the exact request- but it's from the storage

Activity

  1. stephenplusplus
    added
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    api: storageIssues related to the Cloud Storage API.
    on Aug 17, 2015

  2. stephenplusplus commented on Aug 17, 2015

    @stephenplusplus
    stephenplusplus
    on Aug 17, 2015
    Contributor

    Thanks for reporting. If you can zero in on one or more of your gcloud calls that consistently produces this, that would definitely help. But, generally speaking, our streams do need some safeguards to prevent again this.

  3. leibale commented on Aug 17, 2015

    @leibale
    leibale
    on Aug 17, 2015
    ContributorAuthor
    file.download({
  destination: path
}, function (err) {
// --
/});

    this is the request

  4. leibale commented on Aug 17, 2015

    @leibale
    leibale
    on Aug 17, 2015
    ContributorAuthor

    it's important so.. i will be happy if somebody help me
    sorry for my audacity

  5. stephenplusplus commented on Aug 17, 2015

    @stephenplusplus
    stephenplusplus
    on Aug 17, 2015
    Contributor

    Sure, we'll do our best. Your best option for now is probably to downgrade to v0.17.

  6. leibale commented on Aug 17, 2015

    @leibale
    leibale
    on Aug 17, 2015
    ContributorAuthor

    It also doesn't work

  7. stephenplusplus commented on Aug 17, 2015

    @stephenplusplus
    stephenplusplus
    on Aug 17, 2015
    Contributor

    Ok, roll back once more to 0.16 or the soonest you are able to make the request successfully.

  8. leibale commented on Aug 17, 2015

    @leibale
    leibale
    on Aug 17, 2015
    ContributorAuthor

    but in v0.16 the maxInProgress doesn't exist

    maybe it's happened after change in the server

    "On June 9th your project XXXXXXXX was affected by an incident which caused elevated error rates for 1 hour 40 minutes. You can read about the incident and the changes we have made to prevent re-occurrence at https://status.cloud.google.com/incident/storage/16025.

    We take such incidents seriously and are therefore issuing a credit under the terms of our Service Level Agreement (SLA) as defined at https://cloud.google.com/storage/sla. This credit will be equal to 10% of your June Google Cloud Storage bill. In this case, we will apply this credit to your account automatically, bypassing the normal SLA application procedure, so no action is required on your part.

    Yours,
    The Google Cloud Storage Team

    Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043

    You have received this mandatory service announcement to update you about important changes to Google Cloud Platform or your account.

    i got this in email from [email protected]

  9. stephenplusplus commented on Aug 17, 2015

    @stephenplusplus
    stephenplusplus
    on Aug 17, 2015
    Contributor

    Can you try removing the node_modules directory and re-installing gcloud? I updated the problematic dependency here: stephenplusplus/stream-forward@11ec2a7

  10. leibale commented on Aug 17, 2015

    @leibale
    leibale
    on Aug 17, 2015
    ContributorAuthor

    re-installing gcloud from github or from npm?

  11. stephenplusplus commented on Aug 17, 2015

    @stephenplusplus
    stephenplusplus
    on Aug 17, 2015
    Contributor

    From npm, it will automatically pick up the new stream-forward. Just make sure to rm -rf node_modules first. Updating is weird.

  12. leibale commented on Aug 17, 2015

    @leibale
    leibale
    on Aug 17, 2015
    ContributorAuthor

    now requests not returns (and i am in google vm so it's not internet problem)

  13. stephenplusplus commented on Aug 17, 2015

    @stephenplusplus
    stephenplusplus
    on Aug 17, 2015
    Contributor

    All requests aren't returning? Can you show more of the code you're using?

  14. leibale commented on Aug 17, 2015

    @leibale
    leibale
    on Aug 17, 2015
    ContributorAuthor

    pub/sub working

    file.download({
  destination: path
}, function (err) {
// --
/});

  15. 13 remaining items

  16. sofisl
    added 3 commits that reference this issue on Jan 27, 2026

    chore(deps): update actions/checkout action to v3 (#805)

    98e2aa8

    chore(deps): update actions/checkout action to v3 (#805)

    2127ea6

    chore(deps): update actions/checkout action to v3 (#805)

    ae214e0
  17. miguelvelezsa
    added a commit that references this issue on Jan 28, 2026

    test: add retry to import export flaky test (#805)

    41ff0f1
  18. sofisl
    added 3 commits that reference this issue on Jan 29, 2026

    chore(deps): update actions/checkout action to v3 (#805)

    4c9929d

    chore(deps): update actions/checkout action to v3 (#805)

    e15aa3b

    test: add retry to import export flaky test (#805)

    4389374
  19. sofisl
    added a commit that references this issue on Feb 17, 2026

    test: add retry to import export flaky test (#805)

    2c9e0a8
  20. sofisl
    added 3 commits that reference this issue on Feb 24, 2026

    feat!: convert Gapic client to TypeScript (#805)

    5649cee

    fix(deps): update dependency date-and-time to ^0.9.0 (#805)

    ee16b46

    fix(types)!: types for createInstance (#805)

    822277b
  21. GautamSharda
    added a commit that references this issue on Mar 5, 2026

    chore: update npm scripts and synth.py (#805)

    22f3f7d
  22. sofisl
    added a commit that references this issue on Mar 5, 2026

    build(auth): add token handler for GoogleToken. (#805)

    24a7e38
  23. GautamSharda
    added a commit that references this issue on Mar 12, 2026

    chore(deps): update dependency @types/tmp to v0.2.6 (#805)

    43c495b
  24. thiyaguk09
    added a commit that references this issue on Mar 18, 2026

    fix(deps): update dependency date-and-time to ^0.9.0 (googleapis#805)

    54f6b38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

api: storageIssues related to the Cloud Storage API.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