-
Notifications
You must be signed in to change notification settings - Fork 16.9k
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
multiple: get rid of pyproject extras #22581
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
…/langchain into erick/uv-extended-test-deps
@@ -75,7 +75,7 @@ def _convert_run_to_wb_span(self, run: Run) -> "Span": | |||
:return: The converted Span. | |||
""" | |||
attributes = {**run.extra} if run.extra else {} | |||
attributes["execution_order"] = run.execution_order | |||
attributes["execution_order"] = run.execution_order # type: ignore |
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.
should maybe just remove?
@@ -220,7 +220,7 @@ def _pull_queue(self) -> None: | |||
data = MessageToJson( | |||
pb, | |||
preserving_proto_field_name=True, | |||
including_default_value_fields=True, | |||
including_default_value_fields=True, # type: ignore |
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.
should maybe be MessageToDict
?
# Metadata creation with duckdb raises 3 warnings at the moment about reflection. | ||
# As a stop-gap to increase strictness of pytest to fail on warnings, we'll | ||
# explicitly catch the warning and assert that it's the one we expect. | ||
# explicitly catch the warnings and assert that it's the one we expect. | ||
# We may need to revisit at a later stage and determine why a warning is being | ||
# raised here. | ||
assert len(records) == 1 | ||
assert len(records) == 3 |
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.
new versions of duckdb raise 3 warnings about data types
@@ -1,3 +1,5 @@ | |||
# type: ignore |
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.
type-ignoring pydantic files necessary with new mypy version
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.
some new version of sqlalchemy/duckdb throws 2 additional warnings. We just want to check that the duckdb one is there per #3653
They cause `poetry lock` to take a ton of time, and `uv pip install` can resolve the constraints from these toml files in trivial time (addressing problem with #19153) This allows us to properly upgrade lockfile dependencies moving forward, which revealed some issues that were either fixed or type-ignored (see file comments)
They cause
poetry lock
to take a ton of time, anduv pip install
can resolve the constraints from these toml files in trivial time (addressing problem with #19153)This allows us to properly upgrade lockfile dependencies moving forward, which revealed some issues that were either fixed or type-ignored (see file comments)