Upgrade to Dart 2.0.0

[chalin]

cc @kevmoo @kwalrath

[jcollins-g]

Problems in the bowels of our dependencies to sort through.

~/dart/dart-services
$ pub get
Resolving dependencies... (1.5s)
The current Dart SDK version is 2.0.0.

Because no versions of rpc match >0.6.0-dev.1 and rpc 0.6.0-dev.1 depends on gcloud >=0.2.0+12 <0.6.0, rpc >=0.6.0-dev.1 requires gcloud >=0.2.0+12
  <0.6.0.
So, because gcloud >=0.1.0 <=0.6.0 requires SDK version >=1.5.0 <2.0.0 or >=2.0.0-dev.54.0 <2.0.0 and dart_services depends on rpc >=0.6.0-dev.1,
  version solving failed.

[jcollins-g]

@kevmoo helped with that one in dart-archive/rpc#131 but there's more to knock out.

~/dart/dart-services
$ pub get
Resolving dependencies... (1.5s)
The current Dart SDK version is 2.0.0.

Because appengine >=0.4.4+1 depends on gcloud ^0.5.0 and appengine >=0.2.0
  <=0.4.4 requires SDK version >=1.5.0 <2.0.0, appengine >=0.2.0 requires gcloud
  ^0.5.0.
Because gcloud 0.5.0 requires SDK version >=2.0.0-dev.54.0 <2.0.0 and no
  versions of gcloud match >0.5.0 <0.6.0, gcloud ^0.5.0 is forbidden.
Thus, appengine >=0.2.0 is forbidden.
So, because dart_services depends on appengine >=0.4.0, version solving
  failed.

[kevmoo]

We likely need to get Martin Kusterman involved w/ reviews to pkg:appengine – but you could get a PR going

…

On Tue, Aug 7, 2018 at 1:35 PM Janice Collins ***@***.***> wrote: @kevmoo <https://github.com/kevmoo> helped with that one in dart-archive/rpc#131 <dart-archive/rpc#131> but there's more to knock out. ~/dart/dart-services $ pub get Resolving dependencies... (1.5s) The current Dart SDK version is 2.0.0. Because appengine >=0.4.4+1 depends on gcloud ^0.5.0 and appengine >=0.2.0 <=0.4.4 requires SDK version >=1.5.0 <2.0.0, appengine >=0.2.0 requires gcloud ^0.5.0. Because gcloud 0.5.0 requires SDK version >=2.0.0-dev.54.0 <2.0.0 and no versions of gcloud match >0.5.0 <0.6.0, gcloud ^0.5.0 is forbidden. Thus, appengine >=0.2.0 is forbidden. So, because dart_services depends on appengine >=0.4.0, version solving failed. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#845 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABCioYi1cMjHVT2bFZGAKV66dtgHFkPks5uOfoQgaJpZM4Vwp2v> .

[jcollins-g]

yeah. it's not going to be completely trivial. gcloud breaking changes impact this

[kevmoo]

:-/

…

On Tue, Aug 7, 2018 at 2:02 PM Janice Collins ***@***.***> wrote: yeah. it's not going to be completely trivial. gcloud breaking changes impact this — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#845 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABCilFtw_zNcIey_gFr_KQlHbmtbepoks5uOgBqgaJpZM4Vwp2v> .

[jcollins-g]

another package protobuf has problems that are fixed, but not published. google/protobuf.dart#117

[jcollins-g]

The appengine package also has problems, but I'm part-way through a fix. dart-lang/labs#155

[jcollins-g]

Protobuf problems are fixed and published. Appengine has a fix (dart-archive/appengine#81), and I've got test versions of dart-services and dart-pad that work with 2.0 now.

[jcollins-g]

#846 for the front-end

[jcollins-g]

Remaining blockers are gone with the recent appengine publish; when the backend change at dart-archive/dart-services#350 lands and is deployed we can close this out. Hoping to do this Monday.

[chalin]

Thanks for the update.

…

On Fri, Aug 17, 2018 at 5:15 PM Janice Collins ***@***.***> wrote: Remaining blockers are gone with the recent appengine publish; when the backend change at dart-archive/dart-services#350 <dart-archive/dart-services#350> lands and is deployed we can close this out. Hoping to do this Monday. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#845 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AD8u-cFT2LDj-soBr4QIJnn-G_UnmIwYks5uRzJzgaJpZM4Vwp2v> .

[chalin]

Great! Can you let us know once it is live?