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

[jiriks74]

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

[titanism]

Of course @AnandChowdhary , thank you . This is what OSS is all about 🙏

[titanism]

oh goodness @AnandChowdhary this is broken 🤦

https://community.cloudflare.com/t/cloudflare-warp-not-routing-smtp-to-internal-addresses/335898

it blocks ports like 25 outbound... can you revert? we need to find another IPv6 alternative

[titanism]

@AnandChowdhary please revert when you can 😢

[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/[email protected]
   with:
     mode: client  # Optional, default

wireguard

 - uses: fscarmen/[email protected]
   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)

[AnandChowdhary]

As you can see from the commit c1a25af, the expected output is that fscarmen/warp-on-actions will be completed removed and instead we've hardcoded the step "Install WARP to support IPv6".

[AnandChowdhary]

I'll reopen this issue until we have verification that it works! ✅

[AnandChowdhary]

@jiriks74 This new "Install WARP to support IPv6" step is only added for workflows that have an ipv6: true site, since your Upptime repository (jiriks74/upptime@f2ae9ae) does not have that, this step is unnecessary. Same as yours, @titanism, if you add a site with IPv6 now, I think it should work :)

[Iliya5digital]

Where paste token into GH_PAT secret? Which file? Show me the path.

[titanism]

@AnandChowdhary I don't think this is going to work because inputs.mode is not defined? See my comment at upptime/uptime-monitor@47e177b#r137581722.

[AnandChowdhary]

You're right :( Would you like to make a PR with what's correct? This is where we have to change it - https://github.com/upptime/uptime-monitor/blob/3e32e513ff5d36837223efb82957b67ee5768f42/src/helpers/workflows.ts#L43

[Iliya5digital]

friends!
check with me what's wrong https://github.com/Iliya5digital/sites

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

[titanism]

@AnandChowdhary the easiest thing you can do is remove all the conditional IPv6 stuff and just add this globally for all installations. It would actually be a ➕ feature that users would love, as they wouldn't rely on whatever trash DNS GitHub CI is using. You'd simply add this to the CI yaml:

sudo apt-get -y update
curl -fsSL https://pkg.cloudflareclient.com/pubkey.gpg | sudo gpg --yes --dearmor --output /usr/share/keyrings/cloudflare-warp-archive-keyring.gpg
echo "deb [arch=amd64 signed-by=/usr/share/keyrings/cloudflare-warp-archive-keyring.gpg] https://pkg.cloudflareclient.com/ $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/cloudflare-client.list
sudo apt-get update
sudo apt-get install -y cloudflare-warp
sudo warp-cli --accept-tos register
sudo warp-cli --accept-tos set-mode warp+doh
sudo warp-cli --accept-tos connect

[titanism]

But if you want to just fix that WARP_ACTIONS snippet @AnandChowdhary all you need is the code shared in my previous comment

[AnandChowdhary]

Added globally!

[AnandChowdhary]

Thanks for all your help @titanism, looks like IPv6 is working after adding this - b560b6f