FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Process not exiting by default · Issue #866 · nodegit/nodegit · GitHub

Repository navigation

Process not exiting by default #866

Description

Running a js file that has has just one line that requires nodegit like so:

var nodegit = require("nodegit");

results in the process not exiting... Is this a bug?
node in verson 4.2.4, nodegit in latest version from npm: 0.8.0

Activity

johnhaley81 commented on Jan 18, 2016

Collaborator

Confirmed. This is a bug.

changed the title [-]Potential Bug: Process not exiting by default[/-] [+]Process not exiting by default[/+] on Jan 18, 2016

map01ASCIIDOC10 commented on Jan 26, 2016

I'm also experiencing this

var nodegit = require("nodegit");
console.log("exit?");

just hangs on exit?.


  • nodegit@0.9.0
  • node v5.0.0
  • ubuntu 15.10

johnhaley81 commented on Jan 26, 2016

Collaborator

@srajko can you look into this? I think this is related to #854

lowellk commented on Jan 26, 2016

Can anyone tell me the latest version that does not have this bug?

johnhaley81 commented on Jan 26, 2016

Collaborator

This bug was introduced in 0.8.0 I believe.

srajko commented on Jan 27, 2016

Collaborator

Confirmed - this started happening with 80aabf2

srajko commented on Jan 27, 2016

Collaborator

OK, I have a fix.

Thanks for the bug report @philkunz and @01AutoMonkey!

And thanks for pinging me @johnhaley81 :-)

johnhaley81 commented on Jan 27, 2016

Collaborator

<3

guoshencheng commented on Jan 28, 2016

@srajko thanks, but, is the fix released ?

tbranyen commented on Jan 28, 2016

Member

Check the README we have instructions for installing at various commits. This won't install prebuilts though, so might not be useful for your needs.

philkunz commented on Jan 29, 2016

Author

just as a question: Why aren't patches released in a more constant manner to npm? This fix could be implemented in version 0.9.1 for example.

johnhaley81 commented on Jan 29, 2016

Collaborator

Valid question.

Mostly because of the overhead in releasing that we have. Almost all related to updating CHANGELOG.md and https://www.nodegit.org. The building of the binaries is mostly automated so that's not too bad anymore.

If those were eliminated then we could have a much faster release process which would help getting stuff out there faster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions


      Back | FazBrowse Home | New Git URL