-
-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Action fails with Crypto is not defined #2326
Comments
Thanks for reporting this issue, don't forget to star this project if you haven't already to help us reach a wider audience. |
extremely strange this bug. it does not happen on my colleague's setup. |
Yes. |
I'm am running locally - debian12 VM with docker.
…On Tue, Oct 22, 2024 at 12:54 PM Tonye Jack ***@***.***> wrote:
@winsvega <https://github.com/winsvega> Where are you running the
workflow locally using act <https://github.com/nektos/act>?
—
Reply to this email directly, view it on GitHub
<#2326 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF3UGCMQSWCGV2XDJLEWXQLZ4Z7K7AVCNFSM6AAAAABQK4CQ4SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRZG44DSOJTGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hmm, but what is so special about changed files action that triggers this bug. Since the error comes only if changed files action is activated |
The weird thing is this worked 3 weeks ago.
Now, it doesn't complete the changed-file-patterns group
Is there any debug logging we can enable to see where it is failing with-in
the action?
…On Tue, Oct 22, 2024 at 5:07 PM winsvega ***@***.***> wrote:
Hmm, but what is so special about changed files action that triggers this
bug. Since the error comes only if changed files action is activated
—
Reply to this email directly, view it on GitHub
<#2326 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF3UGCJA2LUN62BJOUDV3BDZ425B3AVCNFSM6AAAAABQK4CQ4SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZQGI4DSMZVGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Tried with prior version, |
Hi @ajgerace, You can set ACTION_STEP_DEBUG to |
Yes I can try that. I too tried v44 and it is working.
…On Sat, Oct 26, 2024 at 3:48 PM Tonye Jack ***@***.***> wrote:
Hi @ajgerace <https://github.com/ajgerace>, You can set ACTION_STEP_DEBUG
<https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/enabling-debug-logging#enabling-step-debug-logging>
to true to enable debug logging.
—
Reply to this email directly, view it on GitHub
<#2326 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF3UGCKOUJ5YDS7YUUU3GHDZ5PW2LAVCNFSM6AAAAABQK4CQ4SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZZG4YTOMZRHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Here is the step logs
::group::changed-files
2 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-2>Env:
{%0A "GITHUB_REF_NAME": "main",%0A "GITHUB_REF": "refs/heads/main",%0A
"GITHUB_WORKSPACE": "/workspace/gerace/test-repo"%0A}
3 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-3>Inputs:
{%0A "files": "",%0A "filesSeparator": "\n",%0A "filesFromSourceFile":
"",%0A "filesFromSourceFileSeparator": "\n",%0A "filesYaml": "",%0A
"filesYamlFromSourceFile": "",%0A "filesYamlFromSourceFileSeparator":
"\n",%0A "filesIgnore": ".gitea/workflows/actions.yml",%0A
"filesIgnoreSeparator": "\n",%0A "filesIgnoreFromSourceFile": "",%0A
"filesIgnoreFromSourceFileSeparator": "\n",%0A "filesIgnoreYaml": "",%0A
"filesIgnoreYamlFromSourceFile": "",%0A
"filesIgnoreYamlFromSourceFileSeparator": "\n",%0A
"failOnInitialDiffError": false,%0A "failOnSubmoduleDiffError": false,%0A
"separator": " ",%0A "sha": "",%0A "baseSha": "",%0A "since": "",%0A
"until": "",%0A "path": ".",%0A "quotepath": ***,%0A "diffRelative":
***,%0A "sinceLastRemoteCommit": false,%0A "recoverDeletedFiles": false,%0A
"recoverDeletedFilesToDestination": "",%0A "recoverFiles": "",%0A
"recoverFilesSeparator": "\n",%0A "recoverFilesIgnore": "",%0A
"recoverFilesIgnoreSeparator": "\n",%0A "includeAllOldNewRenamedFiles":
false,%0A "oldNewSeparator": ",",%0A "oldNewFilesSeparator": " ",%0A
"skipInitialFetch": false,%0A "fetchAdditionalSubmoduleHistory": false,%0A
"dirNamesDeletedFilesIncludeOnlyDeletedDirs": false,%0A
"excludeSubmodules": false,%0A "usePosixPathSeparator": false,%0A
"tagsPattern": "*",%0A "tagsIgnorePattern": "",%0A "dirNames": false,%0A
"dirNamesExcludeCurrentDir": false,%0A "dirNamesIncludeFiles": "",%0A
"dirNamesIncludeFilesSeparator": "\n",%0A "json": false,%0A "escapeJson":
***,%0A "safeOutput": ***,%0A "writeOutputFiles": false,%0A "outputDir":
".github/outputs",%0A "outputRenamedFilesAsDeletedAndAdded": false,%0A
"token": "***",%0A "apiUrl": "https://gitea1.f5demo.org/api/v1",%0A
"negationPatternsFirst": false,%0A "useRestApi": false,%0A "fetchDepth":
25,%0A "fetchMissingHistoryMaxRetries": 20%0A}
4 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-4>Working
directory: /workspace/gerace/test-repo
5 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-5>Has
git directory: ***
6 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-6>files
ignore patterns: !.gitea/workflows/actions.yml
7 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-7>Input
file patterns: %0A!.gitea/workflows/actions.yml
8 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-8>File
patterns: !.gitea/workflows/actions.yml
9 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-9>Yaml
file patterns: {}
10 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-10>Using
local .git directory
11 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-11>Running
on a push event...
12 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-12>Getting
current SHA...
13 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-13>Current
SHA: 3840fa954dcd2d04dc81227ddc5bb6267c91a990
14 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-14>Getting
previous SHA...
15 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-15>Getting
previous SHA for last remote commit...
16 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-16>Previous
SHA: 0c261cbb13fc75b252a8e25fda8e2370fa1c8d4e
17 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-17>Target
branch: main
18 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-18>Current
branch: main
19 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-19>Retrieving
changes between 0c261cbb13fc75b252a8e25fda8e2370fa1c8d4e (main) →
3840fa954dcd2d04dc81227ddc5bb6267c91a990 (main)
20 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-20>All
diff files:
{"A":[],"C":[],"D":["f5demo.org-02dec24.key"],"M":[],"R":[],"T":[],"U":[],"X":[]}
21 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-21>All
Done!
22 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-22>
::endgroup::
23 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-23>
::group::changed-files-patterns
24 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-24>All
filtered diff files:
{"A":[],"C":[],"D":["f5demo.org-02dec24.key"],"M":[],"R":[],"T":[],"U":[],"X":[]}
25 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-25>Dir
names include file patterns: []
26 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-26>Added
files: {"paths":"","count":"0"}
27 <https://gitea1.f5demo.org/gerace/test-repo/actions/runs/43#jobstep-2-27>::error::crypto
is not defined
On Sat, Oct 26, 2024 at 3:50 PM Anthony Gerace ***@***.***>
wrote:
… Yes I can try that. I too tried v44 and it is working.
On Sat, Oct 26, 2024 at 3:48 PM Tonye Jack ***@***.***>
wrote:
> Hi @ajgerace <https://github.com/ajgerace>, You can set ACTION_STEP_DEBUG
> <https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/enabling-debug-logging#enabling-step-debug-logging>
> to true to enable debug logging.
>
> —
> Reply to this email directly, view it on GitHub
> <#2326 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AF3UGCKOUJ5YDS7YUUU3GHDZ5PW2LAVCNFSM6AAAAABQK4CQ4SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZZG4YTOMZRHA>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
What is the next step after the changed files action? |
This log doesn't include the error or message from the next step |
The error message happens at the end of Check changed files
Line 27 - ::error::crypto is not defined
…On Mon, Oct 28, 2024 at 9:27 AM Tonye Jack ***@***.***> wrote:
This log doesn't include the error or message from the next step
—
Reply to this email directly, view it on GitHub
<#2326 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF3UGCOCNFOAK67SZ64TUYDZ5Y3VDAVCNFSM6AAAAABQK4CQ4SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBRGU4TAMZWHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
[image: image.png]
On Mon, Oct 28, 2024 at 9:30 AM Anthony Gerace ***@***.***>
wrote:
… The error message happens at the end of Check changed files
Line 27 - ::error::crypto is not defined
On Mon, Oct 28, 2024 at 9:27 AM Tonye Jack ***@***.***>
wrote:
> This log doesn't include the error or message from the next step
>
> —
> Reply to this email directly, view it on GitHub
> <#2326 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AF3UGCOCNFOAK67SZ64TUYDZ5Y3VDAVCNFSM6AAAAABQK4CQ4SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBRGU4TAMZWHE>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
Is there an existing issue for this?
Does this issue exist in the latest version?
Describe the bug?
Creating a GITEA action using your action in attempt to track files that were added to a repo. When your action runs I'm receiving an error "::error::crypto is not defined".
To Reproduce
sample:
name: List changed files
| on:
| push:
| branches:
| - main
|
| jobs:
| changed_files:
| runs-on: ubuntu-latest
| name: Test added-files
| steps:
| - uses: actions/checkout@v4
| with:
| fetch-depth: 0
| - id: changed-files
| name: Check changed files
| uses: tj-actions/changed-files@v45
| with:
| files: |
| **.txt
::group::changed-files
Using local .git directory
Running on a push event...
Retrieving changes between 5b4334af522301674114cbb23f7199b9268e57f3 (main) → ba0fb119cc92a26f88281d2baad6104fe1788da1 (main)
All Done!
::endgroup::
::group::changed-files-patterns
::error::crypto is not defined
What OS are you seeing the problem on?
ubuntu-latest or ubuntu-22.04
Expected behavior?
Receive list of files that changed in output variable
Relevant log output
Has all relevant logs been included?
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: