Skip to content

SNOW-2265499: toml connection method unable to connect. User is empty error #1523

@erickdcohen

Description

@erickdcohen

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

  1. What version of GO driver are you using?

v1.15.0

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

MacOS Sequoia 15.6 | Apple M4 Pro (ARM)

  1. What version of GO are you using?
    run go version in your console

go version go1.24.5 darwin/arm64

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

SELECT CURRENT_VERSION();

9.23.1

  1. What did you do? If possible, provide a recipe for reproducing the error.
    A complete runnable program is good.

I am attempting to follow the documentation for connecting via .toml, which directs me to this example, which is what I am trying to run. I set up my connections.toml and config.toml files but keep running into the same error message:

failed to connect. 260001: user is empty,
exit status 1

Steps I took:

  1. ensured proper file path
  2. ensured proper TOML file structure, fields, and values.
  3. tried just directing to config.toml and just connections.toml
  4. ensured proper read/write access for owner (same as when running the program)
  5. ensured values work if I use a regular connection string

  1. What did you expect to see?
    What should have happened and what happened instead?

I expected the success message from fmt.Printf("Congrats! You have successfully run %v with Snowflake DB!\n", query)

But instead I see

failed to connect. 260001: user is empty,
exit status 1
  1. Can you set logging to DEBUG and collect the logs?

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

    Before sharing any information, please be sure to review the log and remove any sensitive
    information.

I can't specify the logs since it doesn't pick-up my config.toml file

Metadata

Metadata

Labels

bugErroneous or unexpected behaviourstatus-pr_pending_mergeA PR is made and is under reviewstatus-triage_doneInitial triage done, will be further handled by the driver team

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions