question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Issue running standup-helper.sh

See original GitHub issue

Node Version: node --version v4.7.2 tiny-core-terminal version: npm info tiny-care-terminal | grep version: version: ‘1.0.8’ Shell: bash, zsh, fish, something else? zsh Terminal Program: tmux, iterm, terminator, cmd, something else? iterm Operating System: Mac, Windows, Linux, BSD, Really, something else? macOS Sierra 10.12.3

Hey, I’m having some issues with standup-helper.sh. In the doTheCodes method within care.js (here), the spawn call is throwing an exception

Error: spawn sh /Users/mbrawn/.nvm/versions/node/v4.7.2/lib/node_modules/tiny-care-terminal/standup-helper.sh ENOENT
    at exports._errnoException (util.js:907:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:189:32)
    at onErrorNT (internal/child_process.js:355:16)
    at nextTickCallbackWith2Args (node.js:458:9)
    at process._tickCallback (node.js:372:17)
    at Function.Module.runMain (module.js:443:11)
    at startup (node.js:139:18)
    at node.js:990:3
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: spawn sh /Users/mbrawn/.nvm/versions/node/v4.7.2/lib/node_modules/tiny-care-terminal/standup-helper.sh ENOENT
    at exports._errnoException (util.js:907:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:189:32)
    at onErrorNT (internal/child_process.js:355:16)
    at nextTickCallbackWith2Args (node.js:458:9)
    at process._tickCallback (node.js:372:17)

Using the function mentioned in this SO post, I was able to see the following before the exception is thrown

spawn called
{ '0': 'sh /Users/mbrawn/.nvm/versions/node/v4.7.2/lib/node_modules/tiny-care-terminal/standup-helper.sh',
  '1': [ '~/repos/' ],
  '2': { shell: true } }
spawn called
{ '0': 'sh /Users/mbrawn/.nvm/versions/node/v4.7.2/lib/node_modules/tiny-care-terminal/standup-helper.sh',
  '1': [ '-d 7', '~/repos/' ],
  '2': { shell: true } }

I am able to run the standup helper manually and get a result with sh sh-3.2$ ./standup_helper.sh ~/repos/

From what I can see, I’ve added the environment variables

echo $TTC_REPOS
~/repos

My .zshrc

# List of accounts to read the last tweet from, comma separated
# The first in the list is read by the party parrot.
export TTC_BOTS='tinycarebot,selfcare_bot,magicrealismbot'

# List of folders to look into for `git` commits, comma separated.
export TTC_REPOS='~/repos'

# Location/zip code to check the weather for. Both 90210 and "San Francisco, CA"
# _should_ be ok (the zip code doesn't always work -- use a location
# first, if you can). It's using weather.service.msn.com behind the curtains.
export TTC_WEATHER='Toronto'

# Set to false if you're an imperial savage. <3
export TTC_CELSIUS=true

# Unset this if you _don't_ want to use Twitter keys and want to
# use web scraping instead.
export TTC_APIKEYS=true

# Refresh the dashboard every 20 minutes.
export TTC_UPDATE_INTERVAL=20

# Twitter api keys
export TTC_CONSUMER_KEY='SECRET'
export TTC_CONSUMER_SECRET='SECRET'
export TTC_ACCESS_TOKEN='SECRET'
export TTC_ACCESS_TOKEN_SECRET='SECRET'

# Note: in tiny-terminal-care < 1.0.7, the recommended variables for the Twitter
# API keys were the ones before. As of 1.0.8, they are deprecated
# (because the names are too generic), but will still be supported
# until the next major version.
# export CONSUMER_KEY='...'
# export CONSUMER_SECRET='...'
# export ACCESS_TOKEN='...'
# export ACCESS_TOKEN_SECRET='...'

I’ve tried ~/repos and ~/repos/

Any ideas? Have I misconfigured something?

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:11 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
notwaldorfcommented, May 14, 2017

As of version 1.2.0 there’s a new way to use the terminal that doesn’t involve the bash script, that should fix your problems. To use that, set the TTC_GITBOT environment variable to gitlog. This will become the default way in the future, I’m just giving it a bit of time in the wild before switching to it

1reaction
notwaldorfcommented, Apr 22, 2017

@KernelDeimos I’m using oh-my-zsh, so this should work in zsh as well 😦

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error at launch of the program · Issue #71 · notwaldorf/tiny-care ...
What happens if you run the standup-helper.sh manually. You have the path to the file in your error message. Try run: sh standup-helper.sh...
Read more >
Untitled - Index of
to be, there is the spectre of a software running somewhere in ... MIPS Edition, Fifth Edition: The Hardware/Software Interface. ... sudo sh...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found