Skip to content

Component: Queues/Workers #5333

@StachuDotNet

Description

@StachuDotNet

This Issue exists to collect many items that relate to "Queues/Workers" in Darklang.
In Darklang-classic, queues only existed in our Cloud runtime (since that was the only runtime), but going forward we should have them supported for the Local/CLI runtime as well.

  • uncomment the _events.dark test file. (This was quite flaky in CI, but we decided to put addressing that for a bit, and have uncommented this until we have some focus on queues/workers)
  • in Tests.fs, uncomment the usage of Queue.Tests.fs
  • bring back Queues, in some minimal capacity
    • why is the issue happening:
      • we clear the Queue DB
      • we add a message to check if the queue exists
      • multiple servers are doing that same thing
  • add timelimit for queue execution
    • the goal here is to limit the execution of an item on the queue
    • To end computation that runs over (lets say) 3 minutes. I'm not sure it's possible without adding cancellation tokens everywhere - maybe that's what we'll need to do?
  • Workers should be typed
  • emit's arg should be real worker name/reference, not a string
  • worker counts should work
  • it should be clearer if a worker is paused
  • workers should have dead-letter queues
  • review Rollbar: "Deadline Exceeded" (Rollbar: "Deadline Exceeded" #3815)
  • disable workers which do nothing (see disable crons and workers which do nothing #3958)

Metadata

Metadata

Assignees

No one assigned

    Labels

    laterLet's think about this later -- we have some higher-priority things to work through first

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions