raspberry pi - removing power causes fletch to hang on linux pc

[seb mitchell]

Running the knight-rider.dart on my pi is cool, 

reboot of the pi is fine with the program stopping and returning to the linux prompt.

For me there is an issue when I remove the power from the raspberry pi, I could not ^C to break out of the current fetch process 

and any new fletch command hangs without any activity on the pi.

Killing all the fletch processes resolves the issue. 

Do you want me to report?

uname -a on my linux box.

Linux  3.16.0-38-generic #52~14.04.1-Ubuntu SMP Fri May 8 09:43:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

I did get back to the command prompt, once, with this error info, still had to kill the process.

fletch run ./samples/raspberry_pi/basic/knight-rider.dart in session remote

^Z^C^C^C^Z^C^CThe Fletch program is broken and has crashed.

The Fletch team would greatly appreciate if you would take a moment to

report this problem at https://github.com/dart-lang/fletch/issues/new

Please include the following information:

* the name and version of your operating system

* the Fletch SDK version (0.1.0-dev.5.0)

* the entire message you see here (including the full stack trace below)

Uncaught Error: InputError(DiagnosticKind.socketAgentConnectError, {#{message}: No route to host, #{address}: 192.168.178.40:12121})

Stack Trace:

#0      throwFatalError (package:fletchc/src/diagnostic.dart:233:3)

#1      connect.<connect_async_body>.<anonymous closure> (package:fletchc/src/driver/developer.dart:100:9)

#2      _rootRunUnary (dart:async/zone.dart:911)

#3      _CustomZone.runUnary (dart:async/zone.dart:811)

#4      _Future._propagateToListeners.handleError (dart:async/future_impl.dart:525)

#5      _Future._propagateToListeners (dart:async/future_impl.dart:580)

#6      _Future._completeError (dart:async/future_impl.dart:376)

#7      _Future._asyncCompleteError.<anonymous closure> (dart:async/future_impl.dart:431)

#8      _rootRun (dart:async/zone.dart:904)

#9      _CustomZone.run (dart:async/zone.dart:803)

#10     _CustomZone.bindCallback.<anonymous closure> (dart:async/zone.dart:736)

#11     _microtaskLoop (dart:async/schedule_microtask.dart:43)

#12     _microtaskLoopEntry (dart:async/schedule_microtask.dart:52)

#13     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:96)

#14     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:149)

#0      _rootHandleUncaughtError.<anonymous closure> (dart:async/zone.dart:895)

#1      _microtaskLoop (dart:async/schedule_microtask.dart:43)

#2      _microtaskLoopEntry (dart:async/schedule_microtask.dart:52)

#3      _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:96)

#4      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:149)

[Michael Thomsen]

Yes, please log an issue in GitHub with the above info:

https://github.com/dart-lang/fletch/issues

Thanks for trying it out!

--
You received this message because you are subscribed to the Google Groups "Fletch Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fletch-discus...@googlegroups.com.
To post to this group, send email to fletch-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fletch-discuss/54c3f9c0-d021-4027-b2bf-5255504862f4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Peter von der Ahé]

Actually, this is a known issue, see https://github.com/dart-lang/fletch/issues/188

[seb mitchell]

Cool, issue created 

"removing power on raspberry pi causes fletch to hang on linux pc #214"

https://github.com/dart-lang/fletch/issues/214

[seb mitchell]

Using "fletch quit" is a lot nicer than killing the process,

works great to stop a working or faulty fletch session.

On Tuesday, 6 October 2015 19:49:16 UTC+11, seb mitchell wrote:

Cool, issue created 

"removing power on raspberry pi causes fletch to hang on linux pc #214"

https://github.com/dart-lang/fletch/issues/214

Issue #214 is a duplicate of #188 and has been closed, in #118 fault was caused by unplugging network cable.

https://github.com/dart-lang/fletch/issues/188

 

[Peter Ahé]

On Tue, Oct 6, 2015 at 11:53 AM seb mitchell <si...@jseb.com> wrote:

Issue #214 is a duplicate of #188 and has been closed, in #118 fault was caused by unplugging network cable.

https://github.com/dart-lang/fletch/issues/188

Yes. The root cause is the same. If we lose connection to the remote VM, we don't handle it well.