Closed
Description
We have a (currently) private fuzzer/crawler which simply opens projects on GitHub, runs some language server operations on a project, and finds crashes. This helps pinpoint stability issues in TypeScript and the server so that we can improve reliability.
It has helped catch many issues over the years, but we believe that there are some opportunities to improve it:
- Now that we have a better idea of the primary functionality, we would benefit from a rewrite - possibly where we can leverage other infrastructure
- The crawler continues to ping about the same issue over and over again. This is okay, and helpful for knowing what issues we've continued to encounter, but maybe a better approach is to have reports of new issues that have been introduced that don't repro in the last stable version of the language service (similar to the new errors detector we run weekly/on-demand)