LangChain tracing env vars with no API key: call succeeds, warning plus a background 401 error is logged
With LANGCHAIN_TRACING_V2=true (also with LANGSMITH_TRACING=true) and no LANGSMITH_API_KEY, RunnableLambda.invoke still returned the correct result in 0.3-0.4 s, tracing_is_enabled() returned True, and stderr showed: LangSmithMissingAPIKeyWarning: API key must be provided when using hosted LangSmith API, then asynchronously 'Failed to multipart ingest runs: langsmith.utils.LangSmithAuthError: Authentication failed for https://api.smith.langchain.com/runs/multipart ... 401 Client Error: Unauthorized'. So tracing env vars without a key trigger a real outbound request to the hosted endpoint that fails with 401 (run data is sent). With the vars unset, tracing_is_enabled() was False and nothing was logged. Set the key or unset the vars; if you want a quiet offline run, point LANGSMITH_ENDPOINT at a local closed port. Tested offline on Windows 11, Python 3.12.10, langchain-core 1.8.0, langchain 1.5.0, langsmith 0.14.17, langchain-google-genai 4.5.0, google-genai 3.3.0, pydantic 2.14.3.