Skip to content

2.3.1 broke vinyl-fs test suite #296

Closed

Description

@phated

I'm digging into this now but this is the only dependency that changed. Every now-failing test have to do with error handling, any thoughts off the top of your head?

Activity

  1. mcollina commented on Jun 21, 2017

    @mcollina
    SponsorMember

    2.3.0 is working fine?

  2. phated commented on Jun 21, 2017

    @phated
    Author

    Probably not, we had 2.2.11 in our last successful run.

  3. mcollina commented on Jun 21, 2017

    @mcollina
    SponsorMember

    If 2.3.0 have the same behavior, it might be nodejs/node#13850.

  4. phated commented on Jun 21, 2017

    @phated
    Author

    Just tested with 2.3.0 and the tests fail, so it looks like that is the breaking version. We are seeing as a transitive issue from our through2 dependency. How can we go about fixing it? Or does it need to be solved here?

  5. phated commented on Jun 21, 2017

    @phated
    Author

    Edit: Reviewing the code linked above, Reviewing https://github.com/nodejs/node/pull/12925/files#diff-4c74bb09dc4dabfff99ec3bc35181885R98, I think it needs to look for _destroyed property, also, to handle through2's implementation.

  6. mcollina commented on Jun 21, 2017

    @mcollina
    SponsorMember

    Ahum, that was not interfering with through2 when I did run the tests. Why do you think that?

    I will have a look asap (probably tomorrow). Maybe we should add vinyl-fs to citgm, we could have caught this earlier.

  7. phated commented on Jun 21, 2017

    @phated
    Author

    I'm attempting to apply your node patch to readable-stream so I can run our test suite with it incorporated.

  8. phated commented on Jun 21, 2017

    @phated
    Author

    Last I heard, vinyl-fs was included in citgm but no one wanted to deal with making it run properly so they just flagged it as flakey...

  9. phated commented on Jun 21, 2017

    @phated
    Author

    @mcollina your patch fixes our test failures. (I also want to note that lib/_stream_transform.js added a dependency on internal/errors which doesn't seem to be replaced by your build script).

    Any idea how long this will take to get resolved? It's currently blocking the major release of vinyl-fs

  10. mcollina commented on Jun 21, 2017

    @mcollina
    SponsorMember

    @nodejs/streams what do you think we should do?

    IMHO we can forward-port that fix, and then wait for core to release.

  11. mcollina commented on Jun 21, 2017

    @mcollina
    SponsorMember

    Can you please link the reference to internal/errors?

  12. phated commented on Jun 21, 2017

    @phated
    Author
  13. mcollina commented on Jun 21, 2017

    @mcollina
    SponsorMember

    Oh, that is part of core, that's the code we will convert. Not sure how it got there, I'll get it fixed.

  14. mcollina commented on Jun 21, 2017

    @mcollina
    SponsorMember

    Asap is whar we'll do.

  15. phated commented on Jun 21, 2017

    @phated
    Author

    Thanks!

  16. lrlna commented on Jun 21, 2017

    @lrlna
    Contributor

    heyyyy! it seems like node-core's got a fix coming on the next release (and that's within a week or so?); i am thinking we should just wait for that ✌️

  17. phated commented on Jun 21, 2017

    @phated
    Author

    It's really hard for me to find time to push towards our gulp4 (which requires this vinyl-fs major) release but I have some this week, so it would be really hard for me to wait until next week or later.

  18. mcollina commented on Jun 22, 2017

    @mcollina
    SponsorMember

    @phated we have just released v2.3.2 with the fix.

  19. phated commented on Jun 22, 2017

    @phated
    Author

    Thanks a ton @mcollina and team!

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions