LeanKit-Labs/wascally issues and pull requests

#139 - AMQP Uri support

Issue - State: open - Opened by AlexandreRoba almost 8 years ago

#138 - addExchange raise error when options is null

Issue - State: open - Opened by AlexandreRoba almost 8 years ago

#137 - Documentation not uptodate

Issue - State: open - Opened by AlexandreRoba almost 8 years ago

#136 - Accept a uri from configs

Issue - State: closed - Opened by ryanwilliamquinn about 8 years ago - 1 comment

#135 - Messages being acknowledge by queue and consumer not being set up after reconnect.

Issue - State: closed - Opened by ghost about 8 years ago - 1 comment

#134 - Added check if headers existed on reply

Pull Request - State: closed - Opened by mashu-daishi about 8 years ago - 1 comment

#133 - Duplicate default handling

Issue - State: closed - Opened by djMax about 8 years ago - 1 comment

#132 - How does one undo a startSubscription?

Issue - State: closed - Opened by djMax about 8 years ago - 5 comments

#131 - call clearAckInterval() on connection close event

Pull Request - State: closed - Opened by mikestaub about 8 years ago - 1 comment

#130 - Topology/bindings not rebuilt after reconnection

Issue - State: closed - Opened by steirico about 8 years ago - 1 comment

#129 - Promise is resolved before the message is published

Issue - State: closed - Opened by krazar about 8 years ago - 4 comments

#128 - How is concurrency handled?

Issue - State: closed - Opened by ppwfx over 8 years ago - 3 comments
Labels: question

#127 - option to import just the Broker class

Pull Request - State: closed - Opened by fczuardi over 8 years ago - 1 comment

#126 - configure promise is resolving empty

Pull Request - State: closed - Opened by fczuardi over 8 years ago - 2 comments

#125 - Setting a consumer tag

Issue - State: closed - Opened by lgomez over 8 years ago - 1 comment
Labels: question

#124 - Connection FSM consistency?

Issue - State: closed - Opened by yamii over 8 years ago - 2 comments

#123 - Wascally does not publish message after starting, stopping, and starting server during tests

Issue - State: closed - Opened by krishnaglick over 8 years ago - 5 comments

#122 - fanout exchange should not require message type or routing key

Issue - State: closed - Opened by mxriverlynn over 8 years ago - 1 comment

#121 - Are rejectUnhandled and onUnhandled working when using dead-lettering?

Issue - State: closed - Opened by n321203 over 8 years ago - 3 comments
Labels: bug

#120 - Question: Avoid handlers from picking up dead lettered messages?

Issue - State: closed - Opened by n321203 over 8 years ago - 1 comment

#119 - Wascally does not re-subscribe to manually started subscriptions on reconnection

Issue - State: closed - Opened by arobson over 8 years ago - 3 comments
Labels: bug

#118 - Pub/sub, my consumer is only getting called on every other publish.

Issue - State: closed - Opened by jnystrom over 8 years ago - 2 comments

#117 - Consumer Cancel Notification

Issue - State: closed - Opened by vjuras over 8 years ago - 1 comment
Labels: enhancement

#116 - Unable to handle non-JSON messages

Issue - State: closed - Opened by NRaf over 8 years ago - 1 comment
Labels: enhancement

#115 - Not clear how reconnect effects subscriptions

Issue - State: closed - Opened by dynajoe over 8 years ago - 4 comments
Labels: related

#114 - Declare a queue as HA

Issue - State: closed - Opened by NRaf over 8 years ago - 1 comment

#113 - zombie connections(flow connections) never closed

Issue - State: closed - Opened by BlueHotDog over 8 years ago - 1 comment
Labels: investigating

#112 - node.js 4.2.2 will not exit if wascally is required

Issue - State: closed - Opened by djMax over 8 years ago - 19 comments
Labels: enhancement

#111 - How to configure an exclusive consumer

Issue - State: closed - Opened by vilasmaciel over 8 years ago - 3 comments
Labels: enhancement

#110 - Address lint issues

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

#109 - Add badges to README.md

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

#108 - fix heartbeat and add it to documentation

Pull Request - State: closed - Opened by mxriverlynn over 8 years ago - 2 comments

#107 - connection timeout

Issue - State: closed - Opened by BlueHotDog over 8 years ago - 9 comments
Labels: bug, investigating

#106 - Add "verbatim" option to subscribe function

Pull Request - State: closed - Opened by josephfrazier over 8 years ago - 4 comments

#105 - Change pubsub demo credentials to guest/guest

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

#104 - Add examples of server clusters to README

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

#103 - `npm test` errors out with "Error: Cannot find module 'expect.js'"

Issue - State: closed - Opened by josephfrazier over 8 years ago - 3 comments
Labels: bug

#102 - README.md: fix ports forwarded by Vagrant

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

#101 - Add vagrant support for virtualbox provider

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

#100 - Bug fix - working with node-config

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

#99 - Enhancements & Bug fixes

Pull Request - State: closed - Opened by arobson over 8 years ago - 11 comments

#98 - memory leak in `wascally.addExchange`

Issue - State: closed - Opened by mxriverlynn over 8 years ago
Labels: bug

#97 - Error: Failed to create exchange 'dead.letters-ex.1' on connection 'default' with 'No endpoints could be reached'

Issue - State: closed - Opened by rkstar over 8 years ago - 9 comments

#96 - Is there a way to consume messages without a type?

Issue - State: closed - Opened by puncha over 8 years ago - 3 comments
Labels: enhancement

#95 - Handler registration against wildcard topics (message types)

Issue - State: closed - Opened by dermidgen over 8 years ago - 8 comments
Labels: investigating

#94 - Upgrade amqplib dependency to v0.4.0

Issue - State: closed - Opened by benjsicam over 8 years ago - 2 comments
Labels: enhancement

#93 - Question on when channels get closed.

Issue - State: closed - Opened by subbucomity almost 9 years ago - 2 comments
Labels: help wanted

#92 - Req/Res with alternate

Issue - State: closed - Opened by BLaurent almost 9 years ago - 1 comment

#91 - There should be a publish timeout

Issue - State: closed - Opened by dynajoe almost 9 years ago - 1 comment
Labels: enhancement

#90 - wascally ignores return value of amqplib `publish()`

Issue - State: closed - Opened by jwalton almost 9 years ago - 1 comment

#89 - Idle channel

Issue - State: closed - Opened by BlueHotDog almost 9 years ago - 5 comments
Labels: help wanted, investigating

#88 - how to set the send interval

Issue - State: closed - Opened by bboalimoe almost 9 years ago - 2 comments
Labels: help wanted

#87 - Handler to Queue binding

Issue - State: closed - Opened by joshrivers almost 9 years ago - 17 comments
Labels: help wanted, documentation / demo

#86 - Reply queue message not ack'ed on req-resp pattern

Issue - State: closed - Opened by pocheng almost 9 years ago - 1 comment
Labels: help wanted, investigating

#85 - Channels Limit on Heroku (Cloudamqp)

Issue - State: closed - Opened by dirajkumar almost 9 years ago - 2 comments
Labels: help wanted, investigating

#84 - what is the difference between reject and ack

Issue - State: closed - Opened by geyang almost 9 years ago - 4 comments
Labels: question

#83 - remove specific listener to listened emitted event

Issue - State: closed - Opened by yamii almost 9 years ago - 1 comment

#82 - Rabbitmq only sends another message to a queue after if ack/nack/resject earlier message.

Issue - State: closed - Opened by harishbisht8 almost 9 years ago - 2 comments

#81 - npm install wascally does not work

Issue - State: closed - Opened by ryandac almost 9 years ago - 1 comment
Labels: investigating

#80 - Add explanation of publish promises and message format to README

Pull Request - State: closed - Opened by arobson almost 9 years ago - 1 comment

#79 - Document message format

Pull Request - State: closed - Opened by arobson almost 9 years ago

#78 - Adding X-Priority Support

Pull Request - State: closed - Opened by akainz about 9 years ago - 1 comment

#77 - Reconnections and disconnections

Issue - State: closed - Opened by joergd about 9 years ago - 2 comments
Labels: documentation / demo

#76 - How to recover/subscribe to unacknowledged messages?

Issue - State: closed - Opened by dirajkumar about 9 years ago - 5 comments

#75 - Including postal envelope header `resolverNoCache`.

Pull Request - State: closed - Opened by ifandelse about 9 years ago - 1 comment

#74 - Memory leak on postal.js when using req-res pattern

Issue - State: closed - Opened by gideonairex about 9 years ago - 7 comments

#73 - Publish method seems async

Issue - State: closed - Opened by joergd about 9 years ago - 8 comments

#72 - Update dependencies. Prefer defer. Bug fix for queue and exchange destroy.

Pull Request - State: closed - Opened by arobson about 9 years ago - 1 comment

#71 - Need examples on setting up connection and ques programmatically (without topology definition)

Issue - State: closed - Opened by geyang about 9 years ago - 2 comments
Labels: help wanted

#70 - [Enhancement] Support of TS

Issue - State: closed - Opened by juliendangers about 9 years ago - 1 comment

#69 - How to remove binding from a direct exchange?

Issue - State: closed - Opened by geyang about 9 years ago - 3 comments

#68 - How to set connection configuration for heroku?

Issue - State: closed - Opened by rafaeljesus about 9 years ago - 4 comments

#67 - Adding vagrant support.

Pull Request - State: closed - Opened by brianedgerton about 9 years ago - 3 comments

#66 - Fix publish defect. Add URI to connection. Improvements around connection cleanup.

Pull Request - State: closed - Opened by arobson about 9 years ago - 1 comment

#65 - replyQueue: false - messages do not get published

Issue - State: closed - Opened by astanciu about 9 years ago - 2 comments
Labels: bug

#64 - Wascally doesn't work with the node 'config' module installed

Issue - State: closed - Opened by xiehan over 9 years ago - 3 comments
Labels: bug

#63 - Feature Request: Add a URL property on the connection object

Issue - State: closed - Opened by mehcode over 9 years ago - 3 comments
Labels: enhancement

#62 - Updated connection URI scheme name for SSL.

Pull Request - State: closed - Opened by longplay over 9 years ago - 2 comments

#61 - SSL Uri not built correctly

Issue - State: closed - Opened by longplay over 9 years ago
Labels: bug

#60 - Handling graceful termination of a subscriber

Issue - State: closed - Opened by mehcode over 9 years ago - 7 comments
Labels: question

#59 - How to properly close / release connections

Issue - State: closed - Opened by mehcode over 9 years ago - 10 comments

#58 - Bug fixes for #39 and #57. Bug fix for setting replyQueue to false.

Pull Request - State: closed - Opened by arobson over 9 years ago

#57 - message.ack() not working for requests

Issue - State: closed - Opened by dvideby0 over 9 years ago - 6 comments
Labels: bug

#56 - replyQueue false cause publish error

Pull Request - State: closed - Opened by juliendangers over 9 years ago - 2 comments

#55 - Is the rabbitmq_consistent_hash_exchange plugin required?

Issue - State: closed - Opened by bclubb over 9 years ago - 1 comment
Labels: question

#54 - added docs to explain how to set a channel prefetch limit

Pull Request - State: closed - Opened by mxriverlynn over 9 years ago

#53 - Is there a better way to get to channel prefetch?

Issue - State: closed - Opened by jarrettmeyer over 9 years ago - 3 comments

#52 - Add dead letter routing key

Pull Request - State: closed - Opened by dvideby0 over 9 years ago

#51 - dead letter routing key?

Issue - State: closed - Opened by dvideby0 over 9 years ago - 1 comment

#50 - Way to tell how many messages are in the que?

Issue - State: closed - Opened by geyang over 9 years ago - 1 comment
Labels: question

#49 - noBatch: allow a queue to run without batching ack/nack

Pull Request - State: closed - Opened by mxriverlynn over 9 years ago - 2 comments

#48 - Clarification of "message type" in handlers

Issue - State: closed - Opened by jhaugh42 over 9 years ago - 2 comments

#47 - use of `batchAck`, and clearing out some messages while other still run?

Issue - State: closed - Opened by mxriverlynn over 9 years ago - 20 comments
Labels: enhancement

#46 - [WSY-45] Check the `port` options before defaulting

Pull Request - State: closed - Opened by esatterwhite over 9 years ago - 2 comments

#45 - port option not honored

Issue - State: closed - Opened by esatterwhite over 9 years ago - 1 comment

#44 - Spec updates

Pull Request - State: closed - Opened by dcneiner over 9 years ago - 1 comment

#43 - Handle messages in "ready" state on reconnect

Issue - State: closed - Opened by nover over 9 years ago - 1 comment

#42 - Missing the connections for the connection name lookup

Pull Request - State: closed - Opened by leobispo over 9 years ago - 1 comment

#40 - wascally wabbit on redhat losing consumers?

Issue - State: closed - Opened by mxriverlynn over 9 years ago - 6 comments
Labels: investigating

#39 - Unacked messages piling up in response queue

Issue - State: closed - Opened by neverfox over 9 years ago - 18 comments
Labels: bug

GitHub / LeanKit-Labs/wascally issues and pull requests