Hacker News Reader

Comment by tacos | Hacker News Reader

I'm running the latest insider build. The bugs reported are based on personal experience and I verified they were currently open on GitHub as well before I posted. Tar hangs, cmake can't find a compiler, Valgrind goes nuts, and mono doesn't run. This is right at the top of the current issue list on GitHub with Microsoft annotations confirming the bugs.

I do what I can to report issues but frankly I do pretty basic development and hit an immediate brick wall with this stuff. I can't believe I'm celebrating Cygwin both for stability and breadth of packages. It's nuts.

I don't expect you guys to demo tensorflow. I'm simply saying that getting Redis limping borders on false prophecy.

View on HN

"He's welcome to run the same redis demo he does every tradeshow and pretend everything's hot and ready for action, but it's misleading at best."

Here, I just built TensorFlow on my Surface while sitting here in an airport. Here's a screenshot: http://i.imgur.com/WlNNuVt.png

I'll try some more complex TensorFlow examples on the plane.

I'm sorry you're having (or had) issues with the build on your machine, but your negativity is kind of a bummer. We're happy to help chase down filed bugs.

writev() still doesn't work, Scott. That breaks countless tools, often subtly. The fix somehow didn't make it into the latest insider build.

My solution? Wait for Windows update to change every Windows component, in hopes that I can then maybe run cmake in a console window.

Like I said, I appreciate the recent progress, but this is exactly the type of goofy situation you used to jump up and down about years ago.

Who are you?

UPDATE: Looks like the TensorFlow minst (no GPU) test data set works: http://i.imgur.com/n4zDz3a.png

Have you got any example tar files that definitely hang on the latest build? I'm sure I've been able to tar -xf on the first and current builds.

I did a "make dist" and then tried to untar. It hung two builds ago. This build it hangs -- or worse, the files are corrupted. It's sort of ridiculous.

EDIT: Maybe it's bug #313? Anyway the Microsoft I used to know wouldn't release stuff like this. Step 1 fire all the testers. Step 2 "let the community vote." Step 3 is not profit.

https://github.com/Microsoft/BashOnWindows/issues/313

Reply on news.ycombinator.com