René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"nodegit doesn't return control to the calling application","articleBody":"I have the following code\n\n``` javascript\nvar cloneOptions = {};\ncloneOptions.remoteCallbacks = {\n    credentials: function(url, userName) {\n        return NodeGit.Cred.sshKeyFromAgent(userName);\n    }\n};\nlogger.info('Cloning snapshot repo');\nvar getMostRecentCommit = function(repository) {\n    return repository.getBranchCommit('master');\n};\n\nvar getCommitMessage = function(commit) {\n    return commit.message();\n};\nNodeGit.Clone(remoteRepo, path.join('_deployments',deployFolderName), cloneOptions )\n    .then(getMostRecentCommit, function() { logger.error('error %o', arguments);})\n    .then(getCommitMessage, function() { logger.error('error %o', arguments);})\n    .then(function(message) {\n        return logger.info(message);\n    }, function() { logger.error('error %o', arguments);});\n\n```\n\nThis is largely copypasta from your site.\n\nThe `NodeGit.*` chain is working fine; the repo is being cloned and I'm getting the right commit message.\n\nHowever, my application then just sits and waits. There's no indication in the nodegit docs that I need to manually resolve the Promise or anything like in order for my application to complete.\n\nWhat am I missing here? Or is this a nodegit bug?\n","author":{"url":"https://github.com/dancrumb","@type":"Person","name":"dancrumb"},"datePublished":"2015-03-19T17:14:53.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":36},"url":"https://github.com/497/nodegit/issues/497"}