DO NOT MERGE: Use llamastack model identifier, not provider resource id, to refer to a model#6
DO NOT MERGE: Use llamastack model identifier, not provider resource id, to refer to a model#6bparees wants to merge 1 commit into
Conversation
bparees
changed the title
|
this change needs to be coordinated with lightspeed-core/lightspeed-stack#368 |
|
@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 |
|
@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? |
|
github issue for the upstream llamastack behavior aspects of this: |
|
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. |
|
i've opened https://issues.redhat.com/browse/LCORE-600 to track resolving this behavior. |
3 participants
No description provided.