54442a3ca7
Bumps [golang.org/x/tools](https://github.com/golang/tools) from 0.9.1 to 0.9.2. <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.2</h2> <p>This release contains many bug fixes, particularly related to problems that would require restarting gopls.</p> <p><strong>Note about network usage</strong>: among these fixes was a change to allow network usage when reloading the workspace. Reloading occurs when a <code>go.mod</code>, <code>go.sum</code>, or <code>go.work</code> file changes on disk. In the past, gopls would only allow network during the first workspace load. This resulted in confusing behavior when, for example, a new dependency is added to a <code>go.mod</code> file and gopls could not load it, but loading succeeded on restart. See <a href="https://go.dev/issues/54069">#54069</a> for more details.</p> <h2>Configuration changes</h2> <h3>directoryFilters at arbitrary depth</h3> <p>The <a href="https://github.com/golang/tools/blob/master/gopls/doc/settings.md#directoryfilters-string"><code>"directoryFilters"</code></a> setting now supports excluding directories at arbitrary depth, using the <code>**</code> operator. (note that for v0.9.2, the default value for this setting is still <code>["-node_modules]"</code>. In the next release, this will change to <code>["-**/node_modules"]</code>).</p> <h2>Bug fixes and Performance improvements...</h2> <p>This release contains the following notable bug fixes / performance improvements:</p> <ul> <li><strong>Additional change optimization</strong> - Following up on the work to optimize change processing from the <a href="https://github.com/golang/tools/releases/tag/gopls%2Fv0.9.0">v0.9.0 release</a>, this release contains additional optimizations that result in around 50% faster change processing (measured via edits in the Kubernetes repo).</li> <li><strong>Fix for a long-standing memory leak</strong> - <a href="https://go.dev/issues/53780">#53780</a> fixed a long-standing bug that caused gopls to hold on to its initial state, gradually leaking memory as state changed during the editing session.</li> <li><strong>Fewer restarts</strong> - This release contains many fixes for cache-invalidation bugs that would cause gopls to get confused and require restarting. Additionally, see the note at top about enabling the network when reloading the workspace. We believe we are close to our goal that restarting gopls should never be required to fix workspace errors. If you encounter such a bug, please file an issue!</li> </ul> <p>A full list of all issues fixed can be found in the <a href="https://github.com/golang/go/milestone/274?closed=1">gopls/v0.9.2 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/antoineco"><code>@antoineco</code></a>, <a href="https://github.com/dle8"><code>@dle8</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/mssdvd"><code>@mssdvd</code></a>, <a href="https://github.com/pjweinbgo"><code>@pjweinbgo</code></a>, <a href="https://github.com/rentziass"><code>@rentziass</code></a>, and <a href="https://github.com/suzmue"><code>@suzmue</code></a>!</p> <h2>What's next</h2> <p>The next planned gopls release is <a href="https://github.com/golang/go/milestone/278">v0.10.0</a>. We’re excited about features and improvements on the horizon, for example:</p> <ul> <li>Package renaming (<a href="https://go.dev/issues/41567">#41567</a>)</li> <li>More accurate static-analysis (<a href="https://go.dev/issues/48738">#48738</a>)</li> <li>Improved support for the new 1.19 doc comment format (<a href="https://go.dev/issues/54260">#54260</a>)</li> <li>Making it easier to work with <code>go.work</code> files (many issues, for example <a href="https://go.dev/issues/53880">#53880</a> or <a href="https://go.dev/issues/54261">#54261</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="96844c3594"><code>96844c3</code></a> cmd/{guru,callgraph}: stop using go/pointer</li> <li><a href="cd694d8db4"><code>cd694d8</code></a> go/packages: include "unsafe".GoFiles=["unsafe.go"]</li> <li><a href="33c741de78"><code>33c741d</code></a> gopls/internal/lsp: add min/max builtin</li> <li><a href="933c7ccb15"><code>933c7cc</code></a> internal/lsp/source: use exact match in import highlighting</li> <li><a href="5974258e68"><code>5974258</code></a> gopls/internal/lsp: clear vuln diagnostics on config changes</li> <li><a href="f3faea1982"><code>f3faea1</code></a> go/packages: pass -pgo=off on go1.21 and later</li> <li><a href="5f74ec7da5"><code>5f74ec7</code></a> internal/lsp/debug: add links to profiles and GC</li> <li><a href="ed90c6d201"><code>ed90c6d</code></a> internal/diff: unexport various identifiers</li> <li><a href="827f5aa2c3"><code>827f5aa</code></a> gopls/internal/lsp/source: test references bug on struct{p.T}</li> <li><a href="a12e1a6aee"><code>a12e1a6</code></a> go/ssa/interp: implement min/max builtins</li> <li>Additional commits viewable in <a href="https://github.com/golang/tools/compare/v0.9.1...v0.9.2">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.