Oliver Mannion

To resolve, use the following permissions under the workflow or job in your workflow yaml: ```yaml permissions: checks: write ```

I would use this!

ICYMI like I did, for short type hints, eg: ```python @app.get("/path/") async def foo( q: str | None = Query(None, title="Some long title", description="Some long description") ): pass ``` you...

I'd be happy to raise a PR for this if you think it worthwhile.

Thank you for considering this! The main wrapper works well. By interactive usage I mean someone running `pyright` on the command line and waiting for results as opposed to CI...

Also seeing this with these call stacks: ``` [2023-07-29 01:25:19.938] [INFO] Worker: Looking for /Users/tekumara/code3/release-please in Error: at findCallLocation (/Users/tekumara/.vscode/extensions/hbenl.vscode-mocha-test-adapter-2.14.1/out/worker/bundle.js:918:17) at /Users/tekumara/.vscode/extensions/hbenl.vscode-mocha-test-adapter-2.14.1/out/worker/bundle.js:909:30 at exports.it (/Users/tekumara/code3/release-please/node_modules/mocha/lib/mocha.js:127:53) at Suite. (/Users/tekumara/code3/release-please/test/factories/changelog-notes-factory.ts:42:9) at Object.create...

We've seen this on jupyterlab 4.1.2 (pip installed) but its client specific, ie: the error will reliably surface from some laptops connecting to the ec2 via [vscode port-forwarding](https://code.visualstudio.com/docs/remote/ssh#_forwarding-a-port-creating-ssh-tunnel) but not...

See also the [prefix.dev resolver](https://x.com/prefix_dev/status/1700109553516327135)

I personally would like a VS Code `typos` extension because I get too many false positives from dictionary-based spell checkers. I think it would be more efficient to run `typos`...

I don't know of any LSP registry as such. The server could be either a separate binary, eg: `typos-lsp` or a flag in the existing binary that starts the server...