"tessel run" will just silently run the previously pushed code if any problem encountered in "run" about t1-cli HOT 7 CLOSED

tessel run can't run anything if it failed. Code that is put on tessel with a tessel push is in flash, which means it runs on boot.

from t1-cli.

Say 5 minutes ago I run tessel blink. Now I say tessel run test.js. Instead, blink is run again, because something, somewhere failed. If this isn't a bug to you, then that's sort of a problem.

from t1-cli.

tessel run normally stops the script when you ctrl-c the host process, and should also stop anything that's already running on the Tessel without a host process attached, and if it's not, that's a bug. But let's diagnose it over on the forum -- describe what you ran and what the output is.

from t1-cli.

I don't understand why there are two places to file issues.
On Jul 26, 2014 1:12 AM, "Kevin Mehall" [email protected] wrote:

tessel run stops the previously-running script, and if it's not, that's a
bug, but let's diagnose it over on the forum https://forums.tessel.io/
-- describe what you ran and what the output is.

—
Reply to this email directly or view it on GitHub
https://github.com/tessel/cli/issues/123#issuecomment-50223703.

from t1-cli.

I don't think its immediately clear to us if this is a user error or a Tessel error. I'm not able to recreate this:

Say 5 minutes ago I run tessel blink. Now I say tessel run test.js. Instead, blink is run again.

In this case, we would like it to go on the forums so that we can get some clarifying details. Also more users are available to help you on the forums than just us, so the chances of it being resolved quicker are higher.

from t1-cli.

I'm not sure you why don't ask for clarifying details here like other open-source projects hosted on github instead. The last thing I need is yet another account on some forum somewhere because some projects think they are special.

Nevermind, I can wait until a newer version like a normal person.

from t1-cli.

We like to have issues on GitHub be actionable things that need to be fixed, containing all necessary information to reproduce the issue. The forum is a better place to ask questions and get answers, and once we've figured out what the issue is, we'll open an issue. We have lots of interacting code in separate repositories (firmware, runtime, CLI, hardware-resolve, colony-lua, and colony-compiler are just a few of them), and this helps us keep track of what needs to be fixed. This is not an uncommon policy for larger projects.

The last thing I need is yet another account on some forum somewhere because some projects think they are special.

You can use your GitHub account on the forum -- no new account required.

Nevermind, I can wait until a newer version like a normal person.

It's probably unlikely that a newer version will fix your issue since we can't seem to be able to recreate it.

from t1-cli.