Getting Error while fetching the Get Operation API

[PrajwalTM]

Summary:
When attempting to fetch operations using the get operation API, the request takes an excessively long time to respond and often hangs, preventing successful retrieval of operation details in Swagger. This issue occurs when there are 40 or more operations in the system.

Description:
We have encountered a significant performance issue with the get operation API. The API call is intended to fetch the details of operations, but when the number of operations exceeds 40, the request becomes very slow and often hangs indefinitely. This behavior is observed in both our application and the Swagger UI, where the operation details fail to load.

Steps to Reproduce:

• Create 40 or more operations in the system.
• Open Swagger UI or use any API client (e.g., Postman) to send a GET request to the get operation API endpoint.
• Observe the response time and check if the operation details are retrieved successfully.
• Expected Behavior:
• The get operation API should respond in a reasonable amount of time and return the operation details without hanging, regardless of the number of operations present.

Actual Behavior:

• The get operation API takes an excessively long time to respond when there are 40 or more operations.
• The API request frequently hangs, resulting in no operation details being retrieved.
• Swagger UI fails to display the operation details due to the hanging issue.

Environment:

• Application Version: 4.2.0
• API Endpoint: get/api/v2/operations
• Browser (if using Swagger UI): Chrome

Additional Information:

• The issue does not occur when there are fewer than 40 operations.
• This problem is impacting our ability to monitor and manage operations effectively.
• No error messages are returned; the request simply hangs.

[github-actions]

Looks like your first issue -- we aim to respond to issues as quickly as possible. In the meantime, check out our documentation here: http://caldera.readthedocs.io/

[L015H4CK]

As a side note: I encounter the same problem when getting all abilities using the API and version 5.0.0. So I think it is not operation-specific. I guess the API/Caldera simply does not support large amounts of data.

[elegantmoose]

@PrajwalTM So we made some changes in the frontend (mitre/magma#53) to make the operation polling more performant. If repull Master, (hopefully) should have no issue.

[elegantmoose]

@L015H4CK That makes sense, as I dont recall us putting in paging yet.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days