search

msiebuhr / slint

Lint-tool for web projects
BSD 3-Clause "New" or "Revised" License
7 stars 1 forks source link

Versions and releases #23

Closed Munter closed 10 years ago

Munter commented 10 years ago

Please release one or more versions. The current version released on npm is not new enough to start testing git pre commit hooks

msiebuhr commented 10 years ago

I have quite lost the interest in this project for the time being, and only seem to get something done when you or @papandreou bother me enough about it.

As a consequence, I've now added the two of you as owners of the project on NPM. Knock yourselves out...

Munter commented 10 years ago

Fair enough. I'll take a look at releasing later today

papandreou commented 10 years ago

Apart from the issue you reported yesterday, --git has a known bug that has kept me from advocating a release. For large projects, it randomly and unpredicably segfaults. Looks very much like a nodegit bug (I have gdb backtraces), but I haven't been able to provide a neat testcase that doesn't involve a huge chunk of my own code. I might try to just report the traces, maybe it'll be an obvious fix.

OTOH people can just not use --git or try again if this happens. As long as we're pre-release, anything goes :)

Munter commented 10 years ago

Yup. I'll take a look at marking some flags as experimental and release 0.1.0 That should still convey the lack of maturity well enough :)

Munter commented 10 years ago

Heads up! I just force pushed because the recent changes added regressions that went untested.

I can't release v0.1.0 at the moment, and I don't know what causes the error: 

npm http PUT https://registry.npmjs.org/slint
npm http 409 https://registry.npmjs.org/slint
npm http GET https://registry.npmjs.org/slint
npm http 200 https://registry.npmjs.org/slint
npm http PUT https://registry.npmjs.org/slint/-/slint-0.1.0.tgz/-rev/5-91a7c930aa2b1f161d4cfb892be01cb6
npm http 500 https://registry.npmjs.org/slint/-/slint-0.1.0.tgz/-rev/5-91a7c930aa2b1f161d4cfb892be01cb6
npm ERR! registry error parsing json
npm http PUT https://registry.npmjs.org/slint/-/slint-0.1.0.tgz/-rev/5-91a7c930aa2b1f161d4cfb892be01cb6
npm ERR! cb() never called!
npm ERR! not ok code 0
papandreou commented 10 years ago

Saw the same thing yesterday when attempting to publish a different package. Turns out npm tried to parse a Varnish error html page as json and blew up. It was fixed 10 minutes later.

papandreou commented 10 years ago

I reported the segfault here: https://github.com/nodegit/nodegit/issues/132

Munter commented 10 years ago

And we're off. v0.1.0 released

msiebuhr commented 10 years ago

:+1: