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
  • #1148
Closed
Open
Issue created Dec 05, 2018 by Administrator@rootContributor

Job is dropped when rate limit hit and bounceback is set to true

Created by: aleccool213

Description

  • This is using the distributed async job processor pattern

Minimal, Working Test code to reproduce the issue.

  • set bounceBack to true for a queue
  • hit the rate limit
  • job is dropped instead of it being in the waiting queue

Bull version

latest

Additional information

  • this bug is minimal impact currently because bounceBack was just recently introduced
  • Here is where the code removes the job from the active queue which is correct: https://github.com/wishabi/bull/blob/632ad7c95cae9bb0fc273b6243ffb9bd1e7888a1/lib/commands/moveToActive-8.lua#L67
  • What doesn't happen is that it is added back to the waiting queue
Assignee
Assign to
Time tracking