-
Notifications
You must be signed in to change notification settings - Fork 11
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
error using omeg-supreme method #13
Comments
But, your test fails if an invalid/non-existent spark is given to primus.forward.sparks(). I made the following change to your server code and ran it again:
Here is what happens as a result:
This is a valid case because sparks can be disconnected anytime (even during the call to .forwards() method). Also, if you decide to fix it, please make sure you return an array of results with one result item for each corresponding spark in the input array like you do for metroplex.sparks(). |
['L1mXUWv', 'L1mXUX9', '234fwfrewrw423#%#$'] So, if above is the input list of sparks and assuming that 3rd item is invalid/disconnected/non-existent, the output should be similar to: [ 'ok','ok',null ] |
It should be fixed in master.
Unfortunately this is not possible as the return value is the info object returned by |
Should I create a new issue at omega-supreme? This is important for client, so it could record the info in DB if the pkt was sent to a spark successfully or not (for re-attempts etc). |
Yes, do it. |
Done. |
was 780c235 not added to the latest release? |
nope. |
when will it be done? And, what are we waiting for? I mean is it safe to get it from the repo directly? |
The problem is that if we publish current master we will force people to use https://github.com/luin/ioredis. You can safely install from GitHub in the meanwhile. |
@lpinca go for it. |
Published |
I have added metroplex with omega-supreme.
Then, I have the following code snippet
The code above prints following error:
Example list of sparks:
I may be missing something in configuration I think:
The text was updated successfully, but these errors were encountered: