49bef351d9
Bumps [golang.org/x/tools](https://github.com/golang/tools) from 0.8.0 to 0.9.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/golang/tools/releases">golang.org/x/tools's releases</a>.</em></p> <blockquote> <h2>gopls/v0.9.1</h2> <p>This release fixes a regression in the v0.9.0 release: a crash when running the <code>go:generate</code><code>golang/go#53781</code></p> <p>Thank you to all those who filed crash reports, and apologies for the breakage!</p> <h2>gopls@v0.9.0</h2> <p>This release contains significant performance improvements (especially in incremental processing after source changes), bug fixes, and support for the LSP “<a href="https://redirect.github.com/microsoft/language-server-protocol/issues/956">inlay hints</a>” feature, along with several other minor enhancements.</p> <h2>Performance improvements</h2> <p>Source edits cause gopls to invalidate and recompute information about the workspace, most of which has not changed. Previously, gopls would spend significant CPU copying data structures, sometimes more than 100ms per keystroke in a large workspace. This release includes many optimizations to avoid copying data needlessly, including a new <a href="https://cs.opensource.google/go/x/tools/+/gopls-release-branch.0.9:internal/persistent/map.go;l=26-37">map representation</a> to achieve copying in constant time. Special thanks to <a href="https://github.com/euroelessar"><code>@euroelessar</code></a> for the design and implementation of this data structure.</p> <p>As a result of these improvements, gopls should be more responsive while typing in large codebases, though it will still use a lot of memory.</p> <p>Time to process a change notification in the Kubernetes repo: <img src="https://user-images.githubusercontent.com/57144380/176967584-a8040048-6357-40d5-9d80-c448281f6482.png" alt="image" /></p> <h2>New Features</h2> <h3>Inlay hints</h3> <p>Added support for displaying inlay hints of composite literal field names and types, constant values, function parameter names, function type params, and short variable declarations. You can try these out in the <a href="https://github.com/golang/vscode-go/blob/master/docs/nightly.md">vscode-go nightly</a> by <a href="https://github.com/golang/vscode-go/blob/master/docs/settings.md#goinlayhintsassignvariabletypes">enabling inlay hints settings</a>.</p> <p><img src="https://user-images.githubusercontent.com/57144380/176967591-a7b767b3-d447-4691-9486-10f957dc9a0f.gif" alt="image3" /></p> <h3>Package References</h3> <p>Find references on <code>package foo</code> now lists locations where the given package is imported.</p> <h3>Quick-fix to add field names to struct literals</h3> <p>A new quick fix adds field names to struct literals with unkeyed fields.</p> <p><img src="https://user-images.githubusercontent.com/57144380/176967261-6acbe0e7-7698-46ea-8deb-cbd913296034.gif" alt="image1" /></p> <h2>Bug fixes</h2> <p>This release includes the following notable bugfixes:</p> <ul> <li>Fixes for goimports performance and correctness when using a go.work file (<a href="https://go.dev/issue/52784">#52784</a>)</li> <li>Fix a crash during renaming in a package that uses generics (<a href="https://go.dev/issue/52940">#52940</a>)</li> <li>Fix gopls getting confused when moving a file from the <code>foo_test</code> package to <code>foo</code> package (<a href="https://redirect.github.com/golang/go/issues/45317">#45317</a>)</li> </ul> <p>A full list of all issues fixed can be found in the <a href="https://github.com/golang/go/milestone/260">gopls/v0.9.0 milestone</a>. To report a new problem, please file a new issue at <a href="https://go.dev/issues/new">https://go.dev/issues/new</a>.</p> <h2>Thank you to our contributors!</h2> <p>Thank you for your contribution, <a href="https://github.com/alandonovan"><code>@alandonovan</code></a>, <a href="https://github.com/euroelessar"><code>@euroelessar</code></a>, <a href="https://github.com/findleyr"><code>@findleyr</code></a>, <a href="https://github.com/hyangah"><code>@hyangah</code></a>, <a href="https://github.com/jamalc"><code>@jamalc</code></a>, <a href="https://github.com/jba"><code>@jba</code></a>, <a href="https://github.com/marwan-at-work"><code>@marwan-at-work</code></a>, <a href="https://github.com/suzmue"><code>@suzmue</code></a>, and <a href="https://github.com/dle8"><code>@dle8</code></a>!</p> <h2>What’s Next?</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="4609d79b05"><code>4609d79</code></a> cmd/bisect: add -compile and -godebug shorthands</li> <li><a href="ddfa2200ae"><code>ddfa220</code></a> internal/fuzzy: improvements to the symbol scoring algorithm</li> <li><a href="344924276c"><code>3449242</code></a> go/types/objectpath: don't panic when receiver is missing a method</li> <li><a href="0809ec2e45"><code>0809ec2</code></a> gopls/internal/lsp/source: document {All,Workspace}Metadata</li> <li><a href="8f7fb01dd4"><code>8f7fb01</code></a> go/analysis/unitchecker: add test of go vet on std</li> <li><a href="23e52a3e12"><code>23e52a3</code></a> bisect: diagnose bad targets better</li> <li><a href="d5af8894fe"><code>d5af889</code></a> gopls: set GOWORK=off for loads from debug and safetoken tests</li> <li><a href="c93329a947"><code>c93329a</code></a> go/analysis/passes/printf: reshorten diagnostic about %s in Println call</li> <li><a href="62197261cf"><code>6219726</code></a> go.mod: update golang.org/x dependencies</li> <li><a href="f4d143ebcd"><code>f4d143e</code></a> go/ssa: cleanup TestGenericBodies to pickup package name</li> <li>Additional commits viewable in <a href="https://github.com/golang/tools/compare/v0.8.0...v0.9.1">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) You can trigger a rebase of this PR 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>
Corso
Corso is the first open-source tool that aims to assist IT admins with the critical task of protecting their Microsoft 365 data. It provides a reliable, secure, and efficient data protection engine. Admins decide where to store the backup data and have the flexibility to perform backups of their desired service through an intuitive interface. As Corso evolves, it can become a great building block for more complex data protection workflows.
Corso is currently in Beta.
Corso supports M365 Exchange and OneDrive with SharePoint and Teams support in active development. Coverage for more services, possibly beyond M365, will expand based on the interest and needs of the community.
Getting Started
See the Corso Quickstart on our docs page.
Building Corso
To learn more about working with the project source core and building Corso, see the Developer section of the Corso Documentation.
Roadmap
You can learn more about the Corso roadmap and how to interpret it here.
If you have feature requests, please file a GitHub issue
and attach the enhancement label to the issue.
Contribution Guidelines
Code of Conduct
It's important that our community is inclusive and respectful of everyone. We ask that all Corso users and contributors take a few minutes to review our Code of Conduct.
License
Corso is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.