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

Getting model config from connection to be used with evalutors #39171

Closed
wants to merge 75 commits into from

Conversation

singankit
Copy link
Contributor

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

All SDK Contribution checklist:

  • The pull request does not introduce [breaking changes]
  • CHANGELOG is updated for new features, bug fixes or other significant changes.
  • I have read the contribution guidelines.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

dargilco and others added 7 commits December 20, 2024 12:59
* Fixed and chain stream

* Roll back to keep until_done() for the main stream.

* added tests

* fixed CI

* added integrated tests

* fixed lint

* fixed lint and test

* ghope to fix doc gen

* fix test and doc gen

* enable tests for streaming
* multiagent sample

* config file, team leader configurability

* multiagent folder

* review changes

* fixes

* fixes

* fix

---------

Co-authored-by: Marko Hietala <markhiet@microsoft.com>
* handle incompleted events

* Fixed CI and add chagne log
@dargilco
Copy link
Member

Please target this PR toward the feature branch feature/azure-ai-projects-beta5. This is the staging ground for the next release.

@dargilco
Copy link
Member

Please update the "Bug fixes" section in CHANGELOG.md with a description of the fix.

@singankit singankit changed the base branch from main to feature/azure-ai-projects-beta5 January 14, 2025 17:56
dinazavyr and others added 23 commits January 14, 2025 09:59
* Fixes mypy type errors.

* Fixed mypy errors

* Fixed pylint annotation errors

---------

Co-authored-by: Dina Saparbaeva <dsaparbaeva@microsoft.com>
* Fixed samples

* update date
* Update code_report.py

* Fix AttributeError by using `__all__` for operations
* update typespec-python 0.38.0

* update package.json
* Update sample_evaluations.py

* Update sample_evaluations.py

* Update sample_evaluations_async.py

* Replace HateUnfairnessEvaluator with ViolenceEvaluator
* Fix urls

* update
* Fix urls

* update
@singankit singankit changed the base branch from feature/azure-ai-projects-beta5 to main January 14, 2025 18:59
@azure-sdk
Copy link
Collaborator

API change check

APIView has identified API level changes in this PR and created following API reviews.

azure-ai-projects

@@ -238,7 +238,7 @@ def __init__(
self.key = connection.properties.credentials.key # type: ignore
self.token_credential = token_credential

def to_evaluator_model_config(self, deployment_name, api_version) -> Dict[str, str]:
def to_evaluator_model_config(self, deployment_name, api_version, *, include_credentials=False) -> Dict[str, str]:

Choose a reason for hiding this comment

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

Is it possible for us to check the connection type, and if its key-based, automatically add the include_credentials=True to the underlying call?

That removes some complexity for the end user, the code doesn't need to change if the connection type changes.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

For local usage that will work perfectly. But for remote evals it could lead to secret unintentionally getting exposed hence added this param explicitly. Same is done for connections too.

Copy link

Hi @singankit. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days.

@github-actions github-actions bot added the no-recent-activity There has been no recent activity on this issue. label Mar 28, 2025
Copy link

github-actions bot commented Apr 4, 2025

Hi @singankit. Thank you for your contribution. Since there hasn't been recent engagement, we're going to close this out. Feel free to respond with a comment containing /reopen if you'd like to continue working on these changes. Please be sure to use the command to reopen or remove the no-recent-activity label; otherwise, this is likely to be closed again with the next cleanup pass.

@github-actions github-actions bot closed this Apr 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AI no-recent-activity There has been no recent activity on this issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.