Do CI trace pages continue to poll after the job is finished?

There is currently some work underway to investigate peak-per-minute usage from users, in preparation for tighter rate limiting restrictions.

Interestingly, many of the worst offenders we've found has been the Projects::JobsController#trace endpoint.

We've been able to find examples of this endpoint peaking at several hundred requests per minute from what appears to be a single browser instance.

In other cases, it appears that people leave their browser tabs open for days, long after jobs have finished running, but still incurring high costs polling.

In one case, what appears to be a single browser issued 30k requests for traces over several days. This led to 50,000 redis calls and 120,000 database calls.

If we could disable polling after the job had completed, we could reduce load on our servers, and costs.