exception - develop thread - log undefined

[johoja12]

on c8ddb1e

folderTree Size Before: 125115

/mnt/2TB2/sources/BitcasaF4JS/build/ls.js:607
fiber.run();
^
TypeError: Cannot call method 'log' of undefined
at Socket. (/mnt/2TB2/sources/BitcasaF4JS/node_modules/node-ipc/lib/client.js:65:20)
at Socket.emit (events.js:95:17)
at onwriteError (_stream_writable.js:238:10)
at onwrite (_stream_writable.js:256:5)
at WritableState.onwrite (_stream_writable.js:96:5)
at fireErrorCallbacks (net.js:437:13)
at Socket._destroy (net.js:448:5)
at Socket._write (net.js:637:10)
at doWrite (_stream_writable.js:225:10)
at writeOrBuffer (_stream_writable.js:215:5)
at Socket.Writable.write (_stream_writable.js:182:11)
at Socket.write (net.js:615:40)

[EricTheMagician]

Is the error reproducible?
I'm not able to find the line of code that the error is associated with.

Did you only run "ls.js" or did you use the start.sh script?

[johoja12]

Will see what happens. That was from overnight I went to the latest commit
in the dev branch will let it keep running and see if it pops up again.
On Sep 12, 2014 7:48 AM, "thejinx0r" notifications@github.com wrote:

Is the error reproducible?
I'm not able to find the line of code that the error is associated with.

—
Reply to this email directly or view it on GitHub
#26 (comment)
.

[EricTheMagician]

Did you only run "ls.js" or did you use the start.sh script?

[johoja12]

'sh start.sh' -- i'll let you know if it happens again.

On Fri, Sep 12, 2014 at 7:55 AM, thejinx0r notifications@github.com wrote:

Did you only run "ls.js" or did you use the start.sh script?

—
Reply to this email directly or view it on GitHub
#26 (comment)
.

• Saqeb Akhter

[johoja12]

Got it again:

length of folders after splicing: 0
folderTree Size Before: 125326

/mnt/2TB2/sources/BitcasaF4JS/build/ls.js:607
fiber.run();
^
TypeError: Cannot call method 'log' of undefined
at Socket. (/mnt/2TB2/sources/BitcasaF4JS/node_modules/node-ipc/lib/client.js:65:20)
at Socket.emit (events.js:95:17)
at onwriteError (_stream_writable.js:238:10)
at onwrite (_stream_writable.js:256:5)
at WritableState.onwrite (_stream_writable.js:96:5)
at fireErrorCallbacks (net.js:437:13)
at Socket._destroy (net.js:448:5)
at Socket._write (net.js:637:10)
at doWrite (_stream_writable.js:225:10)
at writeOrBuffer (_stream_writable.js:215:5)
at Socket.Writable.write (_stream_writable.js:182:11)
at Socket.write (net.js:615:40)
sakhter@sakhter-ubuntu:/sources/BitcasaF4JS/build$
sakhter@sakhter-ubuntu:/sources/BitcasaF4JS/build$

[EricTheMagician]

I can’t reproduce the error on my end, but it looks like the error is coming from one of the packages that I’m using. It seems like the error is stemming from the updater not being able to communicate with the main filesystem process.

Can you check that in your “/tmp” folder, do you have these files or entries?

 BitcasaF4JS.log

 bitcasaf4js.client

 bitcasaf4js.download0

 bitcasaf4js.download1

Eric

On Fri, Sep 12, 2014 at 1:21 PM, saqebakhter notifications@github.com
wrote:

Got it again:
length of folders after splicing: 0
folderTree Size Before: 125326
/mnt/2TB2/sources/BitcasaF4JS/build/ls.js:607
fiber.run();
^
TypeError: Cannot call method 'log' of undefined
at Socket. (/mnt/2TB2/sources/BitcasaF4JS/node_modules/node-ipc/lib/client.js:65:20)
at Socket.emit (events.js:95:17)
at onwriteError (_stream_writable.js:238:10)
at onwrite (_stream_writable.js:256:5)
at WritableState.onwrite (_stream_writable.js:96:5)
at fireErrorCallbacks (net.js:437:13)
at Socket._destroy (net.js:448:5)
at Socket._write (net.js:637:10)
at doWrite (_stream_writable.js:225:10)
at writeOrBuffer (_stream_writable.js:215:5)
at Socket.Writable.write (_stream_writable.js:182:11)
at Socket.write (net.js:615:40)
sakhter@sakhter-ubuntu:~/sources/BitcasaF4JS/build$

sakhter@sakhter-ubuntu:~/sources/BitcasaF4JS/build$

Reply to this email directly or view it on GitHub:
#26 (comment)

[EricTheMagician]

Also,
try the latest commit, there was a few bugs that I have since fixed, which may be causing the issues you are seeing.

[johoja12]

The logging files that you mentioned all exist - I'll update to the latest in dev branch, and continue to run it - will update you when I know more.

For the log files - the other files are 0 length though:

srwxrwxr-x 1 sakhter sakhter 0 Sep 13 15:47 bitcasaf4js.download1
srwxrwxr-x 1 sakhter sakhter 0 Sep 13 15:47 bitcasaf4js.download0
srwxrwxr-x 1 sakhter sakhter 0 Sep 13 15:47 bitcasaf4js.client
-rw-rw-r-- 1 sakhter sakhter 2703395 Sep 13 16:09 BitcasaF4JS.log

Is that normal ?

[EricTheMagician]

It's been running pretty smoothly for me now. I'm going to merge it in to master soon.

[johoja12]

on this commit: 74602ef

Still getting this error:

length of folders after splicing: 1
length of folders after splicing: 0
folderTree Size Before: 126810

/mnt/2TB2/sources/BitcasaF4JS/build/ls.js:607
fiber.run();
^
TypeError: Cannot call method 'log' of undefined
at Socket. (/mnt/2TB2/sources/BitcasaF4JS/node_modules/node-ipc/lib/client.js:65:20)
at Socket.emit (events.js:95:17)
at onwriteError (_stream_writable.js:238:10)
at onwrite (_stream_writable.js:256:5)
at WritableState.onwrite (_stream_writable.js:96:5)
at fireErrorCallbacks (net.js:437:13)
at Socket._destroy (net.js:448:5)
at Socket._write (net.js:637:10)
at doWrite (_stream_writable.js:225:10)
at writeOrBuffer (_stream_writable.js:215:5)
at Socket.Writable.write (_stream_writable.js:182:11)
at Socket.write (net.js:615:40)
^C
sakhter@sakhter-ubuntu:~/sources/B

[EricTheMagician]

Can you post the last few lines of the log?
Eric

On Mon, Sep 15, 2014 at 8:05 PM, saqebakhter notifications@github.com
wrote:

on this commit: 74602ef
Still getting this error:
length of folders after splicing: 1
length of folders after splicing: 0
folderTree Size Before: 126810
/mnt/2TB2/sources/BitcasaF4JS/build/ls.js:607
fiber.run();
^
TypeError: Cannot call method 'log' of undefined
at Socket. (/mnt/2TB2/sources/BitcasaF4JS/node_modules/node-ipc/lib/client.js:65:20)
at Socket.emit (events.js:95:17)
at onwriteError (_stream_writable.js:238:10)
at onwrite (_stream_writable.js:256:5)
at WritableState.onwrite (_stream_writable.js:96:5)
at fireErrorCallbacks (net.js:437:13)
at Socket._destroy (net.js:448:5)
at Socket._write (net.js:637:10)
at doWrite (_stream_writable.js:225:10)
at writeOrBuffer (_stream_writable.js:215:5)
at Socket.Writable.write (_stream_writable.js:182:11)
at Socket.write (net.js:615:40)
^C

sakhter@sakhter-ubuntu:~/sources/B

Reply to this email directly or view it on GitHub:
#26 (comment)

[johoja12]

Here's hte last few lines form the log file -

{"level":"debug","message":"api rate limit reached while getting folders","timestamp":"2014-09-15T15:22:20.715Z"}
{"level":"error","message":"there was a problem processing i=0(namespaces) - Error: 9006 - folders length - 1 - data","timestamp":"2014-09-15T15:22:20.715Z"}
{"result":null,"error":{"code":9006,"message":"API call rate limit reached."},"level":"debug","message":"the bad data was:","timestamp":"2014-09-15T15:22:20.715Z"}
{"level":"debug","message":"api rate limit reached while getting folders","timestamp":"2014-09-15T15:22:21.137Z"}
{"level":"error","message":"there was a problem processing i=0(namespaces) - Error: 9006 - folders length - 1 - data","timestamp":"2014-09-15T15:22:21.137Z"}
{"result":null,"error":{"code":9006,"message":"API call rate limit reached."},"level":"debug","message":"the bad data was:","timestamp":"2014-09-15T15:22:21.137Z"}
{"level":"debug","message":"api rate limit reached while getting folders","timestamp":"2014-09-15T15:22:21.526Z"}
{"level":"error","message":"there was a problem processing i=0(namespaces) - Error: 9006 - folders length - 1 - data","timestamp":"2014-09-15T15:22:21.526Z"}
{"result":null,"error":{"code":9006,"message":"API call rate limit reached."},"level":"debug","message":"the bad data was:","timestamp":"2014-09-15T15:22:21.526Z"}
{"level":"debug","message":"api rate limit reached while getting folders","timestamp":"2014-09-15T15:22:21.942Z"}
{"level":"error","message":"there was a problem processing i=0(namespaces) - Error: 9006 - folders length - 1 - data","timestamp":"2014-09-15T15:22:21.942Z"}
{"result":null,"error":{"code":9006,"message":"API call rate limit reached."},"level":"debug","message":"the bad data was:","timestamp":"2014-09-15T15:22:21.942Z"}
{"level":"debug","message":"api rate limit reached while getting folders","timestamp":"2014-09-15T15:22:22.358Z"}
{"level":"error","message":"there was a problem processing i=0(namespaces) - Error: 9006 - folders length - 1 - data","timestamp":"2014-09-15T15:22:22.358Z"}
{"result":null,"error":{"code":9006,"message":"API call rate limit reached."},"level":"debug","message":"the bad data was:","timestamp":"2014-09-15T15:22:22.359Z"}
{"level":"debug","message":"it took 47 minutes to update folders","timestamp":"2014-09-15T15:22:23.862Z"}

I have another problem now though

When i try to start the FS it says my token is invalid -

/mnt/2TB2/sources/BitcasaF4JS/build/fs.js:921
throw new Error("access token is not valid");
^
Error: access token is not valid
at errnoMap.EPERM (/mnt/2TB2/sources/BitcasaF4JS/build/fs.js:921:13)

And they seem to have changed the home page for https://developer.bitcasa.com/ , can't find how to request a new token

[EricTheMagician]

There was an email sent out this morning by bitcsasa

The new link is

https://consumerapi.bitcasa.com

Eric

On Mon, Sep 15, 2014 at 8:45 PM, saqebakhter notifications@github.com
wrote:

Here's hte last few lines form the log file -
{"level":"debug","message":"api rate limit reached while getting folders","timestamp":"2014-09-15T15:22:20.715Z"}
{"level":"error","message":"there was a problem processing i=0(namespaces) - Error: 9006 - folders length - 1 - data","timestamp":"2014-09-15T15:22:20.715Z"}
{"result":null,"error":{"code":9006,"message":"API call rate limit reached."},"level":"debug","message":"the bad data was:","timestamp":"2014-09-15T15:22:20.715Z"}
{"level":"debug","message":"api rate limit reached while getting folders","timestamp":"2014-09-15T15:22:21.137Z"}
{"level":"error","message":"there was a problem processing i=0(namespaces) - Error: 9006 - folders length - 1 - data","timestamp":"2014-09-15T15:22:21.137Z"}
{"result":null,"error":{"code":9006,"message":"API call rate limit reached."},"level":"debug","message":"the bad data was:","timestamp":"2014-09-15T15:22:21.137Z"}
{"level":"debug","message":"api rate limit reached while getting folders","timestamp":"2014-09-15T15:22:21.526Z"}
{"level":"error","message":"there was a problem processing i=0(namespaces) - Error: 9006 - folders length - 1 - data","timestamp":"2014-09-15T15:22:21.526Z"}
{"result":null,"error":{"code":9006,"message":"API call rate limit reached."},"level":"debug","message":"the bad data was:","timestamp":"2014-09-15T15:22:21.526Z"}
{"level":"debug","message":"api rate limit reached while getting folders","timestamp":"2014-09-15T15:22:21.942Z"}
{"level":"error","message":"there was a problem processing i=0(namespaces) - Error: 9006 - folders length - 1 - data","timestamp":"2014-09-15T15:22:21.942Z"}
{"result":null,"error":{"code":9006,"message":"API call rate limit reached."},"level":"debug","message":"the bad data was:","timestamp":"2014-09-15T15:22:21.942Z"}
{"level":"debug","message":"api rate limit reached while getting folders","timestamp":"2014-09-15T15:22:22.358Z"}
{"level":"error","message":"there was a problem processing i=0(namespaces) - Error: 9006 - folders length - 1 - data","timestamp":"2014-09-15T15:22:22.358Z"}
{"result":null,"error":{"code":9006,"message":"API call rate limit reached."},"level":"debug","message":"the bad data was:","timestamp":"2014-09-15T15:22:22.359Z"}
{"level":"debug","message":"it took 47 minutes to update folders","timestamp":"2014-09-15T15:22:23.862Z"}
I have another problem now though
When i try to start the FS it says my token is invalid -
/mnt/2TB2/sources/BitcasaF4JS/build/fs.js:921
throw new Error("access token is not valid");
^
Error: access token is not valid
at errnoMap.EPERM (/mnt/2TB2/sources/BitcasaF4JS/build/fs.js:921:13)

And they seem to have changed the home page for https://developer.bitcasa.com/ , can't find how to request a new token

Reply to this email directly or view it on GitHub:
#26 (comment)

[johoja12]

Yes - that worked, thanks. I'm not sure why your not getting the log undefined exception i'm getting though.

[EricTheMagician]

are you running anything on port 8000 by any chance?
if you are not, can you check your permissions with the “/tmp” folder?
On Mon, Sep 15, 2014 at 8:49 PM, saqebakhter notifications@github.com
wrote:

Yes - that worked, thanks. I'm not sure why your not getting the log undefined exception i'm getting though.

Reply to this email directly or view it on GitHub:
#26 (comment)