We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Along with #2760, we found that there is a deviation between wsproxy and other server packages: pydantic-based vs. trafaret-based local-config schema.
wsproxy
Let's migrate our local configs to pydantic.
ai.backend.typeutils
ai.backend.types
ai.backend.logging.config
wsproxy.cli.context.CLIContext
--log-level
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Along with #2760, we found that there is a deviation between
wsproxy
and other server packages: pydantic-based vs. trafaret-based local-config schema.Let's migrate our local configs to pydantic.
ai.backend.typeutils
andai.backend.types
packages.ai.backend.logging.config
to use pydantic-based schema as well.wsproxy.cli.context.CLIContext
: Let it respect the local logging configuration if present and silently fallback to a default config like other server components. (remaining of Wrong Implicit log level overridding when--log-level
argument is not provided #2759)wsproxy
.The text was updated successfully, but these errors were encountered: