An issue was identified in Airlock’s API request handling and pagination logic. Airlock APIs were designed to return responses only under one of two conditions: (1) a full page containing 10,000 records, or (2) a terminal response indicating that no additional data remained.
For long-running queries spanning large time ranges, the Airlock server could exceed the client-side timeout configured in the Airlock library while aggregating the result set. When this occurred, the client library would time out and terminate the request prematurely, despite additional data being available. Because the response had not yet reached the 10,000-record threshold and did not represent the end of the dataset, the API did not return a partial result, resulting in data loss for that request.
An issue was identified in Airlock’s API request handling and pagination logic. Airlock APIs were designed to return responses only under one of two conditions: (1) a full page containing 10,000 records, or (2) a terminal response indicating that no additional data remained.
For long-running queries spanning large time ranges, the Airlock server could exceed the client-side timeout configured in the Airlock library while aggregating the result set. When this occurred, the client library would time out and terminate the request prematurely, despite additional data being available. Because the response had not yet reached the 10,000-record threshold and did not represent the end of the dataset, the API did not return a partial result, resulting in data loss for that request.
mysticmomba
added the bug label 2026-01-16 16:04:10 -05:00
mysticmomba
self-assigned this 2026-01-16 16:04:10 -05:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
An issue was identified in Airlock’s API request handling and pagination logic. Airlock APIs were designed to return responses only under one of two conditions: (1) a full page containing 10,000 records, or (2) a terminal response indicating that no additional data remained.
For long-running queries spanning large time ranges, the Airlock server could exceed the client-side timeout configured in the Airlock library while aggregating the result set. When this occurred, the client library would time out and terminate the request prematurely, despite additional data being available. Because the response had not yet reached the 10,000-record threshold and did not represent the end of the dataset, the API did not return a partial result, resulting in data loss for that request.