-
Notifications
You must be signed in to change notification settings - Fork 190
Runtime node no longer supported #192
Comments
It looks like the latest release is not up-to-date with the latest changes in the code. The latest release was in the fall of 2017, and the code appears to have been updated to fix this error 2 months ago. My guess is that the best solution is to compile it from the source code, but even that is a chore because the base version of Go this runs on isn't very readily available. |
@cjwilburn I'm not convinced this was properly fixed. I've finally managed to make a new build from master. $ ./goad-2 -V It's still errorring out:
This older version runs fine: $ ./goad -V This seems to be an introduced issue. |
Issue is still not fixed, we tried to use for one of our projects and now it says
@matiaskorhonen can i raise a pull request for it? |
I just compiled from source and it worked @jay-dee7 |
Fetching the project throws the following error $ go get github.com/goadapp/goad github.com/goadapp/goad/infrastructure/docker github.com/goadapp/goad/infrastructure/aws Compiling the app does not throw any error, however there is an error while trying to run the app panic: InvalidParameterValueException: The runtime parameter of nodejs4.3 is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs10.x) while creating or updating functions. goroutine 1 [running]: Any idea how to fix the nodejs runtime issue? Tks |
Here is the version of the app $ goad -V |
@vi8rel what worked for me was: go get github.com/aws/aws-sdk-go Then depending on your operating system choose one (linux32,linux64,osx64,win64) like this: make osx64 You have to do that where the repo was dowloaded usually $HOME/go/src/github.com/goadapp/goad Then you will find a binary 'goad' in 'build' folder |
@pathcl thank you for pointing me in the right direction. Now it is not clear what is the syntax to insert an http POST body such as {"timestamp": "20190510", "geotag": "000000110000011100000011", "Event": "0001"} ./goad -n 5000 -c 1000 -H "Content-type: application/json" -m "POST" --body="timestamp: 20190510, geotag: 000000110000011100000011, Event: 0200" "http://test.site.com/path" returns 502 bad gateway response (output below) TotReqs TotBytes AvgTime AvgReq/s (post)unzip A simple curl command works just fine and returns a 200 OK response curl -H "content-type: application/json" -X POST -d '{"timestamp": "20190510", "geotag": "000000110000011100000011", "Event": "0200"}' http://test.site.com/path |
I just tested against httpbin.org/post and its giving me 200:
|
@pathcl I followed your steps to build from source, but I'm still getting the "The runtime parameter of nodejs8.10 is no longer supported" error.
Has this project been abandoned? |
It looks indeed abandoned but I can give you a hand tomorrow
…On Thu, 23 Apr 2020 at 19:04 Aaron Murray ***@***.***> wrote:
@pathcl <https://github.com/pathcl> I followed your steps to build from
source, but I'm still getting the "The runtime parameter of nodejs8.10 is
no longer supported" error.
goad -V
2.0.0-rc1x-612187f4
Has this project been abandoned?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#192 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA4YEQB7QMBOJXRBD5EY273ROBYKNANCNFSM4G6AAUFA>
.
|
Hi,
I've just installed the latest release (2.0.4) and I still have the error:
panic: InvalidParameterValueException: The runtime parameter of nodejs4.3 is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs8.10) while creating or updating functions.
The text was updated successfully, but these errors were encountered: