Why is "fortran" censored in the log display? #27210
-
This is an odd one, but I noticed it today in trying to get GitHub Actions working on a repo. Namely, when I watch the log output scroll by I see:
for this bit of the yaml file:
and in one of the steps I have:
and the output is:
And then later on in the logging:
Each one of those Note: things seem to work, but I’m just really baffled by this. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
That is a bit weird. 🤔 Do you have a secret that contains |
Beta Was this translation helpful? Give feedback.
-
@thomasshaped Oooh. I did not know that exisited! Guess what I added to this workflow when I was updating it? Docker Hub Authorization for my image pull because of the whole “limits on anonymous pulls” thing they announced. And want to guess my Docker Hub username? (Not too much of a reveal as it’s my default internet username almost everywhere.) Though now as I read actions/runner-images#1445, maybe I don’t need to worry? Sounds like GitHub might have reached an agreement that it isn’t needed for public images pulls into GitHub Actions? Sigh. Thanks. Weird mystery solved. (Though I guess this could make a very inefficient attack on secrets.) |
Beta Was this translation helpful? Give feedback.
-
Oh no way, wild guess but I’m glad it was right! 😅
mathomp4:
I believe this is the case, yep! Public pulls of images should not be affected by these rate limits when used on GitHub-hosted runners. |
Beta Was this translation helpful? Give feedback.
That is a bit weird. 🤔 Do you have a secret that contains
fortran
in it? It might be the secret masker that’s doing it.