You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a log table already, but it fetches logs of all steps in a job. This is often too much to handle in a single page.
Instead, it would be useful to try to fetch logs for particular steps in a job, after identifying failing steps. This is not documented, but the URL is: {owner}/{repo}/commit/{sha}/checks/{jobId}/logs/{stepNumber}. This could map to a table called step_logs and would have to support predicate pushdown for all params in that URL.
The text was updated successfully, but these errors were encountered:
There's a log table already, but it fetches logs of all steps in a job. This is often too much to handle in a single page.
Instead, it would be useful to try to fetch logs for particular steps in a job, after identifying failing steps. This is not documented, but the URL is:
{owner}/{repo}/commit/{sha}/checks/{jobId}/logs/{stepNumber}
. This could map to a table calledstep_logs
and would have to support predicate pushdown for all params in that URL.The text was updated successfully, but these errors were encountered: