New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2100 parameter limit when querying artifacts #5371
Comments
Here is a linqpad script which can be used to reproduce the bug on
|
Release Note: Fixed a bug where you could not fetch artifacts for releases with a large number of deployments |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately. |
The bug
Hit the endpoint
/api/artifacts?regarding=Releases-1234
. If the release has more than 2100 associated deployments, the underlying sql query will fail because it hits the 2100 sql parameter limit.What I expected to happen
The request should succeed
Log exerpt
Affected versions
Octopus Server: 2019.2.2 and earlier
Links
https://help.octopus.com/t/error-when-release-has-been-deployed-too-many-times/22485
The text was updated successfully, but these errors were encountered: