Skip to content

Conversation

bparees
Copy link
Contributor

@bparees bparees commented Aug 8, 2025

No description provided.

@bparees bparees changed the title Use llamastack model identifier, not provider resource id, to refer to a model DO NOT MERGE: Use llamastack model identifier, not provider resource id, to refer to a model Aug 8, 2025
@bparees
Copy link
Contributor Author

bparees commented Aug 8, 2025

this change needs to be coordinated with lightspeed-core/lightspeed-stack#368

@bparees
Copy link
Contributor Author

bparees commented Aug 11, 2025

@eyevana i'm not sure what the merge process is for this repo, but we need to make sure this doesn't actually merge until we resolve some conversations and resolve/merge the changes in lightspeed-core/lightspeed-stack#368

@eyevana
Copy link
Collaborator

eyevana commented Aug 11, 2025

@bparees yes, I'm holding off until I get the green-light from you. @jrobertboos correct me if I'm wrong, but the merge process is pretty informal right? Do you communicate with anyone/team when fixes are applied in the main branch?

@bparees
Copy link
Contributor Author

bparees commented Aug 12, 2025

github issue for the upstream llamastack behavior aspects of this:
llamastack/llama-stack#3116

@jrobertboos
Copy link
Collaborator

Hi @eyevana and @bparees, sorry for the delayed response I have been out backpacking since Saturday :). Yea the merge process for this repo is really informal, I don't really have to communicate with anyone about patches or fixes, for larger changes I will often times let the LCORE team take a look or demo the new feature/change.

@bparees
Copy link
Contributor Author

bparees commented Aug 26, 2025

i've opened https://issues.redhat.com/browse/LCORE-600 to track resolving this behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants