Known Issues and Limits

Known bugs

The following are known bugs that we are tracking but have not yet fixed:

  • AI-generated issue explanations are sometimes inaccurate
  • Specifying plugin versions as latest does not automatically stay up to date

We expect to fix these bugs within the coming weeks and months. If one of these bugs is causing you an issue, please let us know and we will try to move it up our backlog.

Gaps compared to prior edition

The following are features of the previous edition of Quality which we have not yet implemented:

  • Trends
  • Slack and email notifications
  • Hotspots based on commit activity
  • Maintainability rating changes
  • Atlassian Jira integration
  • Badges
  • REST API
  • GitHub Merge Queue support

If one of these gaps is preventing you from moving to Qlty, please let us know and we will try to priortize it.

We expect to close all of these gaps by the end of 2024 if not sooner.

Limits

Analysis limits

  • Maximum size of a file we will attempt to analyze: 2 megabytes
  • Maximum depth of an AST we will visit: 1024 levels
  • Maximum files linted in a single batch: 512

Pull request review limits

To ensure optimal performance and avoid timeouts during pull request reviews, Qlty imposes the following limits:

  • Maximum number of files in a diff: 300
  • Maximum number of comments per file: 30
  • Maximum number of comments per review: 50

These constraints help maintain efficient analysis and review processes within the system.

Timeouts

  • Pull request analysis: 10 minutes
  • Branch analysis: 30 minutes

Rate limits

Requests made by Qlty to the GitHub API are subject to GitHub’s rate limits. To ensure the security and availability of the system, we may impose additional rate limits.