Currently we don't support clustered clickhouse so we should remove the
ability to configure it(most people use clustered clickhouse unless on
clickhouse cloud!)
Bumps [orjson](https://github.com/ijl/orjson) from 3.9.14 to 3.9.15.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/ijl/orjson/releases">orjson's
releases</a>.</em></p>
<blockquote>
<h2>3.9.15</h2>
<h3>Fixed</h3>
<ul>
<li>Implement recursion limit of 1024 on
<code>orjson.loads()</code>.</li>
<li>Use byte-exact read on <code>str</code> formatting SIMD path to
avoid crash.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/ijl/orjson/blob/master/CHANGELOG.md">orjson's
changelog</a>.</em></p>
<blockquote>
<h2>3.9.15 - 2024-02-23</h2>
<h3>Fixed</h3>
<ul>
<li>Implement recursion limit of 1024 on
<code>orjson.loads()</code>.</li>
<li>Use byte-exact read on <code>str</code> formatting SIMD path to
avoid crash.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/ijl/orjson/commit/a348f59f0b55d92a1364523560f52f5b3cf9c12a"><code>a348f59</code></a>
3.9.15</li>
<li><a
href="https://github.com/ijl/orjson/commit/b0e4d2c06ce06c6e63981bf0276e4b7c74e5845e"><code>b0e4d2c</code></a>
yyjson 0eca326, recursion limit</li>
<li><a
href="https://github.com/ijl/orjson/commit/5067eadc84cf516e4eb33bcb09ad756bb59dc42e"><code>5067ead</code></a>
impl_escape_unchecked() byte exact read</li>
<li><a
href="https://github.com/ijl/orjson/commit/e04ea735b087742b6cee738aa295d8b835c3a195"><code>e04ea73</code></a>
cargo update, build misc</li>
<li>See full diff in <a
href="https://github.com/ijl/orjson/compare/3.9.14...3.9.15">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the
[Security Alerts
page](https://github.com/langchain-ai/langsmith-sdk/network/alerts).
</details>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
use saq
Add configurable values everywhere
fix env vars
fix env vars
fix env vars
feat: Peg docker compose version and use new image names
update template
update template
update template
update template
update template
fmt
- Call info within tracing queue
- Default to batching even if info endpoint fails
If you turn batching off, you have to make your own tracer / traceable
flow that handles threading yourself now.
This lets you scope hide inputs/outputs to a client. It also lets you
add custom filters (rather than just masking everything.
You could then use this in the traceable decorator or langchain tracer
to filter runs within a given trace.
It would _not_ facilitate filtering on a span level though, since it
only sees the inputs/outputs and the client is shared within a trace.
Alternatives could include a single function (filter_run) that takes in
a Run object, though then we'd have to re-construct the run within the
client, which is a bit annoying
So you get linter warnings if you try to do a name. It doesn't actually
alter the behavior, so if we choose to extend the number of types, it
would just be a linting issue rather than a runtime issue
langchain-infra