-
Notifications
You must be signed in to change notification settings - Fork 21
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
Cannot use semantic search bindings in .NET 8 #24
Comments
Your sample project targets .NET in-proc, so this is mostly expected. For the benefit of anyone else who lands here, per the .NET 8 announcement, Azure Functions doesn't yet support .NET 8 using the in-proc model.
In the meantime, we need to create a .NET isolated version of these bindings so that we can support .NET 8 users on the .NET Isolated worker. /cc @aishwaryabh |
Oh thank you @cgillum - you're right I had not connected the dots. Is there any possibility of getting a better error message for this case, maybe pointing to the article/roadmap? When Open.AI.Kusto is ready in isolated, I'll try .NET 8 again. Once we have taken action on any doc clarifications or error messages please feel free to close this. |
As an extension vendor, I'm not sure if there's much we can do to control the error experience, but I wonder if @fabiocav or @mattchenderson have thoughts on how the "graceful error message" can be solved in general for customers that try to run in-process functions on .NET 8? |
When I change my standard sample demo project to target .NET 8 in the csproj, the project builds clean, but then I get this runtime error when I test a post to IngestData (uses Embeddings binding):
This branch exactly repros it as you use
test.http
and post to the local IngestData function:.It is throwing on this line of code that uses the EmbeddingsRequest:embeddings record object, and note I have two fields, with RawText being null here:
If i changed EmbeddingsRequest definition to match the sample having only a single field in the record, I go back to getting Build errors all the time (maybe this was bound to happen and I forced a rebuild?):
The net of this (no pun intended :) ) is I cannot use .NET 8, or figure out a workaround.
The text was updated successfully, but these errors were encountered: