Something going weird after v1.8.0 update: <https:...

# github-workflows-kt

[LeoColman]

Something going weird after v1.8.0 update:
https://github.com/LeoColman/Petals/commit/bb5c966f474722bb4dcebc55c5c7732422428721

[Piotr Krzemiński]

Could you make sure it's not because of the Kotlin Script caching issue?

[Piotr Krzemiński]

https://kotlinlang.slack.com/archives/C02UUATR7RC/p1703338064042929

[Piotr Krzemiński]

https://kotlinlang.slack.com/archives/C02UUATR7RC/p1703338110128869

[Piotr Krzemiński]

Merged threads, please remove the two other top-level messages if still possible

[Piotr Krzemiński]

tested on my machine: checked out https://github.com/LeoColman/Petals/commit/bb5c966f474722bb4dcebc55c5c7732422428721 and ran

.github/workflows/generate-action-bindings.main.kts
.github/workflows/build.main.kts

I see this diff:

diff --git a/.github/workflows/build.yaml b/.github/workflows/build.yaml
index 9fda077..a363e98 100644
--- a/.github/workflows/build.yaml
+++ b/.github/workflows/build.yaml
@@ -15,9 +15,12 @@ jobs:
       name: 'Check out'
       uses: 'actions/checkout@v4'
     - id: 'step-1'
+      name: 'Generate action bindings'
+      run: '.github/workflows/generate-action-bindings.main.kts "build.yaml"'
+    - id: 'step-2'
       name: 'Execute script'
       run: 'rm ''.github/workflows/build.yaml'' && ''.github/workflows/build.main.kts'''
-    - id: 'step-2'
+    - id: 'step-3'
       name: 'Consistency check'
       run: 'git diff --exit-code ''.github/workflows/build.yaml'''
   build:

which means that the script wants to add the missing step back, which means that the issue doesn't reproduce on my machine. I'm pretty sure it's because of the caching issue

[Piotr Krzemiński]

https://typesafegithub.github.io/github-workflows-kt/faq/#kotlin-scripts-work-as-if-changes-in-the-imported-files-werent-applied-why

[Piotr Krzemiński]

My wish to JetBrains for 2024 is to finally fix this caching issue 😓 causes so much confusion

[LeoColman]

Even after dropping caches on my local machine I'm failing to get a new version of the yamls

[LeoColman]

Even after reverting to the previous version I'm failing to generate new yamls. Damn

[LeoColman]

Is this due to action bindings?

[Piotr Krzemiński]

Could you share how you clean the cache and what's your OS? The problematic part of YAML is still this one missing step in the consistency check job, right?

[Piotr Krzemiński]

The issue doesn't occur on GitHub right?

[Piotr Krzemiński]

fixes the main branch: https://github.com/LeoColman/Petals/pull/474

[LeoColman]

It doesn't seem to occur on GitHub, no.

To remove caches, I'm running

rm -rf ~/.cache/main.kts.compiled.cache/

Opening a new terminal and running the scripts inside .workflows again. I also tried some invalidate caches and restart, deleting build, deleting .workflows/generated and deleting .gradle

None of these made any difference to how scripts were being executed.

[LeoColman]

Running ./generate-action-bindings.main.kts does its thing:

... from <https://raw.githubusercontent.com/actions/checkout/v4/action.yml>
  ... types from <https://raw.githubusercontent.com/actions/checkout/v4//action-types.yml>
  ... types from <https://raw.githubusercontent.com/actions/checkout/v4//action-types.yaml>
.................

[LeoColman]

But then running for example build.gradle.kts does nothing to the YAML. If I delete build.yaml it generated the old (stale/bad/incomplete) file. Is there a debug mode I can enable to get more logs of what's going on?

[LeoColman]

OS is
uname -a:

Linux leonardo-pc 6.5.1-060501-generic #202309020842 SMP PREEMPT_DYNAMIC Sat Sep  2 08:48:34 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -a:

Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.3 LTS
Release:	22.04
Codename:	jammy

[Piotr Krzemiński]

Let's dig deeper after Christmas. Logging off for 3 days at least :)

[LeoColman]

https://github.com/typesafegithub/github-workflows-kt/issues/1206