Error: Unable to resolve action `fscarmen/warp-on-actions@v2`, unable to find version `v2`

[jiriks74]

Describe the bug
I've just setup my upptime repo again (the workflows weren't running) so I backed it up and created it again. RN the Setup Upptime workflow fails with

Error: Unable to resolve action `fscarmen/warp-on-actions@v2`, unable to find version `v2`

To Reproduce
Steps to reproduce the behavior:

1. Create a new repo from the template
2. Check that GH pages are setup
3. Create the GH token and put it into the GH_PAT secret
4. Setup your .upptime.yml
5. Go to Actions
6. Open the Setup Upptime workflow
7. See the error in logs

Expected behavior
Setup Upptime workflow successfully running

[AnandChowdhary]

We got this from actions/runner-images#668.

@titanism, perhaps it should be v1 instead of v2?

[jiriks74]

We got this from actions/runner-images#668.

@titanism, perhaps it should be v1 instead of v2?

Not really. I've modified the files where it's present and I get this:

Error: Unable to resolve action `fscarmen/warp-on-actions@v1`, unable to find version `v1`

[titanism]

Prob should just directly put this in, so we're not dependent on 3rd party https://github.com/fscarmen/warp-on-actions/blob/7c3bf29e14b71882e4ff62138da4a663fdd74c4a/action.yml#L15-L26

[jiriks74]

@titanism
I think I fixed it. I looked at the repo and the version that is available is v1.0.

From the repo:

Usage:

client warp+doh mode

 - uses: fscarmen/warp-on-actions@v1.0
   with:
     mode: client  # Optional, default

wireguard

 - uses: fscarmen/warp-on-actions@v1.0
   with:
     mode: wireguard

In Releases there's only the v1.0. I'll make a PR if you want.

RN. I've tried this and it works for me as of now.

PS: Since it works now I can go and figure out why the jobs are running avery +- 15 minutes instead of 5 (and sometimes 30m or even hours). Hopefully I've fixed it by modifying the files but we'll see. I've just found this project few days ago so I'm still figuring stuff out.

PPS: Looks like everything now runs as it should. Even on time - yesterday I didn't have any uptime checks for 12 hours - probably the bug got pulled in an update and the installation broke. I've disabled the update workflows until this one's figured out and then I'll turn them on again - the file says that manual changes to it will get overwritten in an update so it should be fine.

[AnandChowdhary]

Thank you for the fix, I'll make sure this goes live ASAP!

Since it works now I can go and figure out why the jobs are running avery +- 15 minutes instead of 5 (and sometimes 30m or even hours)

This is documented here: https://upptime.js.org/blog/2021/01/22/github-actions-schedule-not-working

[AnandChowdhary]

I've just shipped this, can you please test this by manually running "Update Template CI" and then running "Setup CI" after the template has been updated? Thanks!

[jiriks74]

It's still failing with the same issue @AnandChowdhary

[jiriks74]

I can see that the v2 tag is still present in the files instead of v1.0:

upptime/.github/workflows/setup.yml

Lines 42 to 43 in 8daad4a

	- name: Setup WARP
	uses: fscarmen/warp-on-actions@v2

[jiriks74]

I recreated the repo since I broke something and I got the upptime/upptime README instead of mine. I modified the setup.yml to use v1.0 and after running the warp-on-actions completely disappeared from all files. Is this what was supposed to happen?

[jiriks74]

(I also noticed that response time is ran at 11pm instead of every 6 hours)

upptime/.github/workflows/response-time.yml

Lines 20 to 21 in 8daad4a

	schedule:
	- cron: "0 23 * * *"

(just an FYI, I'll create a new issue if you think it's more appropriate)