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 basic implementation of agent profiler #1023

Closed
wants to merge 27 commits into from
Closed

Add basic implementation of agent profiler #1023

wants to merge 27 commits into from

Conversation

gagb
Copy link
Collaborator

@gagb gagb commented Dec 19, 2023

Why are these changes needed?

Implements the most basic profiler for mapping a given chat history to a visualization.
It first annotates the conversation using GPT-4 and then visualizes the annotated history as a directed graph.

Related issue number

#307

Checks

@gagb gagb marked this pull request as ready for review December 19, 2023 00:43
@gagb gagb requested review from afourney and qingyun-wu December 19, 2023 00:43
@codecov-commenter
Copy link

codecov-commenter commented Dec 19, 2023

Codecov Report

Attention: Patch coverage is 0% with 76 lines in your changes missing coverage. Please review.

Please upload report for BASE (0.2@e7cdae6). Learn more about missing BASE report.

Files with missing lines Patch % Lines
autogen/agentchat/contrib/profiler/visualize.py 0.00% 41 Missing ⚠️
autogen/agentchat/contrib/profiler/profiler.py 0.00% 33 Missing ⚠️
autogen/agentchat/contrib/profiler/__init__.py 0.00% 2 Missing ⚠️
Additional details and impacted files
@@          Coverage Diff           @@
##             0.2    #1023   +/-   ##
======================================
  Coverage       ?   39.90%           
======================================
  Files          ?       35           
  Lines          ?     4378           
  Branches       ?     1067           
======================================
  Hits           ?     1747           
  Misses         ?     2505           
  Partials       ?      126           
Flag Coverage Δ
unittests 39.83% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@gagb gagb marked this pull request as draft February 8, 2024 02:17
whiskyboy pushed a commit to whiskyboy/autogen that referenced this pull request Apr 17, 2024
* Catch AuthenticationError trying different configs
While trying different openai `config_list`, some
configs might be outdated (e.g., an API key is expired).
In these cases, we don't want the program to crash.
Instead, we might want to try other configs.

* Lint whitespace
Copy link

gitguardian bot commented Jul 20, 2024

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
Once a secret has been leaked into a git repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@ekzhu ekzhu changed the base branch from main to 0.2 October 2, 2024 18:30
@jackgerrits jackgerrits added the 0.2 Issues which are related to the pre 0.4 codebase label Oct 4, 2024
@rysweet
Copy link
Collaborator

rysweet commented Oct 10, 2024

This PR is against AutoGen 0.2. AutoGen 0.2 has been moved to the 0.2 branch. Please rebase your PR on the 0.2 branch or update it to work with the new AutoGen 0.4 that is now in main.

1 similar comment
@rysweet
Copy link
Collaborator

rysweet commented Oct 10, 2024

This PR is against AutoGen 0.2. AutoGen 0.2 has been moved to the 0.2 branch. Please rebase your PR on the 0.2 branch or update it to work with the new AutoGen 0.4 that is now in main.

@rysweet
Copy link
Collaborator

rysweet commented Oct 11, 2024

@gagb do we still need this one open?

@rysweet rysweet added the awaiting-op-response Issue or pr has been triaged or responded to and is now awaiting a reply from the original poster label Oct 11, 2024
@gagb gagb closed this Oct 13, 2024
@gagb
Copy link
Collaborator Author

gagb commented Oct 13, 2024

I will resume this later; Add to 0.4 instead of 0.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.2 Issues which are related to the pre 0.4 codebase awaiting-op-response Issue or pr has been triaged or responded to and is now awaiting a reply from the original poster
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants