Rohit Amarnath comments

Results 38 comments of


                                            Rohit Amarnath

[Question]: node_content is serialized within metadata and hence stored in the database

Hmm, maybe we need to create RelatedNodeInfo instead of the actual source Node instead?

[Question]: node_content is serialized within metadata and hence stored in the database

Even with RelatedNodeInfo, the node_content can get large if there are many related nodes (parent-child) for example. Do related nodes need to be fully encapsulated in node content? Could rated...

Race condition when two libraries update the same init.py

That makes sense, pyjwt adds functionality to jwt, so its update to the __init__.py should probably come after. Is there a way to force a dependency? If it were possible...

Race condition when two libraries update the same init.py

Could the warning be surfaced, so it's clearer that one is clobbering the other? Agreed on the package behavior, but such is life with dependence on third party libs... And...

Race condition when two libraries update the same init.py

Also, thank you @zanieb for identifying the issue so quickly.

Race condition when two libraries update the same init.py

After looking at what my options around working around this while sticking with "sync" type workflow, and was hoping to use `uv lock` and then `uv sync --no-install-package pyjwt` instead...

Race condition when two libraries update the same init.py

I do (I set managed=false in the pyproject.toml) - because our existing docker images use /opt/venv, and was trying to avoid changing that. But I think I will move stuff...

Race condition when two libraries update the same init.py

Ok I have it working with this Dockerfile and uv.lock ``` ROM python:3.12.3 AS build ENV PATH="/app/.venv/bin:$PATH" ENV VIRTUAL_ENV="/app/.venv" # Python runtime dependencies RUN apt-get update && apt-get install -y...

Race condition when two libraries update the same init.py

I would like to request a feature for future uv noobs, that warns when a library clobbers another one, I spent a fair bit of time going thru a number...

Race condition when two libraries update the same init.py

could there be an option - `uv add --depends_on ` which would update the uv.lock to install that package after the main_package?