-
-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added a unit test, check offline queue in QoS 1 #264
Conversation
f7f9edc
to
64c10c3
Compare
Would you mind to bump aedes persistence? |
The CI test will pass after merging moscajs/aedes-persistence#33 |
And this PR also requires moscajs/aedes-persistence#32, otherwise aedes will not properly call emptyQueue |
The items in offline queue should be same as what we inserted
b146a33
to
54e5d35
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Are we ready for a release of Aedes? Would you mind sending PRs to the redis and mongodb persistences updating them? |
Which part do you want to update aedes-persistence-redis and aedes-persistence-mongodb? |
I prefer to review the changes
Il giorno mar 6 ago 2019 alle 17:27 Gnought <[email protected]> ha
scritto:
… Which part do you want to update aedes-persistence-redis and
aedes-persistence-mongodb?
Still have some PR on hands. The release could go fast if we agree on
directly making changes in master branch. :)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#264>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAMXY7BH34UZ3LFEYVPR3DQDGJ7LANCNFSM4IEBC6EQ>
.
|
The items in offline queue should be same as what we inserted.
However it is related to aedes-persistence. The PR moscajs/aedes-persistence#31 will fix the CI test.