exit code 3 troubleshooting about meteor-google-spreadsheets HOT 5 CLOSED

@1jerry I'll take a look in a few days (I'm traveling), unless anyone else can take a look. Maybe we could add some logging options to help debug, although it sounds like it might be crashing before a log would capture the issue. Is there more output after "=> Exited with code: 3." on the console?

from meteor-google-spreadsheets.

The very next output is my debugging messages that indicates Meteor has
restarted. The log message on the very next line of code after calling
fetch2 never appears.
Thanks for the reply.

Jerry

On Fri, May 22, 2015 at 7:51 AM, Aaron Judd notifications-at-github.com
|git-73ry| [email protected] wrote:

@1jerry https://github.com/1jerry I'll take a look in a few days (I'm
traveling), unless anyone else can take a look. Maybe we could add some
logging options to help debug, although it sounds like it might be crashing
before a log would capture the issue. Is there more output after "=> Exited
with code: 3." on the console?

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

from meteor-google-spreadsheets.

After doing further research, including looking at the node-google-spreadsheets issues, I think the issue relates to Google making some kind of change on April 20. It is very strange that my spreadsheet of 300 rows of test data still works. This has come at a bad time for me because I was ready to create my "live" website, but I cannot get the data into it!

One other big note, which I forgot about before: I have frozen the version to 0.1.0 for two reasons: 1) all the newer version don't work with Windows (I'll make a separate issue), and 2) it worked. Unfortunately, moving my app to Linux and updating to your current 0.4.0 version didn't work either, with different errors. The Linux error was:

(STDERR) FATAL ERROR: CALL_AND_RETRY_0 Allocation failed - process out of memory
=> Exited from signal: SIGABRT*

This is also odd since I watched the memory usage with ps and it never even got close to half my available memory! Loading my 300 row test data set also works on Linux.

I also tried sharing my document publicly and using the fetch read-only method (which I've used successfully before - thanks for the package by the way). Now it gets errors too: Cannot read property 'title' of undefined. This error at least help be track down a possible Google API change.

All this sounds outside of your code, but hopefully will help track down the underlying issue(s) so it can work again.

from meteor-google-spreadsheets.

@aaronjudd Thanks for writing this tutorial! How exactly should the google-key.pem (re: step 6 below) file look when given a json file? Do you think you could provide an example with the tutorial?

Your service account should have a private key associated. Save that private key into a file named "google-key.pem" in your app's "private" folder. You might be given the key within a JSON file, in which case you need to extract and parse it into the separate PEM file (replace "\n" with actual line breaks, etc.).

from meteor-google-spreadsheets.

@wrichman to be honest, I'd have to re-research it. If you have any suggestions, happy to add/edit the tutorial.

from meteor-google-spreadsheets.