-
Notifications
You must be signed in to change notification settings - Fork 55
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
[v1.6.3]: Fix Memory Leak and Improvements #157
Conversation
interface.address.startsWith('10.') || | ||
interface.address.startsWith('172.') || | ||
interface.address.startsWith('192.168.')); | ||
})[0]; |
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.
Does this mean we're changing from picking the last interface given to the first?
Also, we're not saving ipv6 addresses anymore?
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.
if you take a look at the current implementation here, you can see in the if
condition we just check for the existence of ipv4
despite of taking all[ifaces[i]].ipv4 || all[ifaces[i]].ipv6
- we have always taken the ipv4
if possible.
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.
Ah, good call about ipv6. Saw that and then promptly forgot it.
This
Pull Request
contains lots of version dependency updates mainly because of the issues and warnings their older versions had.According to this issue,
inflight
had a memory leak issue and was being used byglob
which is among our dependencies.I have also converted
mocha
tests tojest
to make it easy to extend for our developers, replaced the usage ofmacaddress
with built-inos
and also cleaned upGruntfile.js
too.