Error: execution expired on any ey-core command

Open
#126 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
ruby
Domain
cli

Research direction

Start by reproducing both an ey-core SSH command and ey-core login, noting how long each takes before Error: execution expired. Trace the command's timeout and error path, then verify that login and environment SSH no longer expire unexpectedly.

Written by the indexing model from the issue text.

Description

I've been successfully used the ey-core command until today, then suddenly I couldn't ssh to an environment, I've also tried to run ey-core login but no success there also
It takes a while from the moment I run the command until I get Error: execution expired error message

Dominant language
Ruby
Stars
4
Forks
19
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from engineyard/core-client-rb

All issues in engineyard/core-client-rb

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.