You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
webserver_1 | Find entities
webserver_1 | { Error: ER_PARSE_ERROR: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') and is_deleted = 0 and collection_id = 1' at line 1
webserver_1 | at Query.Sequence._packetToError (/usr/src/app/node_modules/mysql/lib/protocol/sequences/Sequence.js:52:14)
webserver_1 | at Query.ErrorPacket (/usr/src/app/node_modules/mysql/lib/protocol/sequences/Query.js:77:18)
webserver_1 | at Protocol._parsePacket (/usr/src/app/node_modules/mysql/lib/protocol/Protocol.js:279:23)
webserver_1 | at Parser.write (/usr/src/app/node_modules/mysql/lib/protocol/Parser.js:76:12)
webserver_1 | at Protocol.write (/usr/src/app/node_modules/mysql/lib/protocol/Protocol.js:39:16)
webserver_1 | at Socket. (/usr/src/app/node_modules/mysql/lib/Connection.js:103:28)
webserver_1 | at emitOne (events.js:96:13)
webserver_1 | at Socket.emit (events.js:188:7)
webserver_1 | at readableAddChunk (_stream_readable.js:176:18)
webserver_1 | at Socket.Readable.push (_stream_readable.js:134:10)
webserver_1 | at TCP.onread (net.js:547:20)
webserver_1 | --------------------
webserver_1 | at Protocol._enqueue (/usr/src/app/node_modules/mysql/lib/protocol/Protocol.js:145:48)
webserver_1 | at Connection.query (/usr/src/app/node_modules/mysql/lib/Connection.js:208:25)
webserver_1 | at find (/usr/src/app/datasources/mysql.js:139:6)
webserver_1 | at findByValue (/usr/src/app/models/Entity.js:234:14)
webserver_1 | at _mFindEntities (/usr/src/app/controllers/SitesController.js:515:11)
webserver_1 | at fn (/usr/src/app/node_modules/async/lib/async.js:746:34)
webserver_1 | at /usr/src/app/node_modules/async/lib/async.js:1213:16
webserver_1 | at /usr/src/app/node_modules/async/lib/async.js:166:37
webserver_1 | at /usr/src/app/node_modules/async/lib/async.js:706:43
webserver_1 | at /usr/src/app/node_modules/async/lib/async.js:167:37
webserver_1 | code: 'ER_PARSE_ERROR',
webserver_1 | errno: 1064,
webserver_1 | sqlMessage: 'You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') and is_deleted = 0 and collection_id = 1' at line 1',
webserver_1 | sqlState: '42000',
webserver_1 | index: 0,
webserver_1 | sql: 'SELECT Entity.id,Entity.master_id,Entity.multiword,Entity.value,Entity.caption,Entity.type,Entity.show_always FROM entitiesEntity WHERE value IN () and is_deleted = 0 and collection_id = 1' }
Context: docker image of the latest build. MacbookPro, I7 lots of ram. Reading (by way of Readability) a long blog. It seems apparent that if you change web pages to do other browsing, that confuses the reader, causing it to register a new page. It seems to have returned to "The quick brown fox jumped over the lazy dog." and then printing out long reports that appear to mirror what it's reading. No clue what that sql message means.
The text was updated successfully, but these errors were encountered:
webserver_1 | Find entities
webserver_1 | { Error: ER_PARSE_ERROR: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') and
is_deleted
= 0 andcollection_id
= 1' at line 1webserver_1 | at Query.Sequence._packetToError (/usr/src/app/node_modules/mysql/lib/protocol/sequences/Sequence.js:52:14)
webserver_1 | at Query.ErrorPacket (/usr/src/app/node_modules/mysql/lib/protocol/sequences/Query.js:77:18)
webserver_1 | at Protocol._parsePacket (/usr/src/app/node_modules/mysql/lib/protocol/Protocol.js:279:23)
webserver_1 | at Parser.write (/usr/src/app/node_modules/mysql/lib/protocol/Parser.js:76:12)
webserver_1 | at Protocol.write (/usr/src/app/node_modules/mysql/lib/protocol/Protocol.js:39:16)
webserver_1 | at Socket. (/usr/src/app/node_modules/mysql/lib/Connection.js:103:28)
webserver_1 | at emitOne (events.js:96:13)
webserver_1 | at Socket.emit (events.js:188:7)
webserver_1 | at readableAddChunk (_stream_readable.js:176:18)
webserver_1 | at Socket.Readable.push (_stream_readable.js:134:10)
webserver_1 | at TCP.onread (net.js:547:20)
webserver_1 | --------------------
webserver_1 | at Protocol._enqueue (/usr/src/app/node_modules/mysql/lib/protocol/Protocol.js:145:48)
webserver_1 | at Connection.query (/usr/src/app/node_modules/mysql/lib/Connection.js:208:25)
webserver_1 | at find (/usr/src/app/datasources/mysql.js:139:6)
webserver_1 | at findByValue (/usr/src/app/models/Entity.js:234:14)
webserver_1 | at _mFindEntities (/usr/src/app/controllers/SitesController.js:515:11)
webserver_1 | at fn (/usr/src/app/node_modules/async/lib/async.js:746:34)
webserver_1 | at /usr/src/app/node_modules/async/lib/async.js:1213:16
webserver_1 | at /usr/src/app/node_modules/async/lib/async.js:166:37
webserver_1 | at /usr/src/app/node_modules/async/lib/async.js:706:43
webserver_1 | at /usr/src/app/node_modules/async/lib/async.js:167:37
webserver_1 | code: 'ER_PARSE_ERROR',
webserver_1 | errno: 1064,
webserver_1 | sqlMessage: 'You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') and
is_deleted
= 0 andcollection_id
= 1' at line 1',webserver_1 | sqlState: '42000',
webserver_1 | index: 0,
webserver_1 | sql: 'SELECT
Entity
.id
,Entity
.master_id
,Entity
.multiword
,Entity
.value
,Entity
.caption
,Entity
.type
,Entity
.show_always
FROMentities
Entity
WHEREvalue
IN () andis_deleted
= 0 andcollection_id
= 1' }Context: docker image of the latest build. MacbookPro, I7 lots of ram. Reading (by way of Readability) a long blog. It seems apparent that if you change web pages to do other browsing, that confuses the reader, causing it to register a new page. It seems to have returned to "The quick brown fox jumped over the lazy dog." and then printing out long reports that appear to mirror what it's reading. No clue what that sql message means.
The text was updated successfully, but these errors were encountered: