### Description
This PR adds the Dapr runtime for Processes. The runtime is very similar
in concept to the local runtime with a few changes to accommodate the
single threaded remote actors.
A new Demo has also been added called `ProcessWithDapr` that shows a
asp.net core service with Dapr configured. The sample has a single API
that triggers a simple process to run within Dapr. This sample is still
very basic and more work is needed to demonstrate all the patterns that
can be used with Processes.
### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [x] The code builds clean without any errors or warnings
- [x] The PR follows the [SK Contribution
Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
and the [pre-submission formatting
script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts)
raises no violations
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄
---------
Co-authored-by: Ben Thomas <[email protected]>
### Description
This PR is the first in a series that will enable the Dapr runtime for
Processes. This change makes adjustments to the abstractions and core
builder that are mainly focused on supporting the DataContract
serialization used for Dapr actor remoted function calling.
### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [x] The code builds clean without any errors or warnings
- [x] The PR follows the [SK Contribution
Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
and the [pre-submission formatting
script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts)
raises no violations
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄
---------
Co-authored-by: Ben Thomas <[email protected]>
Co-authored-by: Chris <[email protected]>
### Motivation and Context
Closes#6166
### 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 the [SK Contribution
Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
and the [pre-submission formatting
script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts)
raises no violations
- [ ] All unit tests pass, and I have added new tests where possible
- [ ] 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.
-->
### 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 the [SK Contribution
Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
and the [pre-submission formatting
script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts)
raises no violations
- [ ] All unit tests pass, and I have added new tests where possible
- [ ] I didn't break anyone 😄
### Motivation and Context
Currently, users in Python have no ability to configure default_headers
for the AzureOpenAI/OpenAI clients we use. Additionally, if a user wants
to set up their own AzureOpenAI/OpenAI client, this isn't possible. This
PR addresses #2895.
<!-- 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
Allow users to set default_headers for Chat/Text/Embedding Completion
classes for both OpenAI and AzureOpenAI. Additionally, allow users to
pass in a customer OpenAI/AzureOpenAI client, if desired. Update tests
accordingly.
<!-- 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 the [SK Contribution
Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
and the [pre-submission formatting
script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts)
raises no violations
- [ ] All unit tests pass, and I have added new tests where possible
- [ ] I didn't break anyone 😄
---------
Co-authored-by: Evan Mattson <[email protected]>
### Motivation and Context
Adding the experimental attribute to packages and classes in the .NET
SDK of Semantic Kernel to mark things that won't be ready be v1.0.0 of
Semantic Kernel.
### Contribution Checklist
- [ ] The code builds clean without any errors or warnings
- [ ] The PR follows the [SK Contribution
Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
and the [pre-submission formatting
script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts)
raises no violations
- [ ] All unit tests pass, and I have added new tests where possible
- [ ] I didn't break anyone 😄
---------
Co-authored-by: Mark Wallace <[email protected]>
### 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)
### Motivation and Context
This sample continues in the spirit of prior samples in the samples/apps
folder with a goal of teaching developers how the concepts of memory and
embeddings can be integrated.
### Description
This sample includes a frontend app that allows the developer to enter
the address of a publicly available Github repository, which is
downloaded to the temp directory of the machine hosting the
KernelHttpService sample application (can be the same machine).
Once downloaded the developer is able to have a conversation with the
repository and see the impact of the relevance slider on the responses.
---------
Co-authored-by: Craig Presti <[email protected]>
Co-authored-by: teresaqhoang <[email protected]>
Co-authored-by: markwallace-microsoft <[email protected]>
Co-authored-by: Tao Chen <[email protected]>
Co-authored-by: Mark Wallace <[email protected]>
Co-authored-by: Devis Lucato <[email protected]>
Co-authored-by: Devis Lucato <[email protected]>
Co-authored-by: Adrian Bonar <[email protected]>
