re-run github action manually or automatically when tinytex error occurs about case-studies HOT 5 CLOSED

I have a few ideas but I am not sure if either of them will work

1. Try to install tinytex a different way so it is already available before the quarto install
2. Use a different operating system than Mac

from case-studies.

Update: recent failed action required 4 tries to get past this error. Still not clear if it's worth doing anything other than re-running actions manually, but wanted to make sure we have a record of what it can take to get working.

from case-studies.

Ugh, this seems really frustrating! I don't understand why we would be seeing this issue, but the quarto actions folks do not.

I wonder if we could pin the tinytex version and if that would change the need to rerun? I can't think of anything else to try.

from case-studies.

Here's a suggested fix for our error using GITHUB_TOKEN: quarto-dev/quarto-actions#105 (comment).

@Bai-Li-NOAA or @k-doering-NOAA, you two are more familiar with tokens than me. Is the setting of GITHUB_PAT: ${{ secrets.GITHUB_TOKEN }} on line 11 of both of our case-studies workflows already implementing this (and thus the problem has some other origin), or do we need to explicitly provide it under the Set up Quarto step? I also don't understand the difference between GITHUB_PAT (which we have in place) and GH_TOKEN (in the suggested fix). Because the problem is intermittent, I'd rather not just use trial and error without a greater understanding of the elements involved in case it randomly works without actually being fixed.

from case-studies.

Ah, this is super helpful!

I think we should add this to the setup step:

      env:
        GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

based on the docs here. It seems like the setup step is looking for an environmental variable called GH_TOKEN, which we have not set.

If the problem persists, I think we can swap secrets.GITHUB_TOKEN for a personal access token.

from case-studies.