-
Notifications
You must be signed in to change notification settings - Fork 19
Add AWS Bedrock Provider #2
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
Comments
/bounty $750 |
💎 $750 bounty • Golem CloudSteps to solve:
❗ Important guidelines:
Thank you for contributing to golemcloud/golem-llm!
|
what should the short demo video include? Is it just a recording of the changes? |
/attempt #2 I am new to it and will try my best on implementing. I have understood the current working of the llms here and We need to have a similar type for the aws bedrock too right ?? |
In the video you can explain the changes and show that it works running all the (currently 6) test cases of the The PR should add a new module similar to the existing ones, and ideally should not touch the existing code at all. |
/attempt #2 |
1 similar comment
/attempt #2 |
/attempt #2 |
/attempt #2 |
/attempt #2 |
@vigoo Goodday, I'm currently trying to run the tests in the golem-llm-main repo on my local machine using WSL (Windows Subsystem for Linux) and I'm hitting a wall with worker/dependency issues. Here’s my setup: Golem v1.2.1 Installed golem-x86_64-unknown-linux-gnu Running inside WSL on Windows Installed all required dependencies: Rust cargo-component v0.20 wac Target wasm32-wasip1 my server is up and running to through
I was able to deploy test:helper successfully with:
Then I tried deploying test:llm with:
However, when I attempt to create a worker, I encounter the following error:
This issue seems to be related to the golem:durability/durability@1.2.0 component missing in the linker. I don't know if i skipped a step during my installation but Any guidance or suggestions would be much appreciated! Thanks in advance. |
/attempt #2 |
No description provided.
The text was updated successfully, but these errors were encountered: