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

SNOW-1726666: Spurious and Unwanted Log message generated by snowflake-sdk #931

Closed
markddrake opened this issue Oct 7, 2024 · 3 comments
Assignees
Labels
status-triage_done Initial triage done, will be further handled by the driver team wontfix This will not be worked on

Comments

@markddrake
Copy link

Please answer these questions before submitting your issue.
In order to accurately debug the issue this information is required. Thanks!

  1. What version of NodeJS driver are you using?

  2. What operating system and processor architecture are you using?

  3. What version of NodeJS are you using?
    (node --version and npm --version)

  4. What are the component versions in the environment (npm list)?

5.Server version:* E.g. 1.90.1
You may get the server version by running a query:

SELECT CURRENT_VERSION();
  1. What did you do?

    If possible, provide a recipe for reproducing the error.
    A complete runnable program is good.

  2. What did you expect to see?

    What should have happened and what happened instead?

  3. Can you set logging to DEBUG and collect the logs?

    https://community.snowflake.com/s/article/How-to-generate-log-file-on-Snowflake-connectors

e.g
Add this to get standard output.

var snowflake = require('snowflake-sdk');
snowflake.configure(
{
  logLevel: 'trace'
});
  1. What is your Snowflake account identifier, if any? (Optional)
@markddrake markddrake added the bug Something isn't working label Oct 7, 2024
@github-actions github-actions bot changed the title Spurious and Unwanted Log message generated by snowflake-sdk SNOW-1726666: Spurious and Unwanted Log message generated by snowflake-sdk Oct 7, 2024
@markddrake
Copy link
Author

I get the following generated as soon as I attempt to use snowflake-sdk

{"level":"INFO","message":"[8:20:08.617 AM]: Connecting to GLOBAL Snowflake domain"}
{"level":"INFO","message":"[8:20:08.639 AM]: Trying to initialize Easy Logging"}
{"level":"INFO","message":"[8:20:08.645 AM]: No client config detected."}
{"level":"INFO","message":"[8:20:08.646 AM]: No config file path found. Client config will not be used."}
```

These messages should not appear by default...  - They mess up regression testing for starters.

My connection object looks like

{
  account: '####'
  username: '####'
  password: '####'
  warehouse: 'DEMO_WH',
  database: 'DEMO_DB',
  schema: 'PUBLIC',
  insecureConnect: true,
  arrayBindingThreshold: 10000000,
  user: undefined,
  host: undefined,
  port: undefined
}

```

@sfc-gh-dszmolka sfc-gh-dszmolka self-assigned this Oct 7, 2024
@sfc-gh-dszmolka sfc-gh-dszmolka added wontfix This will not be worked on status-triage_done Initial triage done, will be further handled by the driver team and removed bug Something isn't working labels Oct 7, 2024
@sfc-gh-dszmolka
Copy link
Collaborator

hi @markddrake i believe this is duplicate of #794 - please see this comment on options of reducing output, which we seem to be mandated to emit per our own Security team. apologies for the inconvenience.

@sfc-gh-dszmolka
Copy link
Collaborator

sfc-gh-dszmolka commented Oct 7, 2024

..would that help anything, if we were to modify the loglevel of the domain detector? (global vs china?) That's one single log line. The rest (related to Easy Logging feature) must stay I'm afraid.

edit: closing it per #794 (comment)

@sfc-gh-dszmolka sfc-gh-dszmolka closed this as not planned Won't fix, can't repro, duplicate, stale Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status-triage_done Initial triage done, will be further handled by the driver team wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants