Joachim Jablon

Hm, I was able to get logs on a different run. Maybe the problem was with my run...?

Your script does `gh api /repos/$REPO_NAME/actions/runs/$RUN_ID/logs` (https://docs.github.com/en/rest/actions/workflow-runs#download-workflow-run-attempt-logs) What I tried was `gh api -i '/repos/{owner}/{repo}/actions/jobs/7956708541/logs'` (https://docs.github.com/en/rest/actions/workflow-jobs#download-job-logs-for-a-workflow-run) This ticket is mainly about `gh run view --log` and I mentioned the API...

At this point I'm reasonably convinced that when the output is bigger than a certain threshold, some layer under the surface decides it's too much and removes it entirely, silently....

Thanks for your answer. I'm a bit surprised that you read the part on the MITM as FUD, and I'm sorry that I phrased it this way. I totally get...

Yes, that's probably the reason :/

I can't say for sure. I believe it may be possible, but it might require that someone changes the way the sync/async translation works within procrastinate, and I'm not sure...

Ok, sync+async is a mistake and I should never have tried to have procrastinate work on both :D (not being sarcastic, I really regret the choice, but I wont be...

I guess we would need to make as much as possible of the procrastinate code independant from I/Os (fortunately, this is already what happens in many parts of the codebase,...

Worker heavily uses tasks, sadly... but we'll need a full rewrite anyway...

[Screencast from 13-01-2023 13:28:39.webm](https://user-images.githubusercontent.com/1457576/212320577-162245e1-6daf-4e85-a39e-bcd3d95745ca.webm) Nice ! 2 very optional comments: - The way "ctrl+p" menus usually work is that when you press enter, the first element is activated. In this...