GithubHelp home page GithubHelp logo

Comments (4)

nitya avatar nitya commented on June 28, 2024

@nickcoast - if you look at the Azure AI Resource you are using (Azure AI Studio > Manage > Select your resource) and then click on the Connections in the sidebar:

What connections do you see listed there of type "Azure OpenAI"? The manual should have had a step that helped you set up the same named connections in both VS Code and Azure Open AI ahead of time so just checking if the latter was completed.

from contoso-chat.

nickcoast avatar nickcoast commented on June 28, 2024

Hi @nitya thanks for taking the time. I have two connections of type "Azure OpenAI", the "Default" one shared to all projects, and the "aaoi_connection". Both have the same "Target" URI.

image

This is how I had set it up.
Following the instructions from the "AI Tour" event:

  1. I created the connections (including aoai-connection) in AI Studio and ML Studio
  2. I copied the keys and endpoints into .env in the Codespace
  3. I ran connections/create-connections.ipynb to set up local connections
  4. I ran /contoso-chat/flow.dag.yaml and it works, no connection errors.

from contoso-chat.

nitya avatar nitya commented on June 28, 2024

@nickcoast that is strange. Yes the steps seem right and I can see you had both connections setup correctly. The only thing I can think of is that the Cloud connection (made via the Azure AI Studio UI) had the API Key wrong for some reason.

401 indicates it was an authorization issue.

Can you check the key in the AOAI Connection and verify it is the same as local? (BTW the cloud entry should NOT have " " enclosing the key value - I had that issue when I copied the stringified version directly from .env)

from contoso-chat.

nickcoast avatar nickcoast commented on June 28, 2024

@nitya Quotes weren't the issue. But when I copy-pasted I somehow clipped 1 character from the beginning of the key. So that explains why the Flow worked in the Codespace but not on ai.azure.com.

After fixing that, this step works. But now the next one, the deploy step, fails with Environment '{}' is not registered.

I'll start a new issue for that. Thank you for looking into this!

from contoso-chat.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.