codeforpdx / codeforpdx/tenantfirstaid
Error: ALTS creds ignored. Not running on GCP and untrusted ALTS is not enabled.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 21
- Avg merge
- 6d 7h
- Merged PRs (30d)
- 3
Description
Seen several times whenever the google creds are used to authorize (meaning every time a query is run to vertex ai / gemini:
Sep 26 17:39:31 tenantfirstaid-1749072910637-s-2vcpu-2gb-sfo3-01 uv[2572321]: E0000 00:00:1758908371.153382 2572321 alts_credentials.cc:93] ALTS creds ignored. Not running on GCP and untrusted ALTS is not enabled.
Sep 26 17:39:31 tenantfirstaid-1749072910637-s-2vcpu-2gb-sfo3-01 uv[2572321]: E0000 00:00:1758908371.205673 2572321 alts_credentials.cc:93] ALTS creds ignored. Not running on GCP and untrusted ALTS is not enabled.
Doesn't seem to cause unwanted behavior, and this reddit post has a comment saying:
This behavior is caused by a new log message introduced in grpcio version 1.75.0. You can find the specific change in [this commit on GitHub](https://github.com/grpc/grpc/commit/91700c036d920ecf271632710f87f607f339693d#diff-19356ee4274828b67c23eb6293909d2c98513279f53acc01386fe5f06e87326fR93).
Interestingly, the log was implemented with an "error" severity level, even though its content may not indicate a critical failure.
You can suppress this log message by setting the GRPC_VERBOSITY environment variable to NONE.
GRPC_VERBOSITY=NONE
Recommend setting this env var to suppress the error.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the environment or configuration used when Google credentials authorize Vertex AI/Gemini queries, then verify how grpcio logging is configured. Done means the unwanted ALTS message no longer appears during those queries without changing their behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, grpc, python
- Domain
- ai, backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100