-
Notifications
You must be signed in to change notification settings - Fork 45
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
Fixes for Windows #70
Conversation
Codecov Report
@@ Coverage Diff @@
## master #70 +/- ##
=======================================
Coverage 84.33% 84.33%
=======================================
Files 1 1
Lines 83 83
Branches 24 24
=======================================
Hits 70 70
Misses 13 13 Continue to review full report at Codecov.
|
Appveyor doesn't seem to be picking up change to run on Node 8 |
Travis and Appveyor both building successfully. |
Works on Node 8.1.3. Might work on earlier versions, not sure when libuv/libuv#1323 went into Node. |
.travis.yml
Outdated
@@ -4,9 +4,10 @@ notifications: | |||
language: node_js | |||
dist: trusty | |||
node_js: | |||
- "0.10.45" | |||
- "7" | |||
- "0.12" |
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.
It's high time we removed support for this.
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.
And by "this" I mean anything less than node v6 on travis.
package.json
Outdated
@@ -13,21 +18,25 @@ | |||
"engines": { | |||
"node": ">= v0.8.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.
Can you please bump this to >= v6. It's a shame we can't do platform specific versions given Windows now requires v8. I searched and the only solution is a failing install script.
@baudehlo sure see latest commit |
@baudehlo is there anything else you need on this PR? |
I don't think so. Just need some free time (baby, new house, etc).
… On Jul 19, 2017, at 6:46 PM, David Halls ***@***.***> wrote:
@baudehlo is there anything else you need on this PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@baudehlo been there - take time for what's important. |
Merged |
BTW after merge Travis fails. Not sure why.
…On Thu, Jul 20, 2017 at 1:40 AM, David Halls ***@***.***> wrote:
@baudehlo <https://github.com/baudehlo> been there - take time for what's
important.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#70 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAobY7u3RPnzhcNlT4d1MrvrEyxTMz21ks5sPuhHgaJpZM4ORcVU>
.
|
Node 8 behaviour has changed for the -1 utime test. It sets it fine (and Node 6 and Python read the atime as -1). But for Node 8 atime in that case is NaN. |
@baudehlo how do |
I think those were just added after I released this.
… On Jul 20, 2017, at 6:18 PM, David Halls ***@***.***> wrote:
@baudehlo how do utime and utimeSync provided by fs-ext differ from fs.futimes and fs.futimesSync don't?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
How would you feel about removing them or making them aliases?
…On 20 Jul 2017 11:52 p.m., "Matt Sergeant" ***@***.***> wrote:
I think those were just added after I released this.
> On Jul 20, 2017, at 6:18 PM, David Halls ***@***.***>
wrote:
>
> @baudehlo how do utime and utimeSync provided by fs-ext differ from
fs.futimes and fs.futimesSync don't?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or mute the thread.
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#70 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACOMU8bjBcJ_GS_8R1A8NCVss3-rd0srks5sP9oZgaJpZM4ORcVU>
.
|
Sounds good to me.
… On Jul 20, 2017, at 7:00 PM, David Halls ***@***.***> wrote:
How would you feel about removing them or making them aliases?
On 20 Jul 2017 11:52 p.m., "Matt Sergeant" ***@***.***> wrote:
> I think those were just added after I released this.
>
> > On Jul 20, 2017, at 6:18 PM, David Halls ***@***.***>
> wrote:
> >
> > @baudehlo how do utime and utimeSync provided by fs-ext differ from
> fs.futimes and fs.futimesSync don't?
> >
> > —
> > You are receiving this because you were mentioned.
> > Reply to this email directly, view it on GitHub, or mute the thread.
> >
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#70 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ACOMU8bjBcJ_GS_8R1A8NCVss3-rd0srks5sP9oZgaJpZM4ORcVU>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Tests now pass and it compiles on Windows!
Question:
utime
still needed givenfs.utimes
exists?