Bug #99869 | (node:73847) Warning: Accessing non-existent property 'serverGoneMessageId' of m | ||
---|---|---|---|
Submitted: | 15 Jun 2020 8:18 | Modified: | 5 Aug 2020 22:32 |
Reporter: | Zhilin Wang | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector for Node.js | Severity: | S3 (Non-critical) |
Version: | 8.0.20 | OS: | MacOS (10.15) |
Assigned to: | CPU Architecture: | Any |
[15 Jun 2020 8:18]
Zhilin Wang
[17 Jun 2020 9:48]
MySQL Verification Team
[arhimed@localdev msb_ndb8_0_20]$ node keetah.js { auth: 'SHA256_MEMORY', pooling: false, ssl: false, host: 'localhost', user: 'msandbox', port: '18020', dbUser: 'msandbox', socket: undefined } ^C [arhimed@localdev msb_ndb8_0_20]$ cat keetah.js const mysqlx = require('@mysql/xdevapi'); const options = { host: 'localhost', user: 'msandbox', password: 'msandbox', port: '18020', ssl: false }; mysqlx.getSession(options) .then((session) => { console.log(session.inspect()); // { host: 'localhost', ssl: true } }); [arhimed@localdev msb_ndb8_0_20]$
[17 Jun 2020 9:51]
MySQL Verification Team
same connecting to replication master: [arhimed@localdev msb_ndb8_0_20]$ node keetah.js { auth: 'PLAIN', pooling: false, ssl: true, host: 'localhost', user: 'msandbox', port: '30920', dbUser: 'msandbox', socket: undefined } ^C [arhimed@localdev msb_ndb8_0_20]$ vi keetah.js [arhimed@localdev msb_ndb8_0_20]$ node keetah.js { auth: 'SHA256_MEMORY', pooling: false, ssl: false, host: 'localhost', user: 'msandbox', port: '30920', dbUser: 'msandbox', socket: undefined } ^C
[17 Jun 2020 9:52]
MySQL Verification Team
Hi, I'm not sure what type of error you are reporting but your "test case" works ok both on stand alone and replication setup with 8.0 Thanks Bogdan
[18 Jun 2020 1:27]
Zhilin Wang
it's a warning, 'serverGoneMessageId' does not exist.
[18 Jun 2020 7:38]
MySQL Verification Team
Hi, Yes, I know it is a warning but I'm not getting it. Now, I'm not nodejs expert so maybe there's something else I can add to the call to get "more warnings" ? [arhimed@localdev msb_ndb8_0_20]$ node keetah.js { auth: 'SHA256_MEMORY', pooling: false, ssl: false, host: 'localhost', user: 'msandbox', port: '18020', dbUser: 'msandbox', socket: undefined } ^C [arhimed@localdev msb_ndb8_0_20]$ NODE_NO_WARNINGS=0 node keetah.js { auth: 'SHA256_MEMORY', pooling: false, ssl: false, host: 'localhost', user: 'msandbox', port: '18020', dbUser: 'msandbox', socket: undefined } ^C [arhimed@localdev msb_ndb8_0_20]$
[29 Jun 2020 18:55]
Wolfgang Gassler
I can reproduce the issue. The warning is shown several times when using node 14 (default docker image), but is not shown when using node 12 (default docker image).
[29 Jun 2020 19:07]
Wolfgang Gassler
test.js file: const mysqlx = require('@mysql/xdevapi'); const options = { host: 'db', user: 'test', password: 'test', port: '33060'}; mysqlx.getSession(options) .then((session) => { console.log(session.inspect()); }); docker-compose.yml: version: "3.7" services: db: image: mysql:8 environment: MYSQL_DATABASE: test MYSQL_USER: test MYSQL_ROOT_PASSWORD: test MYSQL_PASSWORD: test node: image: node:14 volumes: - ./test.js:/tmp/test/test.js command: "bash -c 'cd /tmp/test && yarn add @mysql/xdevapi && node test.js'" when running with node 14: node_1 | (node:1) Warning: Accessing non-existent property 'serverGoneMessageId' of module exports inside circular dependency node_1 | (Use `node --trace-warnings ...` to show where the warning was created) node_1 | (node:1) Warning: Accessing non-existent property 'serverGoneMessageId' of module exports inside circular dependency node_1 | (node:1) Warning: Accessing non-existent property 'serverGoneMessageId' of module exports inside circular dependency node_1 | (node:1) Warning: Accessing non-existent property 'serverGoneMessageId' of module exports inside circular dependency node_1 | (node:1) Warning: Accessing non-existent property 'serverGoneMessageId' of module exports inside circular dependency
[30 Jun 2020 5:41]
MySQL Verification Team
Hi, Thanks for the follow-up, my bad, I had TLS version running, not the 14! Not sure if the issue is inside connector or something with node but I'm verifying this so that the connectors team can have a stab at it. Thanks Bogdan
[5 Aug 2020 22:32]
Philip Olson
Posted by developer: Fixed as of the upcoming MySQL Connector/Node.js 8.0.22 release, and here's the proposed changelog entry from the documentation team: Added a SERVER_GONE error handler to avoid potential circular dependency warnings with Node.js >= 14.0.0. Thank you for the bug report.
[8 Dec 2020 7:20]
Shannon Palmer
A scheme is sorted for the statement of the bug from the system. The implication of the tunes and https://papernow.org/assignment-help is scene oriented or us. The skills are shining for the margin of the placement for the width for the support for the team.