rabbitmq/rabbitmq-message-timestamp issues and pull requests

#39 - support 3.12.x

Issue - State: closed - Opened by Guzzi over 1 year ago - 3 comments
Labels: enhancement

#37 - Allow overwriting timestamps

Pull Request - State: closed - Opened by lukebakken almost 2 years ago

#35 - Support 3.10.8

Issue - State: closed - Opened by chadknutson about 2 years ago - 1 comment

#34 - Support 3.11.x

Issue - State: closed - Opened by frazjp65 about 2 years ago - 3 comments

#33 - support 3.9

Issue - State: closed - Opened by kudrmudr about 3 years ago - 5 comments

#32 - Fix builds after monorepo migration

Pull Request - State: closed - Opened by binarin about 3 years ago

#31 - Can someone build a release?

Issue - State: closed - Opened by eeblouin about 3 years ago - 4 comments

#30 - Support 3.9.0

Issue - State: closed - Opened by luddd3 over 3 years ago - 1 comment

#29 - Switch to Mozilla Public License 2.0 (MPL 2.0)

Pull Request - State: closed - Opened by dcorbacho over 4 years ago

#28 - Switch to Mozilla Public License 2.0 (MPL 2.0)

Pull Request - State: closed - Opened by dcorbacho over 4 years ago

#27 - Plugin doesn't support current server version. Actual broker version: "3.8.0"

Issue - State: closed - Opened by yderi about 5 years ago - 1 comment
Labels: duplicate

#26 - Support RabbitMQ 3.8

Issue - State: closed - Opened by MrMarkW about 5 years ago - 6 comments

#25 - Timestamp as message exits broker

Issue - State: closed - Opened by akoutmos over 5 years ago - 3 comments

#24 - Timestamp in nano_seconds

Issue - State: closed - Opened by emerleite over 5 years ago - 1 comment
Labels: wontfix, usability

#23 - URL Cleanup

Pull Request - State: closed - Opened by spring-operator over 5 years ago

#22 - Closing AMQP connections after activating the plugin

Issue - State: closed - Opened by maess89 almost 7 years ago - 3 comments
Labels: question

#21 - timestamp_in_ms missing via stomp protocol

Issue - State: closed - Opened by brettmc almost 7 years ago - 1 comment

#20 - Lost `head_message_timestamp` after restart

Issue - State: closed - Opened by kinjelom almost 7 years ago - 1 comment
Labels: not-enough-information

#19 - TImestamp plugin doesn't seem to apply timestamps to messages arriving via Federated exchange before hitting x-consistent-hash exchange

Issue - State: closed - Opened by jefftrimm about 7 years ago - 2 comments
Labels: question

#18 - Erlang/OTP 19.2 is now the minimum supported version.

Pull Request - State: closed - Opened by michaelklishin over 7 years ago

#17 - Added another property "timestamp_in_ms" into header.

Pull Request - State: closed - Opened by hradilf over 7 years ago - 2 comments

#16 - Provide a timestamp in miliseconds as well as seconds

Issue - State: closed - Opened by hradilf over 7 years ago - 10 comments
Labels: enhancement, effort-low

#15 - Millesecond Precision

Pull Request - State: closed - Opened by edi1980 almost 8 years ago - 2 comments
Labels: wontfix

#14 - Missing direct link to the binary

Issue - State: closed - Opened by KokaChernov about 8 years ago - 1 comment
Labels: question

#13 - Question: default plugin?

Issue - State: closed - Opened by vikinghawk about 8 years ago - 1 comment
Labels: question

#12 - No curses lib functions found

Issue - State: closed - Opened by gholadr over 8 years ago - 6 comments
Labels: question

#11 - Switch test suite to Common test

Pull Request - State: closed - Opened by michaelklishin over 8 years ago

#10 - Switch test suite to Common Test

Issue - State: closed - Opened by michaelklishin over 8 years ago
Labels: effort-tiny

#9 - Add warning about more than one interceptor

Pull Request - State: closed - Opened by gmr over 8 years ago

#8 - Do not use time_compat

Pull Request - State: closed - Opened by hairyhum over 8 years ago

#7 - Set broker version requirements