Eugene K in #general: "Just a quick question: what's the typical ETA on review to understand if any code fixes are required or it's good to go? These 3 are pending. Feel fre..." | Archestra Community

#general

May 31June 1, 2026Jun 2 Latest

https://github.com/archestra-ai/archestra/issues/5036

Here need guidance from the team - what's the best solution here, cuz changing the model's characteristic leads to undefined behaviour

3 replies

Eloy BJ5:37 PMOpen in Slack

Hello, I'm Eloy, and I'd like to contribute in the project 👀

Yanis7:35 PMOpen in Slack

Hello everyone ! I'm Yanis. I've been working as a Software Engineer (AI focused) for nearly a year now, I've been dealing with MCPs for the major part of it. I found this gem of a software and it's clear to me just by reading the docs that you guys understand the problems you're solving very well.

I like what you guys are doing, i'd love to contribute despite my relative lack of experience. This project uses a tech stack I am not familiar with, so I will probably spend more time learning than implementing. If you think I could pick up a non-urgent issue to sink my teeth into, i'd love to contribute.

Thanks.

Eugene K9:17 PMOpen in Slack

Just a quick question:

what's the typical ETA on review to understand if any code fixes are required or it's good to go? These 3 are pending. Feel free to close them if you decide that issues are not worth fixing, thx

https://github.com/archestra-ai/archestra/pull/5075

https://github.com/archestra-ai/archestra/pull/5179

https://github.com/archestra-ai/archestra/pull/5177

Read-only live mirror of Archestra.AI Slack

👋Join the discussion withAI enthusiasts!