Skip to content
New issue

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

pub.dev has pub version 2.18.0 and package fails with >=2.18.1 <3.0.0 requirements #6087

Closed
iapicca opened this issue Sep 27, 2022 · 4 comments

Comments

@iapicca
Copy link

iapicca commented Sep 27, 2022

stdout: MSG : Resolving dependencies...
MSG : Logs written to /tmp/tool-envPATXHE/pub-cache-dirOLHKOB/log/pub_log.txt.

stderr: FINE: Pub 2.18.0
SLVR: fact: yak_utils is 1.0.0+13
SLVR: derived: yak_utils
SLVR: fact: yak_utils requires SDK version >=2.18.1 <3.0.0
SLVR: conflict: yak_utils requires SDK version >=2.18.1 <3.0.0
SLVR: Version solving took 0:00:00.030593 seconds.
    | Tried 1 solutions.
FINE: Resolving dependencies finished (0.054s).
ERR : The current Dart SDK version is 2.18.0.
    | 
    | Because yak_utils requires SDK version >=2.18.1 <3.0.0, version solving failed.
FINE: Exception type: SolveFailure
FINE: package:pub/src/solver/version_solver.dart 311:5               VersionSolv[...]
    | package:pub/src/solver/version_solver.dart 132:27              VersionSolv[...]
    | package:pub/src/solver/version_solver.dart 96:11               VersionSolv[...]
    | ===== asynchronous gap ===========================
    | dart:async                                                     Future.catchError
    | package:pub/src/utils.dart 109:52                              captureErro[...]
    | package:stack_trace                                            Chain.capture
    | package:pub/src/utils.dart 122:11                              captureErrors
[...]
FINE: Exception type: SolveFailure
FINE: package:pub/src/solver/version_solver.dart 311:5               VersionSolv[...]
    | package:pub/src/solver/version_solver.dart 132:27              VersionSolv[...]
    | package:pub/src/solver/version_solver.dart 96:11               VersionSolv[...]
    | ===== asynchronous gap ===========================
    | dart:async                                                     Future.catchError
    | package:pub/src/utils.dart 109:52                              captureErro[...]
    | package:stack_trace                                            Chain.capture
    | package:pub/src/utils.dart 122:11                              captureErrors
    | package:pub/src/command.dart 189:13                            PubCommand.run
    | package:args/command_runner.dart 209:27                        CommandRunn[...]
    | package:dartdev/dartdev.dart 231:30                            DartdevRunn[...]
    | package:args/command_runner.dart 119:25                        CommandRunn[...]
    | dart:async                                                     new Future.sync
    | package:args/command_runner.dart 119:14                        CommandRunner.run
    | package:dartdev/dartdev.dart 66:29                             runDartdev
    | /b/s/w/ir/cache/builder/sdk/pkg/dartdev/bin/dartdev.dart 11:9  main
---- End log transcript ----
IO  : Writing 2917 characters to text file /tmp/tool-envPATXHE/pub-cache-dirOLHK[...]

I'm not sure what info I can provide, this is the package failing

@isoos
Copy link
Collaborator

isoos commented Sep 27, 2022

pub.dev uses a fixed SDK version in each deployment, we don't auto-upgrade SDKs (yet). We've upgraded to 2.18.1, but we needed to roll back traffic because of a bug, and we are back to 2.18.0 now. We'll fix the deployment in the coming days, and the package will get updated with a new analysis and score (no new publish is needed).

@iapicca
Copy link
Author

iapicca commented Sep 27, 2022

@isoos I could track the bug and close this issue I guess
could you link it?

@iapicca iapicca closed this as completed Sep 27, 2022
@isoos
Copy link
Collaborator

isoos commented Sep 27, 2022

Even if the bug is closed, pub.dev is deployed manually, in multiple stages, it may take a day or two before the traffic hits the new version (and the new score gets visible).

@iapicca
Copy link
Author

iapicca commented Sep 27, 2022

no problem, thanks for the update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants