Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
communications-backbone communications-backbone
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 25
    • Issues 25
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Communications Backbone System
  • communications-backbonecommunications-backbone
  • Issues
  • #49

Closed
Open
Created Jun 27, 2023 by James Kirk@jamkiOwner

Queues created only when messages are sent to in advance

If we pass in a new client, then try to do GET /queue before we've sent any messages, the server breaks as the queue doesn't exist. This is because the queues are only created once we've sent something to them.

Not urgent but definitely an issue. Currently we have:

response = channel.queue_declare(queue=queue_name, passive=True)

in get_queue_status(), where passive=True returns an error if the queue doesn't already exist, which is where the error is thrown. Maybe we need to make sure the queues exist once they're all setup during client creation?

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking