Skip to content

Issue when parsing large files #449

Open

Description

@maximedupre

I don't know the inner workings of the problem, because I didn't build the library where the error is coming from, but please see https://github.com/tunnckoCore/koa-better-body/issues/109.

Activity

  1. tunnckoCore commented on Oct 27, 2017

    @tunnckoCore
    Member

    Yup. It seems like problem in node-formidable. And if this helps to anyone, here's explanation.

    In the given issue, there is really well-known and all loved "cannot read of undefined"

    TypeError: Cannot read property 'fields' of undefined
    

    Yep, but it isn't a problem in my code, because in that line the result variable must be an object with fields and files properties which comes directly when "end" event of Formidable is fired here.

    Now i'm starting to think that it not even goes to there, but probably aborted or error event is fired.

    Yes, i should probably add one try catch block there so we can debug more. Btw, @maximedupre you can try locally and see what is the real error. I'm sure that one of above events are fired.

  2. maximedupre commented on Oct 27, 2017

    @maximedupre
    Author

    The onerror event handle of koa-better-body is being fired with the above error.

  3. tunnckoCore commented on Oct 27, 2017

    @tunnckoCore
    Member

    Ssstrange. I seriously think that the problem is here, but i'll check what i can do in my lib as soon as i get a bit more time.

  4. GrosSacASac commented on Dec 27, 2020

    @GrosSacASac
    Contributor

    Is it an issue inside koa-better-body or formidable ?

  5. tunnckoCore commented on Jan 7, 2021

    @tunnckoCore
    Member

    It cannot be at koa-better-body for sure. I don't do anything specific and spectacular there, just calling Formidable (.parse without callback).

  6. added
    Priority: MediumThis issue may be useful, and needs some attention.
    Status: AvailableNo one has claimed for resolving this issue. Generally applied to bugs and enhancement issues.
    Type: BugInconsistencies or issues which will cause an issue or problem for users or implementors.
    Type: EnhancementMost issues will probably be for additions or changes. Expected that this will result in a PR.
    Area: streamsThings related to handling streams, and bugs around them.
    and removed on Apr 2, 2022
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

    Area: streamsThings related to handling streams, and bugs around them.Priority: MediumThis issue may be useful, and needs some attention.Status: AvailableNo one has claimed for resolving this issue. Generally applied to bugs and enhancement issues.Type: BugInconsistencies or issues which will cause an issue or problem for users or implementors.Type: EnhancementMost issues will probably be for additions or changes. Expected that this will result in a PR.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions