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

Merge main into live #42477

Merged
merged 13 commits into from
Sep 5, 2024
Merged

Merge main into live #42477

merged 13 commits into from
Sep 5, 2024

Conversation

BillWagner and others added 13 commits September 4, 2024 09:46
Change the example file name. Because managed identity is generally better than connection strings, don't imply that we're using connection strings.
Bumps the dotnet group in /docs/ai/tutorials/snippets/llm-eval with 1 update: [Microsoft.SemanticKernel](https://github.com/microsoft/semantic-kernel).


Updates `Microsoft.SemanticKernel` from 1.17.2 to 1.18.2
- [Release notes](https://github.com/microsoft/semantic-kernel/releases)
- [Commits](microsoft/semantic-kernel@dotnet-1.17.2...dotnet-1.18.2)

---
updated-dependencies:
- dependency-name: Microsoft.SemanticKernel
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
The EventPipe docs were saying things about LTTng that were either incorrect or misleading. I think changing the comparison to use perf_events makes it more effective.

- LTTng does support tracing kernel events, but as written users are likely to get the wrong idea. Perfcollect, the tool we recommend to when using LTTng with .NET, uses perf_events rather than LTTng to perform the kernel tracing. Perfcollect only uses lttng for its user-mode tracing capability.
- LTTng doesn't support native callstacks as far as I am aware.
Sets the output sample's code type to `text` to avoid CLI type highlighting.
Markdown lint fix
@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

@dotnet-bot dotnet-bot added this to the September 2024 milestone Sep 5, 2024
@dotnet-policy-service dotnet-policy-service bot merged commit 3d4f018 into live Sep 5, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.