Troubleshooting

Why is my analysis timing out?

DeepSource currently has a 25-minute time limit for completing analysis. If analysis doesn't finish within this period, you'll see an "Analysis timed out" message.

Common causes:

• First-time analysis of a repository (when all files are analyzed)
• Large repositories with many files
• Complex code that requires deeper analysis

Solutions:

1. Configure excluded file patterns in Settings > Code Review to skip unnecessary files like:
   • Test fixtures
   • Migration files
   • Example code
   • Generated code
   • Third-party libraries

Why do I see test coverage issues for lines that have not changed in my PR?

This typically occurs when your PR branch is not up-to-date with the default branch.

Solution: Rebase your PR branch with the default branch to synchronize the code and resolve this discrepancy.

DeepSource generated the wrong Autofix™. How do I report it?

If you notice an incorrect Autofix suggestion:

1. Take a screenshot or copy the relevant code snippet
2. Reach out to Support:
   • The screenshot/code snippet
   • A brief explanation of why the Autofix is incorrect
   • Name of the repository

Analysis fails, with the message "Error cloning git repository". What should I do?

This error can occur for several reasons:

1. Submodule issues

   • If your repository uses Git submodules, ensure DeepSource has access to them
   • Configure submodule access in your repository settings

2. Default branch mismatch

   • If your default branch has changed (e.g., from "master" to "main"), update this in DeepSource
   • Navigate to Settings > General to change the default branch name
   • Learn more about branch settings

3. VCS provider downtime

   • Rarely, this can be due to GitHub/GitLab/Bitbucket/AzureDevOps service issues and downtime
   • Check status page of respective services and wait a short while and retry the analysis

Why can't I find the option to add team members?

This happens when you're using an Individual account rather than a Team/Organization account.

Account types:

• Individual accounts are connected to personal GitHub, GitLab, Bitbucket or AzureDevOps accounts and don't support adding team members
• Team/Organization accounts are linked to GitHub organizations, GitLab groups, Bitbucket workspaces or AzureDevOps organizations

Solution: To add team members, you need to use a Team/Organization account. Learn more about account management and adding team members.

DeepSource shows issues in all files of the repository even when granular mode is selected

This occurs when a PR is opened against a non-default branch instead of the default branch.

Solution: Open your PR against the default branch to enable proper granular analysis.

CLI login is hanging or failing

If deepsource auth login opens a browser but never completes, or the login page doesn't load:

Common causes:

• Browser extensions (e.g., uBlock Origin, privacy blockers) interfering with the authentication redirect
• Corporate firewall or DNS restrictions blocking DeepSource domains

Solutions:

1. Try an incognito/private browser window with extensions disabled.
2. Try a different browser (e.g., Firefox if you normally use Chrome).
3. If you're behind a corporate firewall, confirm that deepsource.com and app.deepsource.com are allowed.

Code coverage not showing on the Metrics page

If the Metrics page shows "Not enough data" despite uploading coverage reports:

Why this happens: The Metrics page displays trends for the default branch only. If you're only uploading coverage reports on feature/PR branches, the default branch won't have any coverage data.

Solutions:

1. Upload coverage on the default branch — Update your CI pipeline to run deepsource report on pushes to the default branch, not just on pull requests.
2. Enable Report Inference — Go to Settings > Code Coverage and toggle on Report Inference. This infers coverage results from PR branches onto the default branch, so Metrics populate without changing your CI config.

Baseline scan timing out on a new repository

If the first analysis run times out after activating a new repository:

Common cause: The .deepsource.toml file was added to a branch while analysis was deactivated, or Code Review was enabled before the config was committed to the default branch.

Solution:

1. Ensure .deepsource.toml is committed to the repository's default branch first.
2. Then enable Code Review in Settings > Code Review.
3. If the repo is stuck, go to Settings > General and toggle analysis off and back on.

Analysis results are different on the same change in PR and in the default branch

When a PR includes changes to the .deepsource.toml configuration file, analysis results may differ between the PR and after merging to the default branch.

Why this happens: Configuration changes (like new exclude patterns or analyzer options) can affect how existing issues are reported. When merging to the default branch, DeepSource performs a full analysis with the updated configuration to ensure consistency.

Expected behavior:

• PRs receive granular analysis based on their specific changes
• Default branch receives full analysis after merging configuration changes to ensure all issues are properly updated