-
Notifications
You must be signed in to change notification settings - Fork 33
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
use langsmith env vars #373
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
pr doesn't touch:
imo these should also be updated to use LANGSMITH prefix but seems like bigger change? |
@@ -88,8 +88,8 @@ for input_prompt, output_answer in example_inputs: | |||
)`), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need to update old docs, not sure when support was added anyway
@@ -26,9 +26,9 @@ If you are using LangChain (either Python or JS/TS), you can skip this section a | |||
LangSmith makes it easy to log traces with minimal changes to your existing code with the `@traceable` decorator in Python and `traceable` function in TypeScript. | |||
|
|||
:::note | |||
The `LANGCHAIN_TRACING_V2` environment variable must be set to `'true'` in order for traces to be logged to LangSmith, even when using `@traceable` or `traceable`. This allows you to toggle tracing on and off without changing your code. | |||
The `LANGSMITH_TRACING` environment variable must be set to `'true'` in order for traces to be logged to LangSmith, even when using `@traceable` or `traceable`. This allows you to toggle tracing on and off without changing your code. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bearing in mind recent feedback about things changing without warning - can we add a callout documenting that the old variables will still work?
It looks like
|
I would change in the SDK first, let it bake a while, then change docs later |
The changes in the SDK should bw-compat, the older env vars should still be respected |
Updates:
not sure all of these actually work across py and js