The docs for Symfony Bundle should be more explicit about extension tags when using different consume commands. I'm referring to https://php-enqueue.github.io/bundle/consumption_extension/#consumption-extension

When using the "enqueue:transport:consume" command a consumption extension needs to be registered with the tag enqueue.transport.consumption_extension (while docs currently only mentio

The AMQP spec says that prefetchCount is a short (16-bit) value. Despite this, the java amqp-client accents an int parameter. The int then has its MSB stripped off, and the remainder is reinterpreted as a short.

For example, if you supply a prefetch of 1_000_000, that gets interpreted as a prefetchCount of 16960

0b

Is there any documentation or examples on methods to handle disconnect / reconnect scenarios? Specifically I'm interested in typical or suggested patterns or even an explanation of the behavior of basic_send when the server disconnects.

Example: stomp.py has a [on_receiver_loop_ended callback](https://github.com/jasonrbriggs/stomp.py/blob/b04c754e

Code cov. report: https://codecov.io/gh/viartemev/the-white-rabbit/tree/master/src/main/kotlin/com/viartemev/thewhiterabbit/exchange

Steps to reproduce:

1. Deploy a container based on the tarantool/tarantool:1.x-centos7 image:

docker-compose.yml:

version: '3'

services:
  tarantool:
    container_name: tarantool
    build:
      context: .
      dockerfile: Dockerfile.tarantool
    command: tarantool /opt/tarantool/app.lua
    volumes:
      - ./app.lua:/opt/tarantool/app.lua
    ports:
      - '3301:330

Specs - Message delivery retry, Message ordering

When a Client reconnects with CleanSession set to 0, both the Client and Server MUST re-send any unacknowledged PUBLISH Packets (where QoS > 0) and PUBREL Packets using their ori

• add info about new Mojo::Promise based methods
• update Client.pm with with new Publisher API example

For be more easy to create and manage front-end components, I think that is better to change from jQuery to Vue.js.