gruntjs - How to workaround "the input device is not a TTY" when using grunt-shell to invoke a script that calls docker run? -


when issuing grunt shell:test, i'm getting warning "the input device not tty" & don't want have use -f:

$ grunt shell:test running "shell:test" (shell) task input device not tty warning: command failed: /bin/sh -c ./run.sh npm test input device not tty  use --force continue.  aborted due warnings.

here's gruntfile.js command:

shell: {   test: {     command: './run.sh npm test'   }

here's run.sh:

#!/bin/sh # should use latest available image validate, not latest if [ -f .env ];   run_env_file='--env-file .env' fi docker run $run_env_file -it --rm --user node -v "$pwd":/app -w /app yaktor/node:0.39.0 $@

here's relevant package.json scripts command test:

"scripts": {   "test": "mocha --color=true -r spec test/*.test.js && npm run lint" }

how can grunt make docker happy tty? executing ./run.sh npm test outside of grunt works fine:

$ ./run.sh npm test  > yaktor@0.59.2-pre.0 test /app > mocha --color=true -r spec test/*.test.js && npm run lint   [snip]    105 passing (3s)   > yaktor@0.59.2-pre.0 lint /app > standard --verbose

remove "-t" docker run command:

docker run $run_env_file -i --rm --user node -v "$pwd":/app -w /app yaktor/node:0.39.0 $@

the "-t" tells docker configure tty, won't work if don't have tty , try attach container (default when don't "-d").


Comments

Post a Comment

Popular posts from this blog

asynchronous - C# WinSCP .NET assembly: How to upload multiple files asynchronously -

i using winscp .net assembly uploading files. want upload multiple files asynchronous way. have created method works single upload. public class uploadingdata { private sessionoptions _sessionoptions; private session _session; //connection etc private void onconnected() { foreach (var fileinfo in localfileslist) { var task = task.factory.startnew(() => uploadfilesasync(fileinfo)); } } private async task uploadfilesasync(string file) { string remotefilepath = _session.translatelocalpathtoremote(file, @"/", "/test_data_upload"); var uploading = _session.putfiles(file, remotefilepath, false); //when done await task.run(() => thread.sleep(1000)); } } please suggest me correct way. thanks you can use backgroundworker class this: string[] images = new string[50]; foreach (var path in images) { backgroundworker
Read more

aws api gateway - SerializationException in posting new Records via Dynamodb Proxy Service in API -

i getting "__type": "com.amazon.coral.service#serializationexception" as reply in postman & in test console in api gateway trying post record directly dynamodb using api proxy services.. referring aws article - https://aws.amazon.com/blogs/compute/using-amazon-api-gateway-as-a-proxy-for-dynamodb/ here's mapping { "tablename": "tablenamegoeshere", "item": { "id" : "$context.requestid" "eventname" : "$input.path('$.eventname')", "timestamp" : $input.path('$.timestamp'), "answers": "$util.parsejson($input.path('$.answers'))" } } update: did asked ... , worked if try add array of json objects gives me above same error - here's trying now. please - couldnt find on google well #set($inputroot = $input.path('$')) { "tablename": "answer", "item": {
Read more

asp.net - Problems sending emails from forum -

i have been redesigning site has message board, has been written guy looked after site. it has few problems , written in .asp , uses .mdb files database. you can see whole thing here . feel free post if helps, test thing have set using original files , new database. the basic problem when posts message, supposed email sent them, have posted it. when replies, originator supposed message, replier has been posted. i’d have thought @ point in process there should script/file in postmessage.asp? the postmessage.asp page below. <% option explicit %> <!-- #include virtual="common/adovbs.inc" --> <html> <head> <meta http-equiv="content-type" content="text/html; charset=windows-1252"> <meta name="generator" content="microsoft frontpage 4.0"> <meta name="progid" content="frontpage.editor.document"> <title>new page 2</title> <base target="_self"
Read more