You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
Current implementation of Code Inspection waits for all linters to finish before rendering the results in the problems panel. It may become significantly noticeable with the introduction of asynchronous linters which may use a network service or significant amount of time to prepare for the first run. "Fast" linters which provide results quickly should not be dependent on long-running provider to deliver the results. At the same time, on the other hand, should not be discriminating long-running providers, hence the timeout mechanism which #6530 introduces should be replaced with by decoupling providers' execution and render the result immediately once a provider delivers them.
The text was updated successfully, but these errors were encountered:
Current implementation of Code Inspection waits for all linters to finish before rendering the results in the problems panel. It may become significantly noticeable with the introduction of asynchronous linters which may use a network service or significant amount of time to prepare for the first run. "Fast" linters which provide results quickly should not be dependent on long-running provider to deliver the results. At the same time, on the other hand, should not be discriminating long-running providers, hence the timeout mechanism which #6530 introduces should be replaced with by decoupling providers' execution and render the result immediately once a provider delivers them.
The text was updated successfully, but these errors were encountered: