Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some errors thrown as exceptions rather than being passed to parseXlsx's callback #14

Open
addrummond opened this issue May 30, 2013 · 6 comments

Comments

@addrummond
Copy link

Unfortunately I'm not familiar enough with the promise library to be able to see how to fix this yet, but it seems that some errors get thrown as exceptions rather than being passed to the callback given to parseXlsx. For example, if you give parseXslx the path of a nonexistent file, an ENOENT exception is thrown. The intended behavior is (presumably?) for such errors to be passed on to the callback.

var parseXlsx = require('excel');

parseXlsx('nonexistent-file', function () {
    console.log(arguments);
});

======> Throws exception
@SreekeshOkky
Copy link

I was trying this

My app.js

var express = require('express'); //Call Express module
var app = express(); //Create server
var parseXlsx = require('excel');

    parseXlsx('Sheet.xlsx', function(err, data) {
        console.log('sdf');
        if(err) throw err;
        // data is an array of arrays
        console.log(data);
    });

app.listen(3003);

But I'm getting error

/home/local/user/Desktop/sample/node_modules/excel/node_modules/node-promise/promise.js:199

      throw error;
            ^

Error: invalid signature: 0x4acf92ad (at position: 0x29)
at /home/local/user/Desktop/sample/node_modules/excel/node_modules/unzip/lib/parse.js:56:13
at /home/local/user/Desktop/sample/node_modules/excel/node_modules/unzip/node_modules/pullstream/pullstream.js:101:11
at process._tickCallback (node.js:415:13)

How to fix this issue? My file is existing i crosschecked it. My xlsx file is in the same folder as app.js

@amakhrov
Copy link
Contributor

It's the issue with the old 'unzip' library version used - it doesn't support zip format used by LibreOffice and Google Docs for producing XLSX

@kbanman
Copy link

kbanman commented Nov 19, 2013

I'm running into this error as well. Would it be possible to get around this by using a different unzip library?

@amakhrov
Copy link
Contributor

I believe a new unzip lib is used already - could you confirm you use the most recent versions of excel module? If yes, could you post the error output here?

@seti123
Copy link

seti123 commented Mar 10, 2014

+1 invalid signature: 0x20726176

/node_modules/excel/node_modules/node-promise/promise.js:204
throw error;

/node_modules/excel/node_modules/unzip/lib/parse.js:63:13
at process._tickCallback (node.js:415:13)

@kgillespieatmosphere
Copy link

Downloading Bootloader ... **** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. **** Downloading DCT ... **** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. **** Downloading Application ... **** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. **** Build complete

I am able to build and install on the same development board using 3.1.2 I've sent a bug ticket to BCM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants