Comments (12)
Yes.. finally got that......apparently I was not using the latest GitHub runner. Thank you @fjogeleit.
from http-request-action.
done
from http-request-action.
Am facing the same issue, so what would be the resolution for this? is it just changing action from uses: fjogeleit/http-request-action@v1
to uses: fjogeleit/[email protected]
? or is there something more to it?
from http-request-action.
fjogeleit/http-request-action@v1
points to the same commit as fjogeleit/[email protected]
, so it should not make any difference, both tags using node v20 (https://github.com/fjogeleit/http-request-action/blob/v1/action.yml#L78)
Maybe you have some caching which was not updated? You could try to use a pinned version like fjogeleit/[email protected]
but v1
should also work.
from http-request-action.
I tried using fjogeleit/[email protected]
still getting the following error:
Error: System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter ''using: node20' is not supported, use 'docker', 'node12' or 'node16' instead.') at GitHub.Runner.Worker.ActionManifestManager.ConvertRuns(IExecutionContext executionContext, TemplateContext templateContext, TemplateToken inputsToken, String fileRelativePath, MappingToken outputs) at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile) Error: Fail to load fjogeleit/http-request-action/v1.15.2/action.yml
I even cleared the workflow cache for that repo. Could it be a server issue?
from http-request-action.
Thats a totally different issue, looks like your runner does not support node20. Maybe you use outdated machines?
from http-request-action.
I am using ubuntu 20.04 EC2 instance on AWS, the instance doesn't seems to be the issue here.
from http-request-action.
As your issue describes:
Your runner does not support Node20, only lower versions like Node16 but this versions are deprecated for GitHub Runners.
You can either use an older version of this action, like v1.15.1, or you need to update your Runner instances to support Node v20.
from http-request-action.
This is my workflow file
name: Delete User
on:
workflow_dispatch:
inputs:
phoneNumber:
description: 'User phone number with country code'
required: true
default: '+1'
environment:
description: 'The environment. Eg: sandbox, uat'
required: true
default: 'sandbox'
jobs:
delete_user:
runs-on: ${{ github.event.inputs.environment }}
steps:
- name: Delete User
id: deleteUser
uses: fjogeleit/[email protected]
with:
url: https://internal.${{github.event.inputs.environment}}.gritfinancial.org/api/gritAdmin/users/${{github.event.inputs.phoneNumber}}
method: DELETE
timeout: 10000
- name: Response
run: echo ${{ steps.deleteUser.outputs.response }}
I am not sure from where it is picking up node 20.
from http-request-action.
runs-on: ${{ github.event.inputs.environment }}
As I said, from ayour runner instance, which seems the value of the environment
from http-request-action.
yeah, am using variable for the labels, one thing to mention is am using the spot instances for self-hosted runners and i noticed that the workflow worked on previous instance but after the instance was created the workflow stopped working.
from http-request-action.
Then you should update your self-hosted runners
to support newer Node versions.
from http-request-action.
Related Issues (20)
- v1 is not pointing to the latest v1.x.x version HOT 3
- File Uploads with `\` in the path are broken HOT 20
- Feature Request: store response into a file HOT 3
- How to install the CLI tool? HOT 1
- Getting error: "Unable to convert Data and Files into FormData: source.on is not a function" HOT 1
- Retries? HOT 3
- Headers and Content-Type errors HOT 3
- Method delete is causing AxiosError HOT 11
- Enable mutual TLS https authentication HOT 3
- Array of files to upload in single files property fails HOT 6
- Feature Request: Mask responses HOT 7
- Outputting a response via `responseFile` results in an exception when the response is empty. HOT 3
- Conditional use of JSON.stringify on response.data causing issues parsing the response HOT 4
- Pass data through json file HOT 2
- Upgrade to Node 20 HOT 1
- Access to Response Body for Ignored Status Codes HOT 2
- 'No response received' is logged when server returns just a status code HOT 1
- The retry functionality is wrong HOT 5
- Any way to retrieve the response status code?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from http-request-action.