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

Add Azure AI Studio inference API #4020

Merged
merged 5 commits into from
Mar 25, 2025
Merged

Add Azure AI Studio inference API #4020

merged 5 commits into from
Mar 25, 2025

Conversation

lcawl
Copy link
Contributor

@lcawl lcawl commented Mar 19, 2025

Copy link
Contributor

Following you can find the validation results for the APIs you have changed.

API Status Request Response
inference.put_azureaistudio Missing test Missing test

You can validate these APIs yourself by using the make validate target.

@lcawl lcawl changed the title Add inference.put_azureaistudio.json Add Azure AI Studio inference API Mar 21, 2025
@lcawl lcawl marked this pull request as ready for review March 21, 2025 01:54
@lcawl lcawl requested a review from a team as a code owner March 21, 2025 01:54
Copy link
Contributor

Following you can find the validation results for the APIs you have changed.

API Status Request Response
inference.put_azureaistudio Missing test Missing test

You can validate these APIs yourself by using the make validate target.

2 similar comments
Copy link
Contributor

Following you can find the validation results for the APIs you have changed.

API Status Request Response
inference.put_azureaistudio Missing test Missing test

You can validate these APIs yourself by using the make validate target.

Copy link
Contributor

Following you can find the validation results for the APIs you have changed.

API Status Request Response
inference.put_azureaistudio Missing test Missing test

You can validate these APIs yourself by using the make validate target.

azureaistudio
}

export class AzureAiStudioServiceSettings {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@l-trotta l-trotta self-assigned this Mar 24, 2025
@lcawl lcawl mentioned this pull request Mar 24, 2025
2 tasks
@lcawl lcawl force-pushed the azureaistudio-inference branch from 88228b3 to 408bdec Compare March 25, 2025 16:22
@lcawl lcawl enabled auto-merge (squash) March 25, 2025 16:23
Copy link
Contributor

Following you can find the validation results for the APIs you have changed.

API Status Request Response
inference.put_azureaistudio Missing test Missing test

You can validate these APIs yourself by using the make validate target.

@lcawl lcawl merged commit 0eab22c into main Mar 25, 2025
8 checks passed
@lcawl lcawl deleted the azureaistudio-inference branch March 25, 2025 16:24
Copy link
Contributor

The backport to 8.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-8.x 8.x
# Navigate to the new working tree
cd .worktrees/backport-8.x
# Create a new branch
git switch --create backport-4020-to-8.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 0eab22cb8125693e2ceb97917666473a085fb4e0
# Push it to GitHub
git push --set-upstream origin backport-4020-to-8.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.x

Then, create a pull request where the base branch is 8.x and the compare/head branch is backport-4020-to-8.x.

Copy link
Contributor

The backport to 8.18 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-8.18 8.18
# Navigate to the new working tree
cd .worktrees/backport-8.18
# Create a new branch
git switch --create backport-4020-to-8.18
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 0eab22cb8125693e2ceb97917666473a085fb4e0
# Push it to GitHub
git push --set-upstream origin backport-4020-to-8.18
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.18

Then, create a pull request where the base branch is 8.18 and the compare/head branch is backport-4020-to-8.18.

Copy link
Contributor

The backport to 9.0 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-9.0 9.0
# Navigate to the new working tree
cd .worktrees/backport-9.0
# Create a new branch
git switch --create backport-4020-to-9.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 0eab22cb8125693e2ceb97917666473a085fb4e0
# Push it to GitHub
git push --set-upstream origin backport-4020-to-9.0
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-9.0

Then, create a pull request where the base branch is 9.0 and the compare/head branch is backport-4020-to-9.0.

lcawl added a commit that referenced this pull request Mar 25, 2025
@lcawl
Copy link
Contributor Author

lcawl commented Mar 25, 2025

💚 All backports created successfully

Status Branch Result
9.0

Questions ?

Please refer to the Backport tool documentation

lcawl added a commit that referenced this pull request Mar 25, 2025
@lcawl
Copy link
Contributor Author

lcawl commented Mar 25, 2025

💚 All backports created successfully

Status Branch Result
8.x

Questions ?

Please refer to the Backport tool documentation

lcawl added a commit that referenced this pull request Mar 25, 2025
@lcawl
Copy link
Contributor Author

lcawl commented Mar 25, 2025

💚 All backports created successfully

Status Branch Result
8.18

Questions ?

Please refer to the Backport tool documentation

lcawl added a commit that referenced this pull request Mar 25, 2025
lcawl added a commit that referenced this pull request Mar 25, 2025
lcawl added a commit that referenced this pull request Mar 25, 2025
lcawl added a commit that referenced this pull request Mar 25, 2025
lcawl added a commit that referenced this pull request Mar 25, 2025
lcawl added a commit that referenced this pull request Mar 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants