Parker Duckworth

> [Documentation only mentions the existing levels](https://weaviate.io/developers/weaviate/config-refs/env-vars), how do I update it? @amourao here is the repo: https://github.com/weaviate/weaviate-io You can just submit a PR there

Closed by #4155

> When this process is interrupted by an instance killed for example, there is no chance to persist the in-flight data. It can make sense to reduce the amount of...

Very nice @litlig everything looks in order. Will have this merged in shortly

@abhishek818 hello :) The bounty program is still active, we are just a bit behind on reviews. The existing PRs will be addressed shortly.

Hey, thanks for taking interest in the project, and sorry for the wait 🙂 I'm not sure I agree that using `errors.New` here in place of `fmt.Errorf` is any better,...

@iSuslov the intention of making this package a CommonJS library is to keep backwards compatibility with the projects who previously used the CommonJS JavaScript client which this client was migrated...

Hey @maxilie we have since made some changes to the way the client is build and distributed. Can you try out [v1.3.0](https://www.npmjs.com/package/weaviate-ts-client/v/1.3.0) and see if it fits your needs?

@maxilie @iSuslov I am totally fine with whichever solution fixes this problem. We can stop using tsup as well, if there are better alternatives. The only concern is to maintain...

Hey @dirkkul, is this issue already satisfied [here](https://github.com/weaviate/weaviate-javascript-client/blob/main/ci/run_dependencies.sh#L14-L31)? ```sh for port in $(all_weaviate_ports); do # pulling all images usually takes < 3 min # starting weaviate usually takes < 2...