Skip to content
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

Ollama latest broken with the latest beta of Microsoft.Extensions.AI #492

Closed
JohnGalt1717 opened this issue Feb 20, 2025 · 6 comments · Fixed by #500
Closed

Ollama latest broken with the latest beta of Microsoft.Extensions.AI #492

JohnGalt1717 opened this issue Feb 20, 2025 · 6 comments · Fixed by #500
Assignees

Comments

@JohnGalt1717
Copy link

Describe the bug

It causes a fail to startup any models that you add because Microsoft.Extensions.AI removed metadata.

Regression

No response

Steps to reproduce

Use the latest beta of Microsoft.Extensions.AI in your project(s) and add ollama and then add a model (any model) and it will fail to start up the model in the Dashboard with an error about the metatdata property being missing.

Expected behavior

Should startup normally and be updated to use the new version of Microsoft.Extensions.AI

Screenshots

No response

IDE and version

VS 2022, Rider

IDE version

No response

Nuget packages


Additional context

No response

Help us help you

No, just wanted to report this

@aaronpowell
Copy link
Member

Do you mean the NuGet version 9.3.0-preview.1.25114.11?

@JohnGalt1717
Copy link
Author

Yes.

@aaronpowell
Copy link
Member

Our package hasn't been updated to use it, so there's likely API changes we aren't compatible with. We'll look to update it this week.

@JohnGalt1717
Copy link
Author

Why is the Ollama package depending upon Microsoft.Exentensions.AI at all?

I mean the purpose should be to get an Ollama client, which if you want, you can then take and make into an IChatClient without any assistance from Aspire at all.

And given how much they're messing with Microsoft.Extensions.AI right now, it isn't fit for consumption in anything beyond play projects so I'd suggest that the core issue is that this shouldn't be in the package.

@aaronpowell
Copy link
Member

OllamaSharp provides integration with MEAI, so we are going to have that as a dependency none the less.

Both the OpenAI and Azure.OpenAI integrations from the Aspire team support integration with MEAI, so it makes sense to be aligned with them.

@aaronpowell aaronpowell self-assigned this Feb 25, 2025
aaronpowell added a commit that referenced this issue Feb 25, 2025
aaronpowell added a commit that referenced this issue Feb 25, 2025
@JohnGalt1717
Copy link
Author

Ok, well this is very problematic because of the massive changes that they're making and how fast they're making them.

It breaks code right now and there aren't even any warnings about packages being incompatible as it currently stands.

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 a pull request may close this issue.

2 participants