These are chat archives for AvaloniaUI/Avalonia

5th
Apr 2017
Steven Kirk
@grokys
Apr 05 2017 07:12
appveyor seems be be hanging on
Avalonia.AndroidTestApplication -> C:\projects\Avalonia\src\Android\Avalonia.AndroidTestApplication\bin\Release\Avalonia.AndroidTestApplication.dll
is that an appveyor problem or our problemi wonder?
rebuilding 5af27d9d (the last passing appveyor commit) to see if that still passes
Steven Kirk
@grokys
Apr 05 2017 07:38
seems it's happening there too so seems to be an appveyor problem?
danwalmsley
@danwalmsley
Apr 05 2017 10:02
@/all found this site... https://apisof.net/
if you are porting to net standard or net core
and not sure which assembly apis have moved to
you can search on this site
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 14:21

is that an appveyor problem or our problemi wonder?

@grokys Probably issue with VS2017/xamarin , try disabling parallel build (set max to 1) and rebuild solution, its hanging on my machine

and build takes lot longer than previously
I am using Version 15.0.26228.12 D15RTWSVC version
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 14:27
or I think there is something wrong with git repo and its messing with solution build
One less mobile platform to worry about
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 18:34
2017-04-05_20-33-55.png
this is timing-out Appveyor builds
Steven Kirk
@grokys
Apr 05 2017 18:52
@wieslawsoltes so you can reproduce it locally huh?
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 18:52
yes
trying to remove test application and see if this goes aways
Steven Kirk
@grokys
Apr 05 2017 18:52
any idea what's causing it and why it's only started now?
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 18:53
no idea
2017-04-05_20-53-55.png
msbuild memory usage :fire:
Steven Kirk
@grokys
Apr 05 2017 18:55
is it xamarin that's causing the problem? i've not installed xamarin on my 2017 instance
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 18:55
not sure
I did not update xamarin only vs2017
maybe something with msbuild
removed Avalonia.AndroidTestApplication and Avalonia.iOSTestApplication and solution builds
Steven Kirk
@grokys
Apr 05 2017 18:58
i'm not seeing it here, you see
hmm so looks like a xamarin problem which would explain why it's happening on appveyor but not travis too
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 18:59
the issue is with Avalonia.AndroidTestApplication
Steven Kirk
@grokys
Apr 05 2017 19:01
do we even need that any more? we have ControlCatalog.Android
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 19:04
we can temporarily remove just from solution
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 19:09
@grokys same issue with ControlCatalog.Android :(
Steven Kirk
@grokys
Apr 05 2017 19:09
basically xamarin is broken
but why only now??!
it was working a couple of days ago
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 19:11
i can build blank android apps is vs2017
Nikita Tsukanov
@kekekeks
Apr 05 2017 19:36
It probably tries to deploy the app or something
I have to unload android projects during development
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 19:45
msbuild is building same projects again and again in infinite loop
Nikita Tsukanov
@kekekeks
Apr 05 2017 19:56
RTM they said
Production ready, they said
Commercially reasonable support, they said
Steven Kirk
@grokys
Apr 05 2017 20:52
@wieslawsoltes seems to be hanging now building Avalonia.iOS :(
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 20:56
it was building on my machine but took some time too
maybe it will help
Steven Kirk
@grokys
Apr 05 2017 21:02
ah yeah it seems to have got a bit further now
do you think it's that that might have caused it?
i don't know if appveyor automatically update their VS images
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 21:04
I thinks its some issue with msbuild project references
Steven Kirk
@grokys
Apr 05 2017 21:04
the thing that i just don't get is why it started yesterday
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 21:07
maybe appveyor applied VS2017 patch
March 31, 2017 - version 15.0 (26228.12)
I'm installing April 5, 2017 - version 15.1 (26403.00) update and will check if issue is still there
looks like there have been changes related to Xamarin in
Release Date: March 31, 2017 - version 15.0 (26228.12)
What's New in this Release
We now support Xcode 8.3, iOS 10.3, watchOS 3.2, and tvOS 10.2 tools and APIs in the Xamarin.VS Extension for Visual Studio 2017.
Steven Kirk
@grokys
Apr 05 2017 21:12
this one passed on 3rd april though
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 21:13
appveyor must applied patch with some delay
Steven Kirk
@grokys
Apr 05 2017 21:13
perhaps yeah
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 21:14
seems like version 15.1 (26403.00) is pretty big update
I think appveyor VS2017 images have limited memory and msbuild is using GBs of memory
so it also slows down builds
Steven Kirk
@grokys
Apr 05 2017 21:15
yeah, it's going really slow
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 21:16
i think on my machine msbuild was using ~10GB :fire:
Steven Kirk
@grokys
Apr 05 2017 21:17
wow
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 21:17
this is when if you enable parallel builds
Steven Kirk
@grokys
Apr 05 2017 21:17
i suspected it might be a mistake to jump to using the new stuff so soon :/
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 21:17
normally is limited by memory as it is 32-bit process
the dotnet stuff works pretty good
Steven Kirk
@grokys
Apr 05 2017 21:18
it's just vs and msbuild that don't...
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 21:22
version 15.1 (26403.00) does not have NuGet fixes :(
but I was able to build Avalonia.AndroidTestApplication it took a lot of memory and little time but finally compiled
don't think appveyor can build Avalonia solution under 1h
2017-04-05_23-25-42.png
~15GB to build Avalonia with Visual Studio 2017 15.1 (26403.00)
Steven Kirk
@grokys
Apr 05 2017 21:28
yeah, the build for #950 has nearly taken an hour - not sure it will finish in time
that's crazy. an hour to build!
i'm going to file an issue on the appveyor forum
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 21:33
57 min 10 sec
yeah
i think we should hold off merging #950 until we have an idea what's causing the problem
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 21:42
ok
Steven Kirk
@grokys
Apr 05 2017 21:48
it's annoying that VS2017 can't even keep up with my typing...
i don't even type that fast
Wiesław Šoltés
@wieslawsoltes
Apr 05 2017 21:58
yeah I had same experience with high memory usage
with latest April 5, 2017 - version 15.1 (26403.00) is still high memory usage
Nikita Tsukanov
@kekekeks
Apr 05 2017 22:02
Got hardware issues with my laptop, tried to run VS2017 on the old one
Ended up in a store looking for a new one, since it wasn't quite possible to run it on Core2 Duo
Nikita Tsukanov
@kekekeks
Apr 05 2017 23:21

@grokys I have "great" news, new we-do-not-know-how-to-read-old-code-so-we-will-instead-create-a-new-worse-product display server for linux won't support global window coordinates

https://blog.gtk.org/2016/07/15/future-of-relative-window-positioning/

So no client/screen coordinate transformations for us anymore
Darnell Williams
@Seeker1437
Apr 05 2017 23:28
Why... this is upsetting
Nikita Tsukanov
@kekekeks
Apr 05 2017 23:28
Everything about that crap is, actually
The problem is that it will be force-integrated just like systemd
Darnell Williams
@Seeker1437
Apr 05 2017 23:29
:(
Nikita Tsukanov
@kekekeks
Apr 05 2017 23:32
There is another issue with window decorations
There is no way to tell the display server that you want it to render window border, title and buttons for you
There is also no way to grab the mouse
Nikita Tsukanov
@kekekeks
Apr 05 2017 23:38
basically it's only usable for hello world and social network client apps