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-1964327: HOME is blank log messages are appearing after updating from 1.13.0 to 1.13.1 #1325

Open
horgh opened this issue Mar 5, 2025 · 2 comments
Assignees
Labels
bug Erroneous or unexpected behaviour status-triage_done Initial triage done, will be further handled by the driver team

Comments

@horgh
Copy link

horgh commented Mar 5, 2025

  1. What version of GO driver are you using?

1.13.1

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

Linux x86_64

  1. What version of GO are you using?

go version go1.24.1 linux/amd64

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

SELECT CURRENT_VERSION();

Not sure it's relevant, so I'm omitting.

  1. What did you do?

I ran a pre-existing program that updates tables in a snowflake database.

  1. What did you expect to see?

No log messages.

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

Not sure if it's relevant so I'm omitting.

Summary:

After updating to 1.13.1 from 1.13.0, my application is generating log messages like:

INFO[0000]log.go:244 gosnowflake.(*defaultLogger).Info HOME is blank

Since this seems to happen in init(), I'm not sure I can hide it.

Potentially I need to create a HOME for the application to use, which presumably would solve it too. However if things would continue to work without a HOME, then it would be nice to be able to hide this log message.

@horgh horgh added the bug Erroneous or unexpected behaviour label Mar 5, 2025
@github-actions github-actions bot changed the title HOME is blank log messages are appearing after updating from 1.13.0 to 1.13.1 SNOW-1964327: HOME is blank log messages are appearing after updating from 1.13.0 to 1.13.1 Mar 5, 2025
@sfc-gh-dszmolka sfc-gh-dszmolka added the status-triage_done Initial triage done, will be further handled by the driver team label Mar 6, 2025
@sfc-gh-dszmolka
Copy link
Contributor

hello - thank for submitting this issue with us ! seems to come from #1295 and happens in secure_storage_manager when determining the cache directory where the temp credential storage should be put.

Indeed can be either worked around with setting HOME as you pointed out :) no other solution for now because as you pointed out, logging message happens sooner than logger configuration.

We'll take a look.

@sfc-gh-pfus
Copy link
Collaborator

Hi @horgh ! It's me who you should blame ;) Sorry for that!
We are in the middle of refactoring token cache to make it more secure. In the final version this log shouldn't be present.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Erroneous or unexpected behaviour status-triage_done Initial triage done, will be further handled by the driver team
Projects
None yet
Development

No branches or pull requests

4 participants