PR for main copy to sync with original repo #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…cep template (microsoft#1780) ### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> Adding `ChatStore:Cosmos:ChatParticipantsContainer` config setting to the bicep template for the web app. In response to: https://github.com/orgs/microsoft/projects/852/views/5?pane=issue&itemId=32088282 Did a test deployment and verified that new setting is in the config! { "name": "ChatStore:Cosmos:ChatParticipantsContainer", "value": "chatparticipants", "slotSetting": false },  Then tested deployed webapi with local webapp instance and chatbot is running as expected ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [x] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) - [x] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with `dotnet format` - [x] All unit tests pass, and I have added new tests where possible - [x] I didn't break anyone 😄
…1790) ### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> Method `SaveInformationAsync` of kernel memory type should be idempotent to update memory record with same key multiple times. This PR contains changes to allow that behavior in Chroma connector and tests to verify it. ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> 1. Replaced Chroma `POST /collections/{collection_id}/add` with `POST collections/{collection_id}/upsert` to allow idempotent behavior. 2. Added integration tests to verify scenario with adding/updating memory record with same key multiple times. ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [x] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) - [x] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with `dotnet format` - [x] All unit tests pass, and I have added new tests where possible - [x] I didn't break anyone 😄
…rosoft#1710) ### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> fix the ESLint violations in CopilotChat and enable the linter to run during `yarn start`/`yarn build`. **lint errors going forward will fail the build** and will need to be corrected before a PR can merge. we have already configured the linter to auto-fix on save in VSCode and for other IDEs the `yarn lint:fix` script can be used. ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> - `.node-pr.yml`: removed unneeded directory filter since `samples/apps` no longer contains a `yarn.lock`. - `.vscode/settings.json`: updated to point to the `eslintConfig` in the `package.json` rather than the shared JS file. this is required so that the plugins are resolved correctly by the extension. - `.eslintrc.js`: - removed deprecated `@typescript-eslint` rules. - removed plugins already resolved from create-react-app. - removed `standard-with-typescript` extended config in favor of more widely used configs. - `webapp/package.json`: - pinned TS version to `5.0.4`, the latest version below `5.1.0`. this is a dependency requirement of `@typescript-eslint` and otherwise the linter will not work. - re-added `eslintConfig` that now extends from the `../../eslintrc.js`. this is required so that the plugins are resolved correctly by ESLint. - `samples/apps/package.json`: - deleted since there are now no shared dependencies that need to be downloaded. - similarly, the `yarn.lock` file was removed as well. - all of the plugins/configs used in `.eslintrc.js` are already included in the [create-react-app config](https://github.com/facebook/create-react-app/blob/main/packages/eslint-config-react-app/index.js) which we extend. - **all other files**: fixed **379** errors and **42** warnings. ### Preview #### During build <img width="258" alt="image" src="https://github.com/microsoft/semantic-kernel/assets/52973358/94a42909-7cb6-48a7-8d5f-6f55a15d6025"> #### In VSCode w/ ESLint extension installed <img width="253" alt="image" src="https://github.com/microsoft/semantic-kernel/assets/52973358/182604ab-6228-49f6-8983-4ef902e7e945"> ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [X] The code builds clean without any errors or warnings - [x] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) - [X] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with `dotnet format` - [X] All unit tests pass, and I have added new tests where possible - [X] I didn't break anyone 😄 - [X] Bugbash to double check nothing is broken (not yet but before merging)
…oft#1786) ### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> I noticed the script was slightly misaligned during my deployment of webapi. ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> corrects the usage string and sets a default value for the `PACKAGE_FILE_PATH` similar to the Powershell script. ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [X] The code builds clean without any errors or warnings - [X] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) - [X] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with `dotnet format` - [X] All unit tests pass, and I have added new tests where possible - [X] I didn't break anyone 😄
### Motivation and Context The culture will never be null here so these fallbacks aren't ever used. ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [x] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) - [x] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with `dotnet format` - [x] All unit tests pass, and I have added new tests where possible - [x] I didn't break anyone 😄
) ### Motivation and Context While trying to reuse the Settings class used in the C# notebooks to load the Kernel configuration, I saw the parameter to specify a file was not properly used. ### Description Very simple changes as I just updated the code to use the function parameter instead of the Class variable Default It is in the notebook part so no build nor tests. Notebooks are still working. ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [x] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) - [x] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with `dotnet format` - [x] All unit tests pass, and I have added new tests where possible - [x] I didn't break anyone 😄 Co-authored-by: Shawn Callegari <36091529+shawncal@users.noreply.github.com>
…ch (microsoft#1686) Improve on the options to get RediSearch. ### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [ ] The code builds clean without any errors or warnings - [ ] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) - [ ] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with `dotnet format` - [ ] All unit tests pass, and I have added new tests where possible - [x] I didn't break anyone 😄 Co-authored-by: Dmytro Struk <13853051+dmytrostruk@users.noreply.github.com>
…t#1785) ### Motivation and Context Notebook showing how to leverage the new Chroma connector in .NET. --------- Co-authored-by: Dmytro Struk <13853051+dmytrostruk@users.noreply.github.com>
### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> Follow microsoft#1735 (review) advice to rename methods and separate responsibilities. ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> - Separate the responsibilities of PostgresMemoryStore and PostgresDbClient. - Add the real batch methods to PostgresDbClient. - Save timestamp with `TIMESTAMP WITH TIME ZONE` type - Stop creating index ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [x] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) - [x] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with `dotnet format` - [x] All unit tests pass, and I have added new tests where possible - [x] I didn't break anyone 😄 --------- Co-authored-by: Dmytro Struk <13853051+dmytrostruk@users.noreply.github.com>
### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? To fix the SemanticTextMemory functionality 2. What problem does it solve? microsoft#1815 3. What scenario does it contribute to? All scenarios that intend on using RAG 4. If it fixes an open issue, please link to the issue here. microsoft#1815 --> 1. Why is this change required? To fix the SemanticTextMemory functionality 2. What problem does it solve? microsoft#1815 3. What scenario does it contribute to? All scenarios that intend on using RAG 4. If it fixes an open issue, please link to the issue here. microsoft#1815 ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> Simple decomposition of the list of embeddings returned via `generate_embeddings_async` ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [x] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) - [ ] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with `dotnet format` - [x] All unit tests pass, and I have added new tests where possible - [x] I didn't break anyone 😄
### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> Labeler actions on PRs are currently failing due to a broken match rule. ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> Add required quotation marks for match rule with leading asterisk (see [reference](https://github.com/actions/labeler#basic-examples)).
Bumps [ruff](https://github.com/astral-sh/ruff) from 0.0.275 to 0.0.276. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/astral-sh/ruff/releases">ruff's releases</a>.</em></p> <blockquote> <h2>v0.0.276</h2> <!-- raw HTML omitted --> <p>See the <a href="https://astral.sh/blog/ruff-v0.0.276">release blog post</a> for more, including detailed descriptions of any newly added rules.</p> <h2>What's Changed</h2> <p>Highlights include: experimental support for linting Jupyter Notebooks.</p> <p>To opt-in to linting Jupyter Notebook files, add the <code>*.ipynb</code> pattern to your <a href="https://github.com/astral-sh/ruff/blob/HEAD/settings.md#include"><code>include</code></a> setting, like so:</p> <pre lang="toml"><code>[tool.ruff] # Allow Ruff to discover `*.ipynb` files. include = ["*.py", "*.pyi", "**/pyproject.toml", "*.ipynb"] </code></pre> <p>This will prompt Ruff to discover Jupyter Notebook files in any specified directories, and lint them accordingly.</p> <p>Jupyter Notebook support is currently opt-in and experimental. We'd love your help testing it out. Have feedback? Run into issues? <a href="https://github.com/astral-sh/ruff/issues/new">Let us know!</a></p> <h3>New Rules</h3> <ul> <li>[<code>flake8-pyi</code>] Implement <code>PYI002</code>, <code>PYI003</code>, <code>PYI004</code>, <code>PYI005</code> by <a href="https://github.com/density"><code>@density</code></a> in <a href="https://redirect.github.com/astral-sh/ruff/pull/5457">astral-sh/ruff#5457</a></li> <li>[<code>numpy</code>] Implement <code>numpy-deprecated-function</code> (<code>NPY003</code>) by <a href="https://github.com/charliermarsh"><code>@charliermarsh</code></a> in <a href="https://redirect.github.com/astral-sh/ruff/pull/5468">astral-sh/ruff#5468</a></li> <li>[<code>perflint</code>] Implement <code>unnecessary-list-cast</code> (<code>PERF101</code>) by <a href="https://github.com/qdegraaf"><code>@qdegraaf</code></a> in <a href="https://redirect.github.com/astral-sh/ruff/pull/5121">astral-sh/ruff#5121</a></li> <li>[<code>perflint</code>] Implement <code>try-except-in-loop</code> (<code>PERF203</code>) by <a href="https://github.com/evanrittenhouse"><code>@evanrittenhouse</code></a> in <a href="https://redirect.github.com/astral-sh/ruff/pull/5166">astral-sh/ruff#5166</a></li> <li>[<code>perflint</code>] Implement <code>manual-list-comprehension</code> (<code>PERF401</code>) and <code>manual-list-copy</code> (<code>PERF402</code>) rules by <a href="https://github.com/qdegraaf"><code>@qdegraaf</code></a> in <a href="https://redirect.github.com/astral-sh/ruff/pull/5298">astral-sh/ruff#5298</a></li> <li>[<code>pylint</code>] Implement Pylint <code>single-string-used-for-slots</code> (<code>C0205</code>) as <code>single-string-slots</code> (<code>PLC0205</code>) by <a href="https://github.com/tjkuson"><code>@tjkuson</code></a> in <a href="https://redirect.github.com/astral-sh/ruff/pull/5399">astral-sh/ruff#5399</a></li> </ul> <h3>Jupyter</h3> <ul> <li>Experimental release for Jupyter notebook integration by <a href="https://github.com/dhruvmanila"><code>@dhruvmanila</code></a> in <a href="https://redirect.github.com/astral-sh/ruff/pull/5363">astral-sh/ruff#5363</a></li> <li>Enable --watch for Jupyter notebooks by <a href="https://github.com/charliermarsh"><code>@charliermarsh</code></a> in <a href="https://redirect.github.com/astral-sh/ruff/pull/5394">astral-sh/ruff#5394</a></li> <li>Consider Jupyter index for code frames (<code>--show-source</code>) by <a href="https://github.com/dhruvmanila"><code>@dhruvmanila</code></a> in <a href="https://redirect.github.com/astral-sh/ruff/pull/5402">astral-sh/ruff#5402</a></li> <li>fixup! Consider Jupyter index for code frames (<code>--show-source</code>) (<a href="https://redirect.github.com/astral-sh/ruff/issues/5402">#5402</a>) by <a href="https://github.com/dhruvmanila"><code>@dhruvmanila</code></a> in <a href="https://redirect.github.com/astral-sh/ruff/pull/5414">astral-sh/ruff#5414</a></li> </ul> <h3>Settings</h3> <ul> <li>[<code>pyupgrade</code>] Restore the <code>keep-runtime-typing</code> setting by <a href="https://github.com/charliermarsh"><code>@charliermarsh</code></a> in <a href="https://redirect.github.com/astral-sh/ruff/pull/5470">astral-sh/ruff#5470</a></li> <li>Add <code>PythonVersion::Py312</code> by <a href="https://github.com/charliermarsh"><code>@charliermarsh</code></a> in <a href="https://redirect.github.com/astral-sh/ruff/pull/5316">astral-sh/ruff#5316</a></li> </ul> <h3>Bug Fixes</h3> <ul> <li>Support <code>pydantic.BaseSettings</code> in <code>mutable-class-default</code> by <a href="https://github.com/charliermarsh"><code>@charliermarsh</code></a> in <a href="https://redirect.github.com/astral-sh/ruff/pull/5312">astral-sh/ruff#5312</a></li> <li>Allow <code>__slots__</code> assignments in <code>mutable-class-default</code> by <a href="https://github.com/charliermarsh"><code>@charliermarsh</code></a> in <a href="https://redirect.github.com/astral-sh/ruff/pull/5314">astral-sh/ruff#5314</a></li> <li>Avoid syntax errors when removing f-string prefixes by <a href="https://github.com/charliermarsh"><code>@charliermarsh</code></a> in <a href="https://redirect.github.com/astral-sh/ruff/pull/5319">astral-sh/ruff#5319</a></li> <li>Ignore unpacking in <code>iteration-over-set</code> by <a href="https://github.com/charliermarsh"><code>@charliermarsh</code></a> in <a href="https://redirect.github.com/astral-sh/ruff/pull/5392">astral-sh/ruff#5392</a></li> <li>Replace same length equal line with dash line in D407 by <a href="https://github.com/dhruvmanila"><code>@dhruvmanila</code></a> in <a href="https://redirect.github.com/astral-sh/ruff/pull/5383">astral-sh/ruff#5383</a></li> <li>Exclude docstrings from PYI053 by <a href="https://github.com/intgr"><code>@intgr</code></a> in <a href="https://redirect.github.com/astral-sh/ruff/pull/5405">astral-sh/ruff#5405</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/astral-sh/ruff/blob/main/BREAKING_CHANGES.md">ruff's changelog</a>.</em></p> <blockquote> <h2>0.0.276</h2> <h3>The <code>keep-runtime-typing</code> setting has been reinstated (<a href="https://redirect.github.com/astral-sh/ruff/pull/5470">#5470</a>)</h3> <p>The <code>keep-runtime-typing</code> setting has been reinstated with revised semantics. This setting was removed in <a href="https://redirect.github.com/astral-sh/ruff/pull/4427">#4427</a>, as it was equivalent to ignoring the <code>UP006</code> and <code>UP007</code> rules via Ruff's standard <code>ignore</code> mechanism.</p> <p>Taking <code>UP006</code> (rewrite <code>List[int]</code> to <code>list[int]</code>) as an example, the setting now behaves as follows:</p> <ul> <li>On Python 3.7 and Python 3.8, setting <code>keep-runtime-typing = true</code> will cause Ruff to ignore <code>UP006</code> violations, even if <code>from __future__ import annotations</code> is present in the file. While such annotations are valid in Python 3.7 and Python 3.8 when combined with <code>from __future__ import annotations</code>, they aren't supported by libraries like Pydantic and FastAPI, which rely on runtime type checking.</li> <li>On Python 3.9 and above, the setting has no effect, as <code>list[int]</code> is a valid type annotation, and libraries like Pydantic and FastAPI support it without issue.</li> </ul> <p>In short: <code>keep-runtime-typing</code> can be used to ensure that Ruff doesn't introduce type annotations that are not supported at runtime by the current Python version, which are unsupported by libraries like Pydantic and FastAPI.</p> <p>Note that this is not a breaking change, but is included here to complement the previous removal of <code>keep-runtime-typing</code>.</p> <h2>0.0.268</h2> <h3>The <code>keep-runtime-typing</code> setting has been removed (<a href="https://redirect.github.com/astral-sh/ruff/pull/4427">#4427</a>)</h3> <p>Enabling the <code>keep-runtime-typing</code> option, located under the <code>pyupgrade</code> section, is equivalent to ignoring the <code>UP006</code> and <code>UP007</code> rules via Ruff's standard <code>ignore</code> mechanism. As there's no need for a dedicated setting to disable these rules, the <code>keep-runtime-typing</code> option has been removed.</p> <h2>0.0.267</h2> <h3><code>update-check</code> is no longer a valid configuration option (<a href="https://redirect.github.com/astral-sh/ruff/pull/4313">#4313</a>)</h3> <p>The <code>update-check</code> functionality was deprecated in <a href="https://redirect.github.com/astral-sh/ruff/pull/2530">#2530</a>, in that the behavior itself was removed, and Ruff was changed to warn when that option was enabled.</p> <p>Now, Ruff will throw an error when <code>update-check</code> is provided via a configuration file (e.g., <code>update-check = false</code>) or through the command-line, since it has no effect. Users should remove this option from their configuration.</p> <h2>0.0.265</h2> <h3><code>--fix-only</code> now exits with a zero exit code, unless <code>--exit-non-zero-on-fix</code> is specified (<a href="https://redirect.github.com/astral-sh/ruff/pull/4146">#4146</a>)</h3> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/astral-sh/ruff/commit/3992c47c008df8f706e03a6ba0d7aa7f068ef0a9"><code>3992c47</code></a> Bump version to 0.0.276 (<a href="https://redirect.github.com/astral-sh/ruff/issues/5488">#5488</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/8de5a3d29df5964dd91f39d0150caccc7bf0ab83"><code>8de5a3d</code></a> Allow <code>Final</code> assignments in stubs (<a href="https://redirect.github.com/astral-sh/ruff/issues/5490">#5490</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/ed1dd09d02af7972df301dac0c6b5d084f26cc1b"><code>ed1dd09</code></a> Refine some <code>perflint</code> rules (<a href="https://redirect.github.com/astral-sh/ruff/issues/5484">#5484</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/ca497fabbd970a557ed1b45acccaa714e12573af"><code>ca497fa</code></a> Remove some <code>diagnostics.extend</code> calls (<a href="https://redirect.github.com/astral-sh/ruff/issues/5483">#5483</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/00fbbe4223d0cbfc3014403ace659f48368e1852"><code>00fbbe4</code></a> Remove some additional manual iterator matches (<a href="https://redirect.github.com/astral-sh/ruff/issues/5482">#5482</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/dadad0e9ed861b50c87f2bf5c4520b949ac177ab"><code>dadad0e</code></a> Remove some allocations in argument detection (<a href="https://redirect.github.com/astral-sh/ruff/issues/5481">#5481</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/d2450c25abc428cb5276933b2ae21017fcd98f3d"><code>d2450c2</code></a> Audit <code>remove_argument</code> usages to use end-of-function (<a href="https://redirect.github.com/astral-sh/ruff/issues/5480">#5480</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/1e4b88969cbfa866c0ac6aace562699c1fd6b371"><code>1e4b889</code></a> Fix <code>unnecessary-encode-utf8</code> to fix <code>encode</code> on parenthesized strings correc...</li> <li><a href="https://github.com/astral-sh/ruff/commit/dc072537e513912eced43c24e6fc8d61d77aca4d"><code>dc07253</code></a> Fix python_formatter generate.py with rust path (<a href="https://redirect.github.com/astral-sh/ruff/issues/5475">#5475</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/7ac9e0252e3c278078e19a7053671fdc845986af"><code>7ac9e02</code></a> Document Checking formatter stability and panics (<a href="https://redirect.github.com/astral-sh/ruff/issues/5415">#5415</a>)</li> <li>Additional commits viewable in <a href="https://github.com/astral-sh/ruff/compare/v0.0.275...v0.0.276">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…ft#1825) Bumps [Microsoft.NET.Test.Sdk](https://github.com/microsoft/vstest) from 17.6.2 to 17.6.3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/vstest/releases">Microsoft.NET.Test.Sdk's releases</a>.</em></p> <blockquote> <h2>v17.6.3</h2> <h3>Issues Fixed</h3> <ul> <li>[rel/17.6] Update version to 17.6.3 by <a href="https://github.com/nohwnd"><code>@nohwnd</code></a> in <a href="https://redirect.github.com/microsoft/vstest/pull/4555">#4555</a></li> <li>[rel/17.6] Disable pre-start of testhosts by <a href="https://github.com/nohwnd"><code>@nohwnd</code></a> in <a href="https://redirect.github.com/microsoft/vstest/pull/4554">#4554</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/vstest/compare/v17.6.2...v17.6.3">https://github.com/microsoft/vstest/compare/v17.6.2...v17.6.3</a></p> <h3>Artifacts</h3> <ul> <li>TestPlatform vsix: <a href="https://vsdrop.corp.microsoft.com/file/v1/Products/DevDiv/microsoft/vstest/17.6/20230627-01;/TestPlatform.vsix">17.6.3</a></li> <li>Microsoft.TestPlatform.ObjectModel : <a href="https://www.nuget.org/packages/Microsoft.TestPlatform.ObjectModel/17.6.3">17.6.3</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/vstest/commit/e7ea853f64af5a4c240acaf9e54cdae3ae0eb7bb"><code>e7ea853</code></a> [rel/17.6] Update version to 17.6.3 (<a href="https://redirect.github.com/microsoft/vstest/issues/4555">#4555</a>)</li> <li><a href="https://github.com/microsoft/vstest/commit/bda2d1e387c47db04a99ae2beee4261ba452e4c7"><code>bda2d1e</code></a> [rel/17.6] Disable pre-start of testhosts (<a href="https://redirect.github.com/microsoft/vstest/issues/4554">#4554</a>)</li> <li>See full diff in <a href="https://github.com/microsoft/vstest/compare/v17.6.2...v17.6.3">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Shawn Callegari <36091529+shawncal@users.noreply.github.com>
This pains me, as it's a technical step backwards. But there are two problems today: 1) The .NET support policy today unfortunately applies not only to the .NET SDK and runtime but also to nuget packages released in the same wave, which means that if someone is relying on eg System.Text.Json and is running on .NET 6, having SK depend on System.Text.Json with a minimum version of 7.0 forces the consumer to also use the 7.0 version of System.Text.Json from the nuget, which then means that one assembly falls under the STS support policy instead of LTS support policy, which means that one assembly will have support end for it a few months earlier than it otherwise would. I've raised this issue for further evaluation on the .NET side of things, but in the meantime, this lowers the version number to remove the perceived problem and possible barrier to adoption. 2) Azure Functions has two deployment models: in-process and isolated. Ideally functions use isolated, which gives them the freedom to reference whatever they need. The in-process model is exactly what it sounds like: the function runs in the same process as the host, and the host pins several dependencies at 6.0 versions. That means that if a function references a 7.0 version, it'll fail to load in the in-process model. While we'd like for folks to be using the isolated model, we can't force it, and we don't want a need for the in-process model to block SK usage. This commit downgrades back to the 6.0 versions, at least where possible. Some of the connectors reference libraries (e.g. NRedisStack, pgvector, etc.) that themselves have a 7.0 dependency. Closes microsoft#1793 --------- Co-authored-by: Shawn Callegari <36091529+shawncal@users.noreply.github.com>
…otnet (microsoft#1826) Bumps [Microsoft.Azure.Functions.Worker.Sdk](https://github.com/Azure/azure-functions-dotnet-worker) from 1.10.0 to 1.11.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/Azure/azure-functions-dotnet-worker/releases">Microsoft.Azure.Functions.Worker.Sdk's releases</a>.</em></p> <blockquote> <h2>Microsoft.Azure.Functions.Worker.Sdk 1.11.0</h2> <h2>What's Changed</h2> <!-- raw HTML omitted --> <h3>Microsoft.Azure.Functions.Worker.Sdk 1.11.0 (meta package)</h3> <ul> <li>Update extension build project to reference Microsoft.NET.Sdk.Functions 4.2.0</li> </ul> <h3>Microsoft.Azure.Functions.Worker.Sdk.Generators 1.1.0-preview4</h3> <ul> <li>Add support for retry options (<a href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/1548">#1548</a>)</li> <li>Bug fix for when DefaultValue is not present on an IsBatched prop (<a href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/1602">#1602</a>).</li> <li>SDK changes for .NET 8.0 support (<a href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/1643">#1643</a>)</li> </ul> <h2>Microsoft.Azure.Functions.Worker 1.11.0-preview2</h2> <h2>What's Changed</h2> <ul> <li>Adding a new worker option property to opt-in the behavior to get empty entries in trigger payload by <a href="https://github.com/kshyju"><code>@kshyju</code></a> in <a href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/pull/1091">Azure/azure-functions-dotnet-worker#1091</a></li> </ul> <p><em>Sample usage</em></p> <pre><code>var host = new HostBuilder() .ConfigureFunctionsWorkerDefaults((builder) => { }, (options) => { options.IncludeEmptyEntriesInMessagePayload = true; }) .Build(); <p>host.Run(); </code></pre></p> <ul> <li>New overloads for <code>WriteStringAsync</code> and <code>WriteBytesAsync</code> methods by <a href="https://github.com/kshyju"><code>@kshyju</code></a> in <a href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/pull/1111">Azure/azure-functions-dotnet-worker#1111</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/Azure/azure-functions-dotnet-worker/compare/1.11.0-preview1...1.11.0-preview2">https://github.com/Azure/azure-functions-dotnet-worker/compare/1.11.0-preview1...1.11.0-preview2</a></p> <h2>Microsoft.Azure.Functions.Worker 1.11.0-preview1</h2> <h2>What's Changed</h2> <ul> <li>Added support for surfacing user-thrown exception to App Insights (<a href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/939">#939</a>)</li> <li>Source-generated function metadata: implementation change to improve cold-start performance (<a href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/956">#956</a>) <ul> <li>This functionality requires version <code>1.8.0-preview1</code> of <code>Microsoft.Azure.Functions.Worker.Sdk</code> or higher.</li> </ul> </li> </ul> <p>Steps for opting into the source-generation preview:</p> <ol> <li>Add MSBuild property <code><FunctionsEnableWorkerIndexing>true</FunctionsEnableWorkerIndexing></code> app's <code>.csproj</code> file.</li> <li>In <code>local.settings.json</code> add the property <code>"AzureWebJobsFeatureFlags": "EnableWorkerIndexing"</code> to configure the Azure Functions host to use worker-indexing.</li> <li>Call the <code>IHostBuilder</code> extension, <code>ConfigureGeneratedFunctionMetadataProvider</code> in <code>Program.cs</code>:</li> </ol> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/Azure/azure-functions-dotnet-worker/commit/a6322a3eb70bb6df93a9b22950c7bd50f8157e97"><code>a6322a3</code></a> Updating gRPC package version</li> <li><a href="https://github.com/Azure/azure-functions-dotnet-worker/commit/bdc8f0417e86db1ad1120f0de100de990118af9a"><code>bdc8f04</code></a> Removing preview for SDK release</li> <li><a href="https://github.com/Azure/azure-functions-dotnet-worker/commit/060d97d047c8f0e0824bdc1346a24704152e9236"><code>060d97d</code></a> Cleanup analyzer rules (<a href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/1686">#1686</a>)</li> <li><a href="https://github.com/Azure/azure-functions-dotnet-worker/commit/ccb3e0c3e93ccc590c42cba9e5543fe29d9cac55"><code>ccb3e0c</code></a> Updating Worker packages for release</li> <li><a href="https://github.com/Azure/azure-functions-dotnet-worker/commit/f80b0025e755ac6e21526ec0afee7fdef0a09c4f"><code>f80b002</code></a> Updating ASP.NET Core integration preview version</li> <li><a href="https://github.com/Azure/azure-functions-dotnet-worker/commit/a79adf4b8ecd86445e1aac9154541ada264a06e2"><code>a79adf4</code></a> Fix symbol to NET5_0_OR_GREATER (<a href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/1662">#1662</a>)</li> <li><a href="https://github.com/Azure/azure-functions-dotnet-worker/commit/d3414ddd08144cf68c556a0c706468603e01cefd"><code>d3414dd</code></a> Remove http proxy sample from FunctionApp (<a href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/1663">#1663</a>)</li> <li><a href="https://github.com/Azure/azure-functions-dotnet-worker/commit/240d5ffeb25020aa54c6afeb225ff20d00de8759"><code>240d5ff</code></a> Add SignalR test project to sln file (<a href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/1664">#1664</a>)</li> <li><a href="https://github.com/Azure/azure-functions-dotnet-worker/commit/ee532e7e1764a1dbe3cd7fedfbbdfa58489da2b0"><code>ee532e7</code></a> Update release notes.</li> <li><a href="https://github.com/Azure/azure-functions-dotnet-worker/commit/ed86b21b63222f60e02901170cf857d23decc3f3"><code>ed86b21</code></a> Setting _ToolingSuffix for V8.0 TargetFrameworkVersion</li> <li>Additional commits viewable in <a href="https://github.com/Azure/azure-functions-dotnet-worker/compare/1.10.0...sdk-1.11.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…app-react (microsoft#1901) Bumps [tough-cookie](https://github.com/salesforce/tough-cookie) from 4.1.2 to 4.1.3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/salesforce/tough-cookie/releases">tough-cookie's releases</a>.</em></p> <blockquote> <h2>4.1.3</h2> <p>Security fix for Prototype Pollution discovery in <a href="https://redirect.github.com/salesforce/tough-cookie/issues/282">#282</a>. This is a minor release, although output from the <code>inspect</code> utility is affected by this change, we felt this change was important enough to be pushed into the next patch.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/salesforce/tough-cookie/commit/4ff4d29f6cefd279a412b8d62a21142ebd410b36"><code>4ff4d29</code></a> 4.1.3 release preparation, update the package and lib/version to 4.1.3. (<a href="https://redirect.github.com/salesforce/tough-cookie/issues/284">#284</a>)</li> <li><a href="https://github.com/salesforce/tough-cookie/commit/12d474791bb856004e858fdb1c47b7608d09cf6e"><code>12d4747</code></a> Prevent prototype pollution in cookie memstore (<a href="https://redirect.github.com/salesforce/tough-cookie/issues/283">#283</a>)</li> <li><a href="https://github.com/salesforce/tough-cookie/commit/f06b72d1d447f33dfa6222c0a3c0c5e063558248"><code>f06b72d</code></a> Fix documentation for store.findCookies, missing allowSpecialUseDomain proper...</li> <li>See full diff in <a href="https://github.com/salesforce/tough-cookie/compare/v4.1.2...v4.1.3">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/microsoft/semantic-kernel/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…ebapp-react (microsoft#1902) Bumps [tough-cookie](https://github.com/salesforce/tough-cookie) from 4.1.2 to 4.1.3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/salesforce/tough-cookie/releases">tough-cookie's releases</a>.</em></p> <blockquote> <h2>4.1.3</h2> <p>Security fix for Prototype Pollution discovery in <a href="https://redirect.github.com/salesforce/tough-cookie/issues/282">#282</a>. This is a minor release, although output from the <code>inspect</code> utility is affected by this change, we felt this change was important enough to be pushed into the next patch.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/salesforce/tough-cookie/commit/4ff4d29f6cefd279a412b8d62a21142ebd410b36"><code>4ff4d29</code></a> 4.1.3 release preparation, update the package and lib/version to 4.1.3. (<a href="https://redirect.github.com/salesforce/tough-cookie/issues/284">#284</a>)</li> <li><a href="https://github.com/salesforce/tough-cookie/commit/12d474791bb856004e858fdb1c47b7608d09cf6e"><code>12d4747</code></a> Prevent prototype pollution in cookie memstore (<a href="https://redirect.github.com/salesforce/tough-cookie/issues/283">#283</a>)</li> <li><a href="https://github.com/salesforce/tough-cookie/commit/f06b72d1d447f33dfa6222c0a3c0c5e063558248"><code>f06b72d</code></a> Fix documentation for store.findCookies, missing allowSpecialUseDomain proper...</li> <li>See full diff in <a href="https://github.com/salesforce/tough-cookie/compare/v4.1.2...v4.1.3">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/microsoft/semantic-kernel/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Shawn Callegari <36091529+shawncal@users.noreply.github.com>
microsoft#1824) Bumps [Microsoft.Azure.Functions.Worker](https://github.com/Azure/azure-functions-dotnet-worker) from 1.15.0 to 1.16.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/Azure/azure-functions-dotnet-worker/releases">Microsoft.Azure.Functions.Worker's releases</a>.</em></p> <blockquote> <h2>Microsoft.Azure.Functions.Worker 1.16.0</h2> <h2>What's Changed</h2> <!-- raw HTML omitted --> <h3>Microsoft.Azure.Functions.Worker (metapackage) 1.16.0</h3> <h3>Microsoft.Azure.Functions.Worker.Core 1.13.0</h3> <ul> <li>Fixed issue spawning child process while debugging due to "DOTNET_STARTUP_HOOKS" always containing "Microsoft.Azure.Functions.Worker.Core". (<a href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/1539">#1539</a>)</li> <li>Add retry options support to <code>IFunctionMetadata</code> (<a href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/1548">#1548</a>)</li> </ul> <h3>Microsoft.Azure.Functions.Worker.Grpc 1.11.0</h3> <ul> <li>Add handling for retry options in worker-indexing grpc communication path (<a href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/1548">#1548</a>)</li> <li>Update protobuf to v1.9.0-protofile, which includes gRPC messages for retry-options in worker-indexing scenarios. (<a href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/1545">#1545</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/Azure/azure-functions-dotnet-worker/commits/1.16.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Shawn Callegari <36091529+shawncal@users.noreply.github.com>
…esponses (microsoft#1489) ### Motivation and Context The python notebooks are pinned to 0.2.7.dev0 while the latest pip package for python is 0.3.1.dev0. This PR updates the notebooks to pull the 0.3.1.dev0 and adds 2 new notebooks demonstrating new features added to SK between these versions. ### Description - All notebooks depend on semantic-kernel==0.3.1.dev0 - Added a notebook demonstrating streaming completion responses - Added a notebook demonstrating multiple responses per prompt (including streaming them) ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [ ] The code builds clean without any errors or warnings - [ ] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) - [ ] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with `dotnet format` - [ ] All unit tests pass, and I have added new tests where possible - [ ] I didn't break anyone 😄 --------- Co-authored-by: Lee Miller <lemiller@microsoft.com> Co-authored-by: Shawn Callegari <36091529+shawncal@users.noreply.github.com>
### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> Some LLM API's have the "max tokens" parameter as optional (OpenAI, Azure OpenAI, etc.) and will default to the remaining tokens left in the models context window. This PR changes the default value of max tokens from an explicitly defined amount to null. Note that skill specific max token amounts are unchanged, this PR aims to just change the defaults for library consumers right now. Fixes microsoft#1362 ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> Change max tokens to a nullable int type (`int` to `int?`). ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [✔️] The code builds clean without any errors or warnings - [✔️] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) - [✔️] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with `dotnet format` - [✔️] All unit tests pass, and I have added new tests where possible - [✔️] I didn't break anyone 😄 Co-authored-by: Lee Miller <lemiller@microsoft.com> Co-authored-by: Shawn Callegari <36091529+shawncal@users.noreply.github.com> Co-authored-by: Roger Barreto <19890735+RogerBarreto@users.noreply.github.com>
) ### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> addressing issue microsoft#1387 chunking text should allow use of an external tokenizer ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> added pass-through of an token counting function, defaulting to the existing _token_counter() method while fixing a type hint bug I got sucked into making a few changes to clean up the code. future work would be nice to add chunk overlap functionality similar to langchain's [TextSplitter]( https://github.com/hwchase17/langchain/blob/a6ebffb69504576a805f3b9f09732ad344751b89/langchain/text_splitter.py#L58) ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [X] The code builds clean without any errors or warnings - [X] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) - [X] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with `dotnet format` - [X] All unit tests pass, and I have added new tests where possible - [X] I didn't break anyone 😄 --------- Co-authored-by: Scott Graham <scgraham@microsoft.com> Co-authored-by: Lee Miller <lemiller@microsoft.com> Co-authored-by: Mark Karle <mkarle@users.noreply.github.com> Co-authored-by: Shawn Callegari <36091529+shawncal@users.noreply.github.com>
### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> Upgrade duckdb to use strong named version ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [X] The code builds clean without any errors or warnings - [X] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) - [X] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with `dotnet format` - [X] All unit tests pass, and I have added new tests where possible - [X] I didn't break anyone 😄
### Motivation and Context Update CopilotChat sample to the latest SK nuget version, absorbing breaking changes. **I've done zero testing on this, other than "it builds", so we'll want to validate it before merging.** cc: @shawncal This cleans up some cruft related to skill definitions, though there's still likely more that can be done for someone more familiar than I am with this code. I expect we'll be able to clean it up further once the exception handling changes land, as there's a lot of code dedicated to checking whether an error has occurred and short-circuiting if one has. (@SergeyMenshykh, this would be a good one to pay attention to, in particular around how exceptions propagate out of semantic functions instead of relying on manual checking of the returned context.) ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [x] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) - [x] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with `dotnet format` - [x] All unit tests pass, and I have added new tests where possible - [x] I didn't break anyone 😄 Co-authored-by: Gina Triolo <51341242+gitri-ms@users.noreply.github.com> Co-authored-by: Chris <66376200+crickman@users.noreply.github.com>
Also included: - Removing FileCompression project - no longer used - Merging GitHubSkill into KernelHttpServer - rename to GitHubPlugin (...the first of many to receive such treatment) - this is where it's used, and it will allow us to instantiate the github skill without passing the access token as a context variable (this change not yet implemented). - Removing LoadPromptsFromCloud - we are moving to a "plugin-first" approach - loading plugins, not raw prompts. This approach is no longer recommended. Resolves microsoft#1876 --------- Co-authored-by: Gina Triolo <51341242+gitri-ms@users.noreply.github.com>
…oft#1912) ### Motivation and Context Please help reviewers and future users, providing the following information: 1. Why is this change required? It's a simple bug fix to account for namespace updates 3. What problem does it solve? The memory and embedding notebook still uses the previous skills namespace and thus breaks 5. What scenario does it contribute to? Notebooks 7. If it fixes an open issue, please link to the issue here. ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> Just a line change ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [X] The code builds clean without any errors or warnings - [X] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) - [X] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with `dotnet format` - [X] All unit tests pass, and I have added new tests where possible - [X] I didn't break anyone 😄
github-actions
bot
added
documentation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation and Context
Description
Contribution Checklist
dotnet format