This repository has been archived by the owner on Oct 13, 2023. It is now read-only.
Resource not accessible by integration (no fork involved) #167
Labels
bug
Something isn't working
Comments
|
Raw log of |
blt
added a commit
to DataDog/lading
that referenced
this issue
Sep 14, 2022
We've lately started seeing actions-rs/clippy-check#167 in our own CI. As the actions-rs/clippy-check has not been updated since 2020 I'm going to say it's abandoned. Signed-off-by: Brian L. Troutwine <[email protected]>
blt
added a commit
to DataDog/lading
that referenced
this issue
Sep 14, 2022
We've lately started seeing actions-rs/clippy-check#167 in our own CI. As the actions-rs/clippy-check has not been updated since 2020 I'm going to say it's abandoned. Signed-off-by: Brian L. Troutwine <[email protected]>
blt
added a commit
to DataDog/lading
that referenced
this issue
Sep 15, 2022
* Avoid broken actions-rs/clippy-check We've lately started seeing actions-rs/clippy-check#167 in our own CI. As the actions-rs/clippy-check has not been updated since 2020 I'm going to say it's abandoned. Signed-off-by: Brian L. Troutwine <[email protected]> * --features -> --all-features Signed-off-by: Brian L. Troutwine <[email protected]>
domodwyer
added a commit
to domodwyer/anchorhash
that referenced
this issue
Nov 10, 2022
Run "cargo clippy" directly, rather than rely on the clippy action due
to:
actions-rs/clippy-check#167
domodwyer
added a commit
to domodwyer/anchorhash
that referenced
this issue
Nov 10, 2022
Run "cargo clippy" directly, rather than rely on the clippy action due
to:
actions-rs/clippy-check#167
|
Notwithstanding that this repo hasn't had a lot of recent action on it. Try changing the workflow permissions of your actions in the Repo settings.
This appeared to fix this issue for me. |
|
To resolve, use the following permissions under the workflow or job in your workflow yaml: permissions:
checks: write |
That fixes the issue for me ! Thanks a lot ! |
|
This should be added to the README |
|
Should also be added to the permissions btw |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Thank you for
actions-rsandactions-rs/clippy-check.Do the checklist before filing an issue:
actions-rsActions?I don't know. I'm new to GitHub actions. Please advise.
Yes.
Summary:
no_stdlibrary crates, plus one library crate (inside that same workspace, but not on crates.io: https://github.com/peter-kehl/no_std_rna_slice_patterns/tree/main/00_utils) shared by the rest (18) of the libraries). It requiresnightly.cargo checkandcargo clippyrun clear locallyWorkflow code
This is only for "check" job below. Both other jobs (
test" andmiri, also run withactions-rs`) do run well.https://github.com/peter-kehl/no_std_rna_slice_patterns/blob/927bf2bcda/.github/workflows/test.yml
It's almost a copy-and-paste (but not a fork) of https://github.com/prokopyl/selfie/blob/726013fc94/.github/workflows/test.yml, except that I use
nightlyonly. Surprisingly, that project's last GitHub actions run (on 28 July 2022) doesn't have a problem with the same jobcheck: https://github.com/prokopyl/selfie/runs/7564839812?check_suite_focus=true.Action output
https://github.com/peter-kehl/no_std_rna_slice_patterns/runs/8119158815?check_suite_focus=true ->
which ends with:
(Unsure if relevant:) The above looks a little different to the screenshot at #2, and it doesn't contain the second line of error output from #2:
Node run failed with exit code 1.Re-run for the same commit, now with
ACTIONS_STEP_DEBUG:https://github.com/peter-kehl/no_std_rna_slice_patterns/runs/8119525450?check_suite_focus=true
Re-run with both
ACTIONS_STEP_DEBUGandACTIONS_RUNNER_DEBUG:https://github.com/peter-kehl/no_std_rna_slice_patterns/runs/8119747255?check_suite_focus=true -> the same error as the above.
I've tried several times to attach a debug output here, but GitHub refused to upload both the whole ZIP, and even parts of it (TXT files). If you need any files, suggest how to get them to you.
This has happened at least a few times (or all the time) since I added the above
test.ymlon Tue Aug 30, 2022.Thank you in advance.
The text was updated successfully, but these errors were encountered: