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

Index out of range error on running tests #55

Open
criticalboot opened this issue Dec 30, 2016 · 1 comment
Open

Index out of range error on running tests #55

criticalboot opened this issue Dec 30, 2016 · 1 comment

Comments

@criticalboot
Copy link

criticalboot commented Dec 30, 2016

tests are failing with index out of range error.
update :
when running example.js (node example.js)

=== TableMap ===
Date: Wed Dec 28 2016 12:04:48 GMT+0530 (IST)
Next log position: 6376
Event size: 56
Table id: 113
Schema: test
Table: testTable
Columns: 12
Column types: [ 3, 15, 3, 3, 15, 16, 15, 3, 3, 17, 3, 17 ]
app/node_modules/zongji/node_modules/mysql/lib/protocol/Parser.js:77
throw err; // Rethrow non-MySQL errors
^
RangeError: index out of range
at checkOffset (buffer.js:642:11)
at Buffer.readInt32BE (buffer.js:807:5)
at readIntBE (app/node_modules/zongji/lib/common.js:206:24)
at Object.exports.readMysqlValue (app/node_modules/zongji/lib/common.js:522:21)
at readRow (app/node_modules/zongji/lib/rows_event.js:113:16)
at WriteRows.RowsEvent._fetchOneRow (app/node_modules/zongji/lib/rows_event.js:95:10)
at WriteRows.RowsEvent (app/node_modules/zongji/lib/rows_event.js:64:27)
at new WriteRows (app/node_modules/zongji/lib/rows_event.js:123:13)
at BinlogHeader.parse (app/node_modules/zongji/lib/packet/binlog_header.js:47:23)
at Protocol._parsePacket (app/node_modules/zongji/node_modules/mysql/lib/protocol/Protocol.js:262:12)

@java168
Copy link

java168 commented May 24, 2017

i got exactly the same error as you when using Azure Database for MySQL server - PREVIEW (mine is wp_logs from wordpress)
i deleted the service and re-created a new one. the issue went away. i don't know if the service had cached some tables information which i deleted that caused this issue. my local mysql server worked just ok.

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

2 participants