Troubleshoot common issues with DeepSource.
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:
Solutions:
.deepsource.toml
file to skip unnecessary files like:
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.
If you notice an incorrect Autofix suggestion:
This error can occur for several reasons:
Submodule issues
Default branch mismatch
VCS provider downtime
This happens when you’re using an Individual account rather than a Team/Organization account.
Account types:
Solution: To add team members, you need to use a Team/Organization account. Learn more about account management and adding team members.
granular
mode is selectedThis 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.
We don’t currently support diff analysis on non-default branches, but this feature is on our roadmap.
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:
Troubleshoot common issues with DeepSource.
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:
Solutions:
.deepsource.toml
file to skip unnecessary files like:
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.
If you notice an incorrect Autofix suggestion:
This error can occur for several reasons:
Submodule issues
Default branch mismatch
VCS provider downtime
This happens when you’re using an Individual account rather than a Team/Organization account.
Account types:
Solution: To add team members, you need to use a Team/Organization account. Learn more about account management and adding team members.
granular
mode is selectedThis 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.
We don’t currently support diff analysis on non-default branches, but this feature is on our roadmap.
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: