Daggraph fails with TypeError #26

krissrex · 2017-12-18T19:01:05Z

Description

Trying to run daggraph exits with an exception.
Node version: v8.9.1
OS: Windows 10

Steps to reproduce

Run daggraph

Expected behaviour

Graph generation without errors.

Log

$ daggraph
Analyzing dagger components and modules..
TypeError: pending.then is not a function
    at FileHound._searchAsync (C:\Users\krire\AppData\Roaming\nvm\v8.9.1\node_modules\daggraph\node_modules\filehound\lib\filehound.js:705:22)
    at tryCatcher (C:\Users\krire\AppData\Roaming\nvm\v8.9.1\node_modules\daggraph\node_modules\bluebird\js\release\util.js:16:23)
    at MappingPromiseArray._promiseFulfilled (C:\Users\krire\AppData\Roaming\nvm\v8.9.1\node_modules\daggraph\node_modules\bluebird\js\release\map.js:61:38)
    at MappingPromiseArray.PromiseArray._iterate (C:\Users\krire\AppData\Roaming\nvm\v8.9.1\node_modules\daggraph\node_modules\bluebird\js\release\promise_array.js:114:31)
    at MappingPromiseArray.init (C:\Users\krire\AppData\Roaming\nvm\v8.9.1\node_modules\daggraph\node_modules\bluebird\js\release\promise_array.js:78:10)
    at MappingPromiseArray._asyncInit (C:\Users\krire\AppData\Roaming\nvm\v8.9.1\node_modules\daggraph\node_modules\bluebird\js\release\map.js:30:10)
    at Async._drainQueue (C:\Users\krire\AppData\Roaming\nvm\v8.9.1\node_modules\daggraph\node_modules\bluebird\js\release\async.js:138:12)
    at Async._drainQueues (C:\Users\krire\AppData\Roaming\nvm\v8.9.1\node_modules\daggraph\node_modules\bluebird\js\release\async.js:143:10)
    at Immediate.Async.drainQueues (C:\Users\krire\AppData\Roaming\nvm\v8.9.1\node_modules\daggraph\node_modules\bluebird\js\release\async.js:17:14)
    at runCallback (timers.js:789:20)
    at tryOnImmediate (timers.js:751:5)
    at processImmediate [as _immediateCallback] (timers.js:722:5)

The text was updated successfully, but these errors were encountered:

smaslenko · 2017-12-25T13:02:26Z

Preconditions:
Node v9.3.0
Dagger2
Actual result:

Analyzing dagger components and modules..
TypeError: pending.then is not a function
at FileHound._searchAsync (C:\Users\ispst\AppData\Roaming\npm\node_modules\daggraph\node_modules\filehound\lib\filehound.js:705:22)
at tryCatcher (C:\Users\ispst\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\util.js:16:23)
at MappingPromiseArray._promiseFulfilled (C:\Users\ispst\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\map.js:61:38)
at MappingPromiseArray.PromiseArray._iterate (C:\Users\ispst\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\promise_array.js:114:31)
at MappingPromiseArray.init (C:\Users\ispst\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\promise_array.js:78:10)
at MappingPromiseArray._asyncInit (C:\Users\ispst\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\map.js:30:10)
at Async._drainQueue (C:\Users\ispst\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\async.js:138:12)
at Async._drainQueues (C:\Users\ispst\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\async.js:143:10)
at Immediate.Async.drainQueues [as _onImmediate] (C:\Users\ispst\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\async.js:17:14)
at runCallback (timers.js:773:18)
at tryOnImmediate (timers.js:734:5)
at processImmediate [as _immediateCallback] (timers.js:711:5)

dvdciri · 2017-12-26T11:25:45Z

Tried to reproduce it but without any success, it seems like a bug in the filehound lib as far as i can see. Will try to investigate it

dvdciri · 2017-12-26T23:56:35Z

Just tried upgrading to node version v9.2.1 and it works. No problems with that, try updating to the latest version and if you have the same issue provide more context as i've no idea how to reproduce this.

smaslenko · 2017-12-27T08:40:24Z

Can you please test it on this project https://github.com/smaslenko/nest-api-demo

krissrex · 2017-12-28T18:20:40Z

I get the same error on v9.2.1. @dvdciri are you running it on windows?

smaslenko · 2017-12-28T18:43:30Z

@krissrex yes, Windows 10 64-bit

juandiana · 2018-01-16T15:12:31Z

I'm experiencing the same problem. Using node v9.4.0.

BrianOdisho · 2018-02-07T22:17:03Z

Same error on Windows 10 64-bit with node v9.5.0

N-i-p-o-l · 2018-03-01T06:41:56Z

TypeError: pending.then is not a function
    at FileHound._searchAsync (C:\Users\NiPoL\AppData\Roaming\npm\node_modules\daggraph\node_modules\filehound\lib\filehound.js:705:22)
    at tryCatcher (C:\Users\NiPoL\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\util.js:16:23)
    at MappingPromiseArray._promiseFulfilled (C:\Users\NiPoL\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\map.js:61:38)
    at MappingPromiseArray.PromiseArray._iterate (C:\Users\NiPoL\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\promise_array.js:114:31)
    at MappingPromiseArray.init (C:\Users\NiPoL\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\promise_array.js:78:10)
    at MappingPromiseArray._asyncInit (C:\Users\NiPoL\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\map.js:30:10)
    at Async._drainQueue (C:\Users\NiPoL\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\async.js:138:12)
    at Async._drainQueues (C:\Users\NiPoL\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\async.js:143:10)
    at Immediate.Async.drainQueues [as _onImmediate] (C:\Users\NiPoL\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\async.js:17:14)
    at runCallback (timers.js:757:18)
    at tryOnImmediate (timers.js:718:5)
    at processImmediate [as _immediateCallback] (timers.js:698:5)

Node v9.6.1 version
npm 5.6.0

Please help

MarkNjunge · 2019-01-11T09:07:51Z

Same error.

Windows 10 64-bit, Node 10.15.0

Analyzing dagger components and modules..
TypeError: pending.then is not a function
    at FileHound._searchAsync (C:\Users\Mark Kamau\AppData\Roaming\npm\node_modules\daggraph\node_modules\filehound\lib\filehound.js:705:22)
    at tryCatcher (C:\Users\Mark Kamau\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\util.js:16:23)
    at MappingPromiseArray._promiseFulfilled (C:\Users\Mark Kamau\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\map.js:61:38)
    at MappingPromiseArray.PromiseArray._iterate (C:\Users\Mark Kamau\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\promise_array.js:114:31)
    at MappingPromiseArray.init (C:\Users\Mark Kamau\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\promise_array.js:78:10)
    at MappingPromiseArray._asyncInit (C:\Users\Mark Kamau\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\map.js:30:10)
    at _drainQueueStep (C:\Users\Mark Kamau\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\async.js:142:12)
    at _drainQueue (C:\Users\Mark Kamau\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\async.js:131:9)
    at Async._drainQueues (C:\Users\Mark Kamau\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\async.js:147:5)
    at Immediate.Async.drainQueues [as _onImmediate] (C:\Users\Mark Kamau\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\async.js:17:14)
    at runCallback (timers.js:705:18)
    at tryOnImmediate (timers.js:676:5)
    at processImmediate (timers.js:658:5)

AMK9978 · 2019-08-22T10:45:13Z

Hi!
A long time has passed and I can't use this repository because of this problem,
Won't be solved?

N-i-p-o-l · 2019-10-17T13:17:10Z

Same problem node v.10.16.3 Windows 10 x64

vberezkin · 2019-10-23T13:07:09Z

Same problem

agoztin · 2019-11-28T13:26:00Z

I know this issue was closed but I find a solution, simply invoke daggraph with a dot "." to pass the cwd
$ daggraph .

dvdciri added bug help wanted labels Dec 26, 2017

dvdciri closed this as completed Dec 26, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Daggraph fails with TypeError #26

Daggraph fails with TypeError #26

krissrex commented Dec 18, 2017 •

edited

Loading

smaslenko commented Dec 25, 2017 •

edited

Loading

dvdciri commented Dec 26, 2017

dvdciri commented Dec 26, 2017

smaslenko commented Dec 27, 2017

krissrex commented Dec 28, 2017

smaslenko commented Dec 28, 2017

juandiana commented Jan 16, 2018

BrianOdisho commented Feb 7, 2018

N-i-p-o-l commented Mar 1, 2018 •

edited

Loading

MarkNjunge commented Jan 11, 2019

AMK9978 commented Aug 22, 2019

N-i-p-o-l commented Oct 17, 2019

vberezkin commented Oct 23, 2019

agoztin commented Nov 28, 2019

Daggraph fails with TypeError #26

Daggraph fails with TypeError #26

Comments

krissrex commented Dec 18, 2017 • edited Loading

Description

Steps to reproduce

Expected behaviour

Log

smaslenko commented Dec 25, 2017 • edited Loading

dvdciri commented Dec 26, 2017

dvdciri commented Dec 26, 2017

smaslenko commented Dec 27, 2017

krissrex commented Dec 28, 2017

smaslenko commented Dec 28, 2017

juandiana commented Jan 16, 2018

BrianOdisho commented Feb 7, 2018

N-i-p-o-l commented Mar 1, 2018 • edited Loading

MarkNjunge commented Jan 11, 2019

AMK9978 commented Aug 22, 2019

N-i-p-o-l commented Oct 17, 2019

vberezkin commented Oct 23, 2019

agoztin commented Nov 28, 2019

krissrex commented Dec 18, 2017 •

edited

Loading

smaslenko commented Dec 25, 2017 •

edited

Loading

N-i-p-o-l commented Mar 1, 2018 •

edited

Loading