Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
It Appears That When I Use Poetry, It Recreates The Environment (Doesn'T Persist The Venv) And Redownloads All The Python Packages (Doesn'T Use A Cache). Is This How The System Currently Works, Or Are There Specific Flags And Such That I Have Not Enabled

It appears that when I use poetry, it recreates the environment (doesn't persist the venv) and redownloads all the python packages (doesn't use a cache). Is this how the system currently works, or are there specific flags and such that I have not enabled to use the cache and persist the venv for poetry?

Posted one year ago
Votes Newest

Answers 5

Should I map the poetry cache volume to a location on the host?

Yes, this will solve it! (maybe we should have that automatically if using poetry as package manager)
Could you maybe add a github issue, so we do not forget ?
Meanwhile you can add the mapping here:
extra_docker_arguments: ["-v", "/mnt/cache/poetry:/root/poetry_cache_here"]

Posted one year ago

Thank you StrangePelican34 !!!

Posted one year ago

Hi StrangePelican34 , you mean poetry as package manager of the agent? The venvs cache will only work for pip and conda, poetry handles everything internally:(

Posted one year ago

But with poetry running in a docker container, the cache is not persistent. Should I map the poetry cache volume to a location on the host?

Posted one year ago
5 Answers
one year ago
4 months ago