Anthony Lapenna
Anthony Lapenna
Yep, that's something we'll look to add after our beta release!
Thanks for the feedback @olljanat One advantage of having direct Swarm support is that we don't have to re-implement any form of orchestration, such as container scheduling on nodes. The...
Hey @shanduur, I see that you have already opened a PR, that's great! Before we actually go further into review, I'd like you to give us more information about the...
@shanduur amazing contribution, I'll review it soon !
Yep I reckon that is a bit of a problem right now when using Canopy. I've been experimenting with it to upsert data using it as a library and I...
I've been using this approach to upsert data using canopy as a SDK (following https://github.com/pinecone-io/canopy/blob/main/examples/canopy-lib-quickstart.ipynb): ``` for file_path in file_paths: print(f"Processing: {file_path}") data = pd.read_json(file_path, lines=True) # Convert the data...
@diegovilar don't worry about codeclimate. cc @itsconquest for functional review first
@corani see the discussions in https://github.com/mark3labs/mcp-go/pull/87 and https://github.com/mark3labs/mcp-go/pull/140 about error handling. TLDR: use `NewToolResultError` and `NewToolResultErrorFromErr` to propagate the error back to the LLM. Looks like I forgot to update...
That's also my current understanding yep
@pull-dog down