You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A simple local run using the pre-reqs as in README.md yields.
helicone-jawn | Error processing request 6d2df17d-7bbe-49a3-97e0-5876d52e4184 for batch : Error fetching content from S3: {"error":"Error fetching content from S3: Forbidden, 403"}
helicone-jawn | Required Kafka environment variables are not set, KafkaProducer will not be initialized.
I did not see in the documentation where Kafka was a requirement. I did not see where this is spun up either.
You also have clickhouse errors
clickhouse-migration-runner | Traceback (most recent call last):
clickhouse-migration-runner | File "ch_hcone.py", line 8, in
clickhouse-migration-runner | import tabulate
clickhouse-migration-runner | ModuleNotFoundError: No module named 'tabulate'
clickhouse-migration-runner exited with code 1
I have seen this a lot in repos where code is committed and breaks the main branch. My suggestion is the same, exercise a clean build or run in a VM following the instructions that have been outlined in the repo. Many times developers have existing packages/libraries installed where as a fresh install does not. Equally, keeping packages somewhat up to date along with n-1 on node will help.
All of this may work in your cloud offering, but it provides no confidence when the core cannot be run with following the README.md. Calls in to question if the source code is current or if the cloud offering is stagnant or put together with bubble gum and shoe string.
The text was updated successfully, but these errors were encountered:
Clickhouse migration succeeds(?) if tabulate is installed, there's a temp soln in #2965
Kafka is not supposed to be needed for local hosting but even with ^^^ I am getting the same result w.r.t KafkaProducer
What happened?
A simple local run using the pre-reqs as in README.md yields.
helicone-jawn | Error processing request 6d2df17d-7bbe-49a3-97e0-5876d52e4184 for batch : Error fetching content from S3: {"error":"Error fetching content from S3: Forbidden, 403"}
helicone-jawn | Required Kafka environment variables are not set, KafkaProducer will not be initialized.
I did not see in the documentation where Kafka was a requirement. I did not see where this is spun up either.
You also have clickhouse errors
clickhouse-migration-runner | Traceback (most recent call last):
clickhouse-migration-runner | File "ch_hcone.py", line 8, in
clickhouse-migration-runner | import tabulate
clickhouse-migration-runner | ModuleNotFoundError: No module named 'tabulate'
clickhouse-migration-runner exited with code 1
I have seen this a lot in repos where code is committed and breaks the main branch. My suggestion is the same, exercise a clean build or run in a VM following the instructions that have been outlined in the repo. Many times developers have existing packages/libraries installed where as a fresh install does not. Equally, keeping packages somewhat up to date along with n-1 on node will help.
All of this may work in your cloud offering, but it provides no confidence when the core cannot be run with following the README.md. Calls in to question if the source code is current or if the cloud offering is stagnant or put together with bubble gum and shoe string.
The text was updated successfully, but these errors were encountered: