[dart-misc] pub upgrade never completing

[Mark H]

Since updating to the most recent dev version that the Editor allows, I am
having problems with pub upgrade:

Dart Editor version 1.10.1.release (DEV)
Dart SDK version 1.10.1

Basically it never seems to complete and gets stuck in some sort of
dependency loop. I have tried the following command:

pub --trace --verbosity=solver upgrade

and have attached the output. However, I'm not entirely sure how to
interpret this to find out which package is causing the problem. Can anyone
take a quick peek at the output and give me some pointers as to what might
be the issue?

My pubspec file looks like this:

name: Autograph
description: Autograph Web Version
dependencies:
animation:
path: dev/Animation
bot: '>=0.27.0+2 <0.28.0'
browser: any
core_elements: '<0.7.0'
google_drive_v2_api: any
google_oauth2_client: any
js: '>=0.2.2 <0.3.0'
js_wrapping: any
math_expressions:
path: dev/math-expressions
polymer: '<0.16.0'
rikulo_commons: '<2.0.0'
rikulo_ui: any
three:
path: dev/three.dart
vector_math: any
widget:
path: dev/widget.dart
transformers:
- polymer:


Thanks.
Mark

[Günter Zöchbauer]

See https://groups.google.com/a/dartlang.org/forum/#!topic/misc/veOqltoM3aE
Try concrete ranges instead of `any`

Post by Mark H
Since updating to the most recent dev version that the Editor allows, I am
Dart Editor version 1.10.1.release (DEV)
Dart SDK version 1.10.1
Basically it never seems to complete and gets stuck in some sort of
pub --trace --verbosity=solver upgrade
and have attached the output. However, I'm not entirely sure how to
interpret this to find out which package is causing the problem. Can anyone
take a quick peek at the output and give me some pointers as to what might
be the issue?
name: Autograph
description: Autograph Web Version
path: dev/Animation
bot: '>=0.27.0+2 <0.28.0'
browser: any
core_elements: '<0.7.0'
google_drive_v2_api: any
google_oauth2_client: any
js: '>=0.2.2 <0.3.0'
js_wrapping: any
path: dev/math-expressions
polymer: '<0.16.0'
rikulo_commons: '<2.0.0'
rikulo_ui: any
path: dev/three.dart
vector_math: any
path: dev/widget.dart
Thanks.
Mark

[Mark H]

Yes, I did see this but, to be honest, I'm not exactly sure what concrete
ranges I should actually be setting for most of the packages as none of
them are actually written by me. Is it just a case of trial and error or is
there a more scientific way to work it all out?

Post by Mark H
Since updating to the most recent dev version that the Editor allows, I am
Dart Editor version 1.10.1.release (DEV)
Dart SDK version 1.10.1
Basically it never seems to complete and gets stuck in some sort of
pub --trace --verbosity=solver upgrade
and have attached the output. However, I'm not entirely sure how to
interpret this to find out which package is causing the problem. Can anyone
take a quick peek at the output and give me some pointers as to what might
be the issue?
name: Autograph
description: Autograph Web Version
path: dev/Animation
bot: '>=0.27.0+2 <0.28.0'
browser: any
core_elements: '<0.7.0'
google_drive_v2_api: any
google_oauth2_client: any
js: '>=0.2.2 <0.3.0'
js_wrapping: any
path: dev/math-expressions
polymer: '<0.16.0'
rikulo_commons: '<2.0.0'
rikulo_ui: any
path: dev/three.dart
vector_math: any
path: dev/widget.dart
Thanks.
Mark

[Günter Zöchbauer]

I usually try to get the latest version unless I run into any problems. If
this leads to unresolvable 'pub upgrade'/'pub get' conflicts, I usually get
a error message from pub. Then I widen the lower constraint until pub can
resolve the dependencies.

Post by Mark H
Yes, I did see this but, to be honest, I'm not exactly sure what concrete
ranges I should actually be setting for most of the packages as none of
them are actually written by me. Is it just a case of trial and error or is
there a more scientific way to work it all out?

Post by Mark H
Since updating to the most recent dev version that the Editor allows, I
Dart Editor version 1.10.1.release (DEV)
Dart SDK version 1.10.1
Basically it never seems to complete and gets stuck in some sort of
pub --trace --verbosity=solver upgrade
and have attached the output. However, I'm not entirely sure how to
interpret this to find out which package is causing the problem. Can anyone
take a quick peek at the output and give me some pointers as to what might
be the issue?
name: Autograph
description: Autograph Web Version
path: dev/Animation
bot: '>=0.27.0+2 <0.28.0'
browser: any
core_elements: '<0.7.0'
google_drive_v2_api: any
google_oauth2_client: any
js: '>=0.2.2 <0.3.0'
js_wrapping: any
path: dev/math-expressions
polymer: '<0.16.0'
rikulo_commons: '<2.0.0'
rikulo_ui: any
path: dev/three.dart
vector_math: any
path: dev/widget.dart
Thanks.
Mark

['Bob Nystrom' via Dart Misc]

I'm not exactly sure what concrete ranges I should actually be setting for
most of the packages as none of them are actually written by me. Is it just
a case of trial and error or is there a more scientific way to work it all
out?

The lower bound is basically >= the oldest version of the package that has
all of the features you need. When I first add a dependency, I typically
just use the current version of it as my lower bound. If I want to be an
extra good package citizen, I may try a few older versions too. (pub
downgrade helps for that.)

If that gave you a version like 0.x.y (i.e. something less than 1.0.0),
then the upper bound is usually <0.*(x+1)*.0.

If the version was like x.y.z (i.e. something 1.0.0 or greater), then the
upper bound is usually <*(x+1)*.0.0.

So, if the current version of foo is 0.3.5, the usual bound is >=0.3.5
<0.4.0. Or just use ^0.3.5, which means the same thing. :)

Cheers!

- bob

[Thomas Schranz]

Stupid q: would it help to cache some solved dependencies (eg if they are common?) or track which resolution attempts take a crazy amount of time and flag them?

I guess some dependency combinations might be fairly common patterns?

If it would work it probably is not very elegant but might ease the pain in some situations.

Disclaimer: I have no idea what I am talking about :)

['Natalie Weizenbaum' via Dart Misc]

The trouble with dependency solving in general is that it's extremely
context-dependent. Every package in the graph that has a dependency on X
matters when solving X, so there's not a great way to cache partial
information.

Post by Thomas Schranz
Stupid q: would it help to cache some solved dependencies (eg if they are
common?) or track which resolution attempts take a crazy amount of time and
flag them?
I guess some dependency combinations might be fairly common patterns?
If it would work it probably is not very elegant but might ease the pain
in some situations.
Disclaimer: I have no idea what I am talking about :)
--
For other discussions, see https://groups.google.com/a/dartlang.org/
For HOWTO questions, visit http://stackoverflow.com/tags/dart
To file a bug report or feature request, go to http://www.dartbug.com/new
To unsubscribe from this group and stop receiving emails from it, send an

[Mark H]

Thanks Bob. I'll use that system from now on.

I guess this implies that I need to regularly actively review my package
ranges as new versions of the various packages are released. I was
basically trying to eliminate this process by using 'any' (or large ranges)
to ensure that I was always using the latest version and then only
reverting back to an older version (via range limits) if things broke.
Obviously not a good plan though!

Cheers
Mark

Post by 'Bob Nystrom' via Dart Misc

I'm not exactly sure what concrete ranges I should actually be setting
for most of the packages as none of them are actually written by me. Is it
just a case of trial and error or is there a more scientific way to work it
all out?

The lower bound is basically >= the oldest version of the package that
has all of the features you need. When I first add a dependency, I
typically just use the current version of it as my lower bound. If I want
to be an extra good package citizen, I may try a few older versions too. (pub
downgrade helps for that.)
If that gave you a version like 0.x.y (i.e. something less than 1.0.0),
then the upper bound is usually <0.*(x+1)*.0.
If the version was like x.y.z (i.e. something 1.0.0 or greater), then the
upper bound is usually <*(x+1)*.0.0.
So, if the current version of foo is 0.3.5, the usual bound is >=0.3.5
<0.4.0. Or just use ^0.3.5, which means the same thing. :)
Cheers!
- bob

[Günter Zöchbauer]

I regularily run `pub upgrade` or `den fetch` which shows where newer
packages are available.
If you don't publish the packages to pub.dartlang.org, you can leave enough
room for newer version. Newer not-yet-existing versions wont cause
troubles. Including all old ones (and probably outdated anyways) generates
a lot of work for pub.
If pub starts having troubles again check the lower bounds and increase
where applicable.
In overall it shouldn't cause notable additional work.

Post by Mark H
Thanks Bob. I'll use that system from now on.
I guess this implies that I need to regularly actively review my package
ranges as new versions of the various packages are released. I was
basically trying to eliminate this process by using 'any' (or large ranges)
to ensure that I was always using the latest version and then only
reverting back to an older version (via range limits) if things broke.
Obviously not a good plan though!
Cheers
Mark

Post by 'Bob Nystrom' via Dart Misc

I'm not exactly sure what concrete ranges I should actually be setting
for most of the packages as none of them are actually written by me. Is it
just a case of trial and error or is there a more scientific way to work it
all out?

The lower bound is basically >= the oldest version of the package that
has all of the features you need. When I first add a dependency, I
typically just use the current version of it as my lower bound. If I want
to be an extra good package citizen, I may try a few older versions too. (pub
downgrade helps for that.)
If that gave you a version like 0.x.y (i.e. something less than 1.0.0),
then the upper bound is usually <0.*(x+1)*.0.
If the version was like x.y.z (i.e. something 1.0.0 or greater), then the
upper bound is usually <*(x+1)*.0.0.
So, if the current version of foo is 0.3.5, the usual bound is >=0.3.5
<0.4.0. Or just use ^0.3.5, which means the same thing. :)
Cheers!
- bob

[Mark H]

This turned out to be an issue with the latest version of js_wrapping. It
was causing a 'disjoint constraints on analyzer' with Polymer 0.15.5+4. I'm
not sure why pub upgrade couldn't resolve it though. Dependencies seem to
be a bit of a nightmare when they go wrong!

Thanks for your help.
Mark

Post by Mark H
Since updating to the most recent dev version that the Editor allows, I am
Dart Editor version 1.10.1.release (DEV)
Dart SDK version 1.10.1
Basically it never seems to complete and gets stuck in some sort of
pub --trace --verbosity=solver upgrade
and have attached the output. However, I'm not entirely sure how to
interpret this to find out which package is causing the problem. Can anyone
take a quick peek at the output and give me some pointers as to what might
be the issue?
name: Autograph
description: Autograph Web Version
path: dev/Animation
bot: '>=0.27.0+2 <0.28.0'
browser: any
core_elements: '<0.7.0'
google_drive_v2_api: any
google_oauth2_client: any
js: '>=0.2.2 <0.3.0'
js_wrapping: any
path: dev/math-expressions
polymer: '<0.16.0'
rikulo_commons: '<2.0.0'
rikulo_ui: any
path: dev/three.dart
vector_math: any
path: dev/widget.dart
Thanks.
Mark

[Günter Zöchbauer]

Yup. I haven used other dependency management systems a lot, but all I used
seem worse.
It's just a difficult problem.

Post by Mark H
This turned out to be an issue with the latest version of js_wrapping. It
was causing a 'disjoint constraints on analyzer' with Polymer 0.15.5+4.
I'm not sure why pub upgrade couldn't resolve it though. Dependencies seem
to be a bit of a nightmare when they go wrong!
Thanks for your help.
Mark

Post by Mark H
Since updating to the most recent dev version that the Editor allows, I
Dart Editor version 1.10.1.release (DEV)
Dart SDK version 1.10.1
Basically it never seems to complete and gets stuck in some sort of
pub --trace --verbosity=solver upgrade
and have attached the output. However, I'm not entirely sure how to
interpret this to find out which package is causing the problem. Can anyone
take a quick peek at the output and give me some pointers as to what might
be the issue?
name: Autograph
description: Autograph Web Version
path: dev/Animation
bot: '>=0.27.0+2 <0.28.0'
browser: any
core_elements: '<0.7.0'
google_drive_v2_api: any
google_oauth2_client: any
js: '>=0.2.2 <0.3.0'
js_wrapping: any
path: dev/math-expressions
polymer: '<0.16.0'
rikulo_commons: '<2.0.0'
rikulo_ui: any
path: dev/three.dart
vector_math: any
path: dev/widget.dart
Thanks.
Mark

['Natalie Weizenbaum' via Dart Misc]

Package resolution, as GÃŒnter points out, is a difficult problem. In fact,
it's NP-complete, which means that all known algorithms have some cases
where they go exponential and are unable to complete in a reasonable amount
of time. That said, there is room for improvement here; I have changes in
1.11 that make the solver much faster in some cases, and I'm planning on
more changes as well in the future.

The best thing you can do regardless of pub's solver, of course, is to
avoid any constraints and make the set of packages pub has to look through
much smaller.

Post by Günter Zöchbauer
Yup. I haven used other dependency management systems a lot, but all I
used seem worse.
It's just a difficult problem.

Post by Mark H
This turned out to be an issue with the latest version of js_wrapping. It
was causing a 'disjoint constraints on analyzer' with Polymer 0.15.5+4.
I'm not sure why pub upgrade couldn't resolve it though. Dependencies seem
to be a bit of a nightmare when they go wrong!
Thanks for your help.
Mark

Post by Mark H
Since updating to the most recent dev version that the Editor allows, I
Dart Editor version 1.10.1.release (DEV)
Dart SDK version 1.10.1
Basically it never seems to complete and gets stuck in some sort of
pub --trace --verbosity=solver upgrade
and have attached the output. However, I'm not entirely sure how to
interpret this to find out which package is causing the problem. Can anyone
take a quick peek at the output and give me some pointers as to what might
be the issue?
name: Autograph
description: Autograph Web Version
path: dev/Animation
bot: '>=0.27.0+2 <0.28.0'
browser: any
core_elements: '<0.7.0'
google_drive_v2_api: any
google_oauth2_client: any
js: '>=0.2.2 <0.3.0'
js_wrapping: any
path: dev/math-expressions
polymer: '<0.16.0'
rikulo_commons: '<2.0.0'
rikulo_ui: any
path: dev/three.dart
vector_math: any
path: dev/widget.dart
Thanks.
Mark

--

For other discussions, see https://groups.google.com/a/dartlang.org/
For HOWTO questions, visit http://stackoverflow.com/tags/dart
To file a bug report or feature request, go to http://www.dartbug.com/new
To unsubscribe from this group and stop receiving emails from it, send an

[Mark H]

My specific issue this time was caused by a newer, not-yet-existing (at the
time) version. I had js_wrapping set to 'any' which worked fine until v0.2
came along. At this point, pub upgrade updated js_wrapping but because the
new version specified a later version of analyzer than Polymer 0.15.5+4, it
caused the 'disjoint constraints' error. This then resulted in pub upgrade
getting stuck in an endless loop.

Post by Mark H
Since updating to the most recent dev version that the Editor allows, I am
Dart Editor version 1.10.1.release (DEV)
Dart SDK version 1.10.1
Basically it never seems to complete and gets stuck in some sort of
pub --trace --verbosity=solver upgrade
and have attached the output. However, I'm not entirely sure how to
interpret this to find out which package is causing the problem. Can anyone
take a quick peek at the output and give me some pointers as to what might
be the issue?
name: Autograph
description: Autograph Web Version
path: dev/Animation
bot: '>=0.27.0+2 <0.28.0'
browser: any
core_elements: '<0.7.0'
google_drive_v2_api: any
google_oauth2_client: any
js: '>=0.2.2 <0.3.0'
js_wrapping: any
path: dev/math-expressions
polymer: '<0.16.0'
rikulo_commons: '<2.0.0'
rikulo_ui: any
path: dev/three.dart
vector_math: any
path: dev/widget.dart
Thanks.
Mark

[Alexandre Ardhuin]

js_wrapping-0.2.x has nothing in common with the previous version. I
strongly recommend you to add a upper-bound version '<0.2.0' if you're fine
with the last 0.1.x version.

This new version is almost a new package that makes the old version
obsolete. It simplifies a lot the use of js lib but is completely different
of the previous version. Using this new version a lot it's really faster to
use js lib. You can have more informations on the README at
https://pub.dartlang.org/packages/js_wrapping . Feel free to migrate if you
have the time.

About the version constraint, js_wrapping-0.2.0 depends on source_gen-0.3.0
that depends on analyzer: ^0.24.0. On the other side Polymer 0.15.5+4
depends on analyzer: '>=0.15.6 <0.23.0'. You can try to add a
dependency_overrides to set analyzer to either ^0.23.0 or ^0.24.0 and see
if it works.

Cheers,
Alexandre

Post by Mark H
My specific issue this time was caused by a newer, not-yet-existing (at
the time) version. I had js_wrapping set to 'any' which worked fine until
v0.2 came along. At this point, pub upgrade updated js_wrapping but because
the new version specified a later version of analyzer than Polymer
0.15.5+4, it caused the 'disjoint constraints' error. This then resulted in
pub upgrade getting stuck in an endless loop.

Post by Mark H
Since updating to the most recent dev version that the Editor allows, I
Dart Editor version 1.10.1.release (DEV)
Dart SDK version 1.10.1
Basically it never seems to complete and gets stuck in some sort of
pub --trace --verbosity=solver upgrade
and have attached the output. However, I'm not entirely sure how to
interpret this to find out which package is causing the problem. Can anyone
take a quick peek at the output and give me some pointers as to what might
be the issue?
name: Autograph
description: Autograph Web Version
path: dev/Animation
bot: '>=0.27.0+2 <0.28.0'
browser: any
core_elements: '<0.7.0'
google_drive_v2_api: any
google_oauth2_client: any
js: '>=0.2.2 <0.3.0'
js_wrapping: any
path: dev/math-expressions
polymer: '<0.16.0'
rikulo_commons: '<2.0.0'
rikulo_ui: any
path: dev/three.dart
vector_math: any
path: dev/widget.dart
Thanks.
Mark

--
For other discussions, see https://groups.google.com/a/dartlang.org/
For HOWTO questions, visit http://stackoverflow.com/tags/dart
To file a bug report or feature request, go to http://www.dartbug.com/new
To unsubscribe from this group and stop receiving emails from it, send an

[Mark H]

I strongly recommend you to add a upper-bound version '<0.2.0' if you're

fine with the last 0.1.x version.

Thanks Alexandre. That's exactly what I have done for now to fix the pub
upgrade problem.

The new version of js_wrapping looks very interesting. I will take a look
when I have a few moments spare.

Cheers
Mark

js_wrapping-0.2.x has nothing in common with the previous version. I
strongly recommend you to add a upper-bound version '<0.2.0' if you're fine
with the last 0.1.x version.
This new version is almost a new package that makes the old version
obsolete. It simplifies a lot the use of js lib but is completely different
of the previous version. Using this new version a lot it's really faster to
use js lib. You can have more informations on the README at
https://pub.dartlang.org/packages/js_wrapping . Feel free to migrate if
you have the time.
About the version constraint, js_wrapping-0.2.0 depends on
source_gen-0.3.0 that depends on analyzer: ^0.24.0. On the other side
Polymer 0.15.5+4 depends on analyzer: '>=0.15.6 <0.23.0'. You can try to
add a dependency_overrides to set analyzer to either ^0.23.0 or ^0.24.0 and
see if it works.
Cheers,
Alexandre

Post by Mark H
My specific issue this time was caused by a newer, not-yet-existing (at
the time) version. I had js_wrapping set to 'any' which worked fine until
v0.2 came along. At this point, pub upgrade updated js_wrapping but because
the new version specified a later version of analyzer than Polymer
0.15.5+4, it caused the 'disjoint constraints' error. This then resulted in
pub upgrade getting stuck in an endless loop.

Post by Mark H
Since updating to the most recent dev version that the Editor allows, I
Dart Editor version 1.10.1.release (DEV)
Dart SDK version 1.10.1
Basically it never seems to complete and gets stuck in some sort of
pub --trace --verbosity=solver upgrade
and have attached the output. However, I'm not entirely sure how to
interpret this to find out which package is causing the problem. Can anyone
take a quick peek at the output and give me some pointers as to what might
be the issue?
name: Autograph
description: Autograph Web Version
path: dev/Animation
bot: '>=0.27.0+2 <0.28.0'
browser: any
core_elements: '<0.7.0'
google_drive_v2_api: any
google_oauth2_client: any
js: '>=0.2.2 <0.3.0'
js_wrapping: any
path: dev/math-expressions
polymer: '<0.16.0'
rikulo_commons: '<2.0.0'
rikulo_ui: any
path: dev/three.dart
vector_math: any
path: dev/widget.dart
Thanks.
Mark

--
For other discussions, see https://groups.google.com/a/dartlang.org/
For HOWTO questions, visit http://stackoverflow.com/tags/dart
To file a bug report or feature request, go to http://www.dartbug.com/new
To unsubscribe from this group and stop receiving emails from it, send an

[Günter Zöchbauer]

I guess the problem is then the combination of `any` for this package,
where the latest version is incompatible with most other packages and also
`any` for all other packages. If you had constraints on all other packages
pub would result in an error quickly, probably giving a hint which package
caused the error.

Post by Mark H
My specific issue this time was caused by a newer, not-yet-existing (at
the time) version. I had js_wrapping set to 'any' which worked fine until
v0.2 came along. At this point, pub upgrade updated js_wrapping but because
the new version specified a later version of analyzer than Polymer
0.15.5+4, it caused the 'disjoint constraints' error. This then resulted in
pub upgrade getting stuck in an endless loop.

Post by Mark H
Since updating to the most recent dev version that the Editor allows, I
Dart Editor version 1.10.1.release (DEV)
Dart SDK version 1.10.1
Basically it never seems to complete and gets stuck in some sort of
pub --trace --verbosity=solver upgrade
and have attached the output. However, I'm not entirely sure how to
interpret this to find out which package is causing the problem. Can anyone
take a quick peek at the output and give me some pointers as to what might
be the issue?
name: Autograph
description: Autograph Web Version
path: dev/Animation
bot: '>=0.27.0+2 <0.28.0'
browser: any
core_elements: '<0.7.0'
google_drive_v2_api: any
google_oauth2_client: any
js: '>=0.2.2 <0.3.0'
js_wrapping: any
path: dev/math-expressions
polymer: '<0.16.0'
rikulo_commons: '<2.0.0'
rikulo_ui: any
path: dev/three.dart
vector_math: any
path: dev/widget.dart
Thanks.
Mark