Skip to content

Conversation

@AjitPadhi-Microsoft
Copy link
Contributor

Purpose

  • Not getting date and time of the next scheduled meeting in response issue fixed. Kernel function ChatWithSQLDatabase now returns the next meeting date and time in the response.

Does this introduce a breaking change?

  • Yes
  • No

Golden Path Validation

  • I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

  • I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

  • ...

Other Information

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR fixes the issue of not receiving the date and time of the next scheduled meeting by updating the kernel function's description to include details about upcoming meeting dates/times. It also includes a comprehensive update to the .dockerignore file for improved container builds.

  • Updated the function decorator in chat_logic_handler.py to correct spelling and expand on meeting details.
  • Added a detailed .dockerignore file to exclude unnecessary files from container builds.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
src/App/backend/chat_logic_handler.py Updated the kernel_function description to fix a spelling error and clarify it now returns meeting details.
src/.dockerignore Introduced an extensive ignore list to prevent inclusion of non-essential files in container builds.

return answer

@kernel_function(name="ChatWithSQLDatabase", description="Given a query about client assets, investements and meeting dates or times, get details from the database based on the provided question and client id")
@kernel_function(name="ChatWithSQLDatabase", description="Given a query about client assets, investments and meeting scheduled (including upcoming or next meeting dates/times), get details from the database based on the provided question and client id")
Copy link

Copilot AI May 14, 2025

Choose a reason for hiding this comment

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

[nitpick] The updated description is clearer, but the phrasing with parentheses may be improved for readability. Consider streamlining the wording to ensure consistency with other function descriptions, for example, '... and next scheduled meeting date/time' could be a simpler alternative.

Copilot uses AI. Check for mistakes.
@AjitPadhi-Microsoft AjitPadhi-Microsoft changed the base branch from main to dev May 14, 2025 11:36
@AjitPadhi-Microsoft AjitPadhi-Microsoft changed the title fix fix: meeting scheduled date time response issue May 14, 2025
@Roopan-Microsoft Roopan-Microsoft merged commit b4ba302 into dev May 14, 2025
8 of 10 checks passed
@Roopan-Microsoft Roopan-Microsoft deleted the PSL-17861 branch May 14, 2025 11:42
Roopan-Microsoft added a commit that referenced this pull request May 21, 2025
* Added .dockerignore file to exclude unnecessary files from Docker build context (#537)

* fixed date time response issue (#542)

* Update main.bicepparam

* Update src/App/backend/chat_logic_handler.py

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

* Update src/.dockerignore

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

---------

Co-authored-by: Prasanjeet-Microsoft <v-singhprasa@microsoft.com>
Co-authored-by: AjitPadhi-Microsoft <v-padhiajit@microsoft.com>
Co-authored-by: Abdul-Microsoft <v-amujeebta@microsoft.com>
Co-authored-by: Harmanpreet Kaur <v-harmanpkau@microsoft.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@github-actions
Copy link

github-actions bot commented Jun 6, 2025

🎉 This PR is included in version 1.2.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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.

3 participants