False Positive When Linting Large Amount of Files

Bug description

When in a workspace and when using a linter on a large amount of files (in this case ~7000 files) it will get caught by agent-smith and the workspace will be stopped and user blocked. I recommend viewing the attached support ticket for further information.

Google Logs Entry.

Steps to reproduce

1. Clone
2. Spin up a new workspace using that repository.
3. Using your linting tool have it lint all ~7000 files - you may need to use something like a for loop.

--

The following steps are untested (I didn't want to block my own account), but in theory this should reproduce the issue.

1. Create a new workspace from https://github.com/tldr-pages/tldr
2. Run npm test.
3. Observe the workspace is stopped and your account is blocked.

Review this function.

Workspace affected

45554c37-bd17-4d8d-9a02-1a1ffce21a7e

Expected behavior

Given that this is not nefarious or malicious behavior I wouldn't expect to get my account blocked when linting files.

Example repository

https://github.com/tldr-pages/tldr

Anything else?

N/A

Front conversations

Start with the linked Google Logs entry and the agent-smith behavior described in the report. Review scripts/test.sh in the tldr-pages/tldr repository and run npm test only in a safe workspace; done means linting roughly 7,000 files no longer incorrectly stops the workspace or blocks the user.