James C. (Jamie) Davis

The code to change is [here](https://github.com/davisjam/vuln-regex-detector/blob/master/src/cache/server/validate-uploads.js#L258) in validate-uploads.

@immo-huneke-zuhlke Thanks for the heads up. I will get this fixed pronto.

This behavior is by design. Testing a regex can take worst-case `O(minutes)/regex * #regexes in line` so I don't see a way to get a response truly synchronously without holding...

> If the service returns "UNKNOWN", this is not helpful at all and strongly hurts usability. The intended use case is CI (see my "[pseudo eslint plugin](https://www.npmjs.com/package/eslint-plugin-vuln-regex-detector)") where the code...

See [here for whole repo docs](https://github.com/davisjam/vuln-regex-detector) and [here for bin/ docs](https://github.com/davisjam/vuln-regex-detector/tree/master/bin).

Do let me know your thoughts when you've had a chance to look it over.

It looks like a microservices approach like AWS Lambda might be a good fit for a "don't reply until you have an answer" design. The expected workload should fit in...

`validate-uploads.js` could also use some parallelism.

That's a bit surprising because I don't believe I deployed the recent pushes to the server. But I will take a look. Thanks! This might instead be due to certificate...

> Is it actually necessary to run the configure command if I'm only trying to use the client? Nope. You just need to point the module at an appropriate endpoint...