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

Fix boundary problem in range node #1338

Merged
merged 3 commits into from Jul 19, 2017
Merged

Fix boundary problem in range node #1338

merged 3 commits into from Jul 19, 2017

Conversation

kazuhitoyokoi
Copy link
Member

I fixed #1337.

@coveralls
Copy link

coveralls commented Jul 11, 2017

Coverage Status

Coverage decreased (-0.08%) to 86.054% when pulling 8b68ee1 on kazuhitoyokoi:master-rangenode into 5324244 on node-red:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.09%) to 86.039% when pulling 9b00cc4 on kazuhitoyokoi:master-rangenode into 5324244 on node-red:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.09%) to 86.039% when pulling 9b00cc4 on kazuhitoyokoi:master-rangenode into 5324244 on node-red:master.

@coveralls
Copy link

coveralls commented Jul 11, 2017

Coverage Status

Coverage remained the same at 86.132% when pulling 5bf3ea3 on kazuhitoyokoi:master-rangenode into 5324244 on node-red:master.

@knolleary knolleary merged commit c6e453f into node-red:master Jul 19, 2017
@kazuhitoyokoi
Copy link
Member Author

Thank you @knolleary 👍

dschrecking pushed a commit to SEDARI/neros that referenced this pull request Aug 11, 2017
* Fix boundary problem in range node

* Remove duplicated test case

* Empty commit to retry Travis CI
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Boundary problem in range node
3 participants