Daco Harkes
Daco Harkes
Ignoring the folders with `analysis_options.yaml` does work to fix `dart analyze`, but not `dart pub global run firehose --validate`: ```yaml analyzer: exclude: # TODO(https://github.com/dart-lang/ecosystem/issues/150): Remove this. - test/data/ ```
A workaround would be if we could somehow configure a set of paths to run `pub get` in.
The root cause is likely in pub, not in this package: * https://github.com/dart-lang/pub/issues/3982
> * avoid having an actual project in test-data. One solution could be to create the project in a sandbox from inside the test itself. That's unpractical when test projects...
> Thanks for reaching out. I had originally hoped to use `native_toolchain_go` for consistency but couldn't. I'd be happy to switch over to that package name for consistency. I can't...
> Ah, that's annoying. I've created an intermediary publisher and sent you an invite. Please invite my google email address: [email protected]
The issue this test covers hasn't been addressed yet. It's crashing on all configurations it's not timing out on. https://dart-current-results.web.app/#/filter=ffi/callback_unwind_error_test&showAll Underlying issue causing crash: * https://github.com/dart-lang/sdk/issues/39487
From flaky to timeout again: https://dart-ci.appspot.com/log/vm-reload-rollback-linux-release-x64/vm-reload-rollback-linux-release-x64/477/vm/dart/isolates/shared_test
> Does this SDK need to be downloaded for the issue to be reproduced? It's reliably reproducing on the GitHub CI downloading the SDK, see the links in the linked...
> Hm, maybe we should be using [FileSystemEntity.typeSync](https://api.dart.dev/stable/3.4.4/dart-io/FileSystemEntity/typeSync.html) instead of `File.existsSync`, which appears like it might return `false` if we're checking the path to a `Link` object. Ah that could...