Skip to content

Frequent instances of "Could not find a file named "pubspec.yaml"" when running dart pub deps --json #4559

Open
@bkonyi

Description

@bkonyi

The top crashers on the Flutter beta channel right now are mostly all related to failures to find the pubspec.yaml within packages in the cache:

Thread 0 main threadStateError: Bad state: /flutter/bin/cache/dart-sdk/bin/dart pub --suppress-analytics deps --json failed
Could not find a file named "pubspec.yaml" in "/root/.pub-cache/hosted/pub.dev/characters-1.4.0".
at _DefaultPub.deps.fail	(pub.dart:370)
at _DefaultPub.deps	(pub.dart:378)
at <asynchronous gap>	(async)
at computeExclusiveDevDependencies	(compute_dev_dependencies.dart:21)
at <asynchronous gap>	(async)
at findPlugins	(flutter_plugins.dart:105)
at <asynchronous gap>	(async)
at refreshPluginsList	(flutter_plugins.dart:1109)
at <asynchronous gap>	(async)
at FlutterProject.ensureReadyForPlatformSpecificTooling	(project.dart:369)
at <asynchronous gap>	(async)
at FlutterCommand.regeneratePlatformSpecificToolingIfApplicable	(flutter_command.dart:1931)
at <asynchronous gap>	(async)
at FlutterCommand.verifyThenRunCommand	(flutter_command.dart:1887)
at <asynchronous gap>	(async)
at FlutterCommand.run.<anonymous closure>	(flutter_command.dart:1553)
at <asynchronous gap>	(async)
at AppContext.run.<anonymous closure>	(context.dart:154)
at <asynchronous gap>	(async)
at CommandRunner.runCommand	(command_runner.dart:212)
at <asynchronous gap>	(async)
at FlutterCommandRunner.runCommand.<anonymous closure>	(flutter_command_runner.dart:494)
at <asynchronous gap>	(async)
at AppContext.run.<anonymous closure>	(context.dart:154)
at <asynchronous gap>	(async)
at FlutterCommandRunner.runCommand	(flutter_command_runner.dart:431)
at <asynchronous gap>	(async)
at run.<anonymous closure>.<anonymous closure>	(runner.dart:98)
at <asynchronous gap>	(async)
at AppContext.run.<anonymous closure>	(context.dart:154)
at <asynchronous gap>	(async)
at main	(executable.dart:102)
at <asynchronous gap>	(async)

This issue is also present on the stable branch, but seems to be much less frequent.

It's unclear why this is happening, but it's worrying that we're seeing this from 100-200 unique users on the beta channel which only has a few hundred users on average.

FYI @sigurdm @jonasfj

Metadata

Metadata

Assignees

No one assigned

    Labels

    P0A serious issue requiring immediate resolutiontype-bugIncorrect behavior (everything from a crash to more subtle misbehavior)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions