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

Main to release [to update docs] #301

Closed
wants to merge 53 commits into from
Closed

Main to release [to update docs] #301

wants to merge 53 commits into from

Conversation

fm1320
Copy link
Collaborator

@fm1320 fm1320 commented Dec 13, 2024

What does this PR do?

Fixes #<issue_number>

Before submitting
  • Was this discussed/agreed via a GitHub issue? (not for typos and docs)
  • Did you read the contributor guideline?
  • Did you make sure your PR does only one thing, instead of bundling different changes together?
  • Did you make sure to update the documentation with your changes? (if necessary)
  • Did you write any new necessary tests? (not for typos and docs)
  • Did you verify new and existing tests pass locally with your changes?
  • Did you list all the breaking changes introduced by this pull request?

adityasugandhi and others added 30 commits August 21, 2024 14:06
fixed azure_ad_token provider in AzureOpenAI
…book

Add Adalflow model client notebook tutorial
[Model_client integration] Model_client AWS BedRock + Azure AI integration
…ry.Memory class. This method returns a formatted conversation history, handles empty conversations, and formats user and assistant messages.Additionally, added add_dialog_turn() method to handle new back-and-forth messages. This adds an id to each dialog turn for tracking and appends it to the current_conversation list. Finally, added 3 new tests for memory -empty memory, single dialog turn, and multiple dialog turn tests. Also updated the chatbot usage notebook to replace the deprecated class with the updated one.
@fm1320 fm1320 requested a review from liyin2015 December 13, 2024 13:06
@fm1320 fm1320 changed the base branch from main to release December 13, 2024 17:15
@liyin2015
Copy link
Member

No summary at all, and not the right process, we go from main -> release, not using main-to-release branch

@liyin2015 liyin2015 closed this Dec 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants