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.

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

Meteor Collection returns collection of wrong “limit” if “skip” parameter has floating point #4844

Closed
iSuslov opened this issue Jul 30, 2015 · 2 comments

Comments

@iSuslov
Copy link

iSuslov commented Jul 30, 2015

Meteor Collection returns collection of wrong “limit” if “skip” parameter has floating point 19.999999999999996

@Slava
Copy link
Contributor

Slava commented Aug 4, 2015

Please provide a full reproduction as described in: https://github.com/meteor/meteor/wiki/Contributing-to-Meteor#reporting-a-bug-in-meteor Without a way to replicate your problem, we can't debug and fix it.

Does it happen on querying? Does it happen on server or client? Does it happen on LiveQuery?

@Slava
Copy link
Contributor

Slava commented Aug 4, 2015

I couldn't reproduce it neither on client, nor on server. Neither with querying, nor with observe APIs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants