Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B bull
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 175
    • Issues 175
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OptimalBits
  • bull
  • Issues
  • #2302
Closed
Open
Issue created Feb 21, 2022 by Administrator@rootContributor

`TimeoutError: Promise timed out after 500 milliseconds` on client disconnect

Created by: addisonElliott

Description

I'll apologize in advance for not having a simple, reproducible case. If I get some time in the future, I'll work on creating a test case that fails.

I'm running tests using jest and they started failing when I upgraded Bull. The bug starts in v4.5.5. Downgrading to v4.5.4, the problem is no longer present. See below for the error message.

  ● Test suite failed to run

    TimeoutError: Promise timed out after 500 milliseconds

      at Timeout.<anonymous> (node_modules/bull/lib/p-timeout.js:56:50)

This is the relevant change that caused issues: https://github.com/OptimalBits/bull/commit/41b940457b3447619c3c2887674a8cebf1508b07

The old p-timeout version used in v4.5.4 is v3.2.0 (https://github.com/sindresorhus/p-timeout/blob/v3.2.0/index.js). If you compare that with the latest version (which is what was upgraded to), it's pretty different. I suspect the bug lies somewhere in there.

That's about as far as I got ☹️. I spent some time debugging it but didn't get anywhere useful.

Let me know how I can help

Bull version

4.5.5

Assignee
Assign to
Time tracking