We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
Seems dust is not working well with null safety and the newest dart.
dust
dart run bin/dust.dart example/crash_on_bad.dart Unhandled exception: Observatory did not start on 7575 output: #0 VmController._startProcess (package:dust/src/vm_controller.dart:268:7) <asynchronous suspension> #1 VmController.prestart (package:dust/src/vm_controller.dart:69:5) <asynchronous suspension> #2 Future.wait.<anonymous closure> (dart:async/future.dart) <asynchronous suspension> #3 Cli.run (package:dust/src/cli.dart:199:7) <asynchronous suspension> #4 main (file:///tmp/dust/bin/dust.dart:8:3) <asynchronous suspension>
dart --version Dart SDK version: 2.13.4 (stable) (Unknown timestamp) on "linux_x64"
The text was updated successfully, but these errors were encountered:
Was this ever resolved? I am having the same issue running on M1 Mac.
Sorry, something went wrong.
The issue is caused by an outdated path in lib/src/vm_controller.dart to '.pub-cache/global_packages/dust/bin/controller.dart.snapshot.dart2'.
lib/src/vm_controller.dart
The current controller snapshot in pub_cache is called controller.dart-2.16.2.snapshot therefore to resolve this run
controller.dart-2.16.2.snapshot
cp ~/.pub-cache/global_packages/dust/bin/controller.dart-2.16.2.snapshot ~/.pub-cache/global_packages/dust/bin/controller.dart.snapshot.dart2
to make the hardcoded path point to a valid controller snapshot.
Awesome, Thank you for the hint. It works!
No branches or pull requests
Hi,
Seems
dust
is not working well with null safety and the newest dart.dart --version Dart SDK version: 2.13.4 (stable) (Unknown timestamp) on "linux_x64"
The text was updated successfully, but these errors were encountered: