Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Strange issue > 4.0.10 #546

Open
1 of 4 tasks
jcbit opened this issue Jun 13, 2020 · 1 comment
Open
1 of 4 tasks

Strange issue > 4.0.10 #546

jcbit opened this issue Jun 13, 2020 · 1 comment

Comments

@jcbit
Copy link

jcbit commented Jun 13, 2020 •
edited
Loading

Issue type

  • bug
  • missing functionality
  • performance
  • feature request

Brief description

I was using 4.0.10 fine but when updating to 4.0.13 it broke. Several times a message is received it seems. When I create an order I get the order update fired like 6 times. All has the same information. I turned on seqAudit and it threw an error that it was getting the same number back several times. Had to move back to 4.0.10 and all is good again.

Steps to reproduce

Additional Notes:
@jcbit
Copy link
Author

jcbit commented Jun 21, 2020 •
edited
Loading

Had to debug this one... Found out each order was getting notified for any order that had a listener :s

jcbit added a commit to jcbit/bitfinex-api-node that referenced this issue Jun 21, 2020
@jcbit
Fixed bug reported bitfinexcom#546
627a04f 
_isEmpty only works for collections, here you are evaluating an individual item so something like checking for undefined would be best. This fixes my bug reported:
bitfinexcom#546
@jcbit jcbit mentioned this issue Jun 21, 2020
Open
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jcbit