Thanks for the feedback Jens.

On Mon, Sep 8, 2014 at 1:31 PM, Jens <[email protected]> wrote:

> Any new bugs to report?
>>
>
> Some things we have observed at work while using latest trunk SDM (compile
> per file):
>
> 1.) If we don't use -noprecompile then SDM does not start because it says
> it has found more than one permutation. If we use -noprecompile then SDM
> starts and the first compile through the bookmarklet works as well. Our
> trunk build from 1st Sep still worked in both situations. With current
> trunk the precompile says that it can not set the locale property to "en"
> because only "de" was allowed, then tries a fallback value and finally the
> precompile fails.
>
I'm working on a CL right now to opt -XcompilePerFile into the
-noprecompile behavior for just the reason. Should be in today.

>
> 2.) From time to time it happens that a recompile through the bookmarklet
> breaks the app because some JS isn't emitted correctly. For example we have
> a factory that creates a specific Ginjector and that factory has rebind
> rules that are triggered by a form factor property. Just today a colleague
> <http://www.dict.cc/englisch-deutsch/colleague.html> has recompiled the
> app and got "DesktopGinjectorProvider is undefined". Another example is
> that a custom composite stopped working with error "undefined is not a
> function". Taking a look at the JS code is seems like the problem happened
> in the constructor function that wanted to call the clinit function for
> that class. The machine that had the issue also had Chrome beta so I wasn't
> able to debug the pure JS because of 4.)
>
I've fixed two Gin generator related breakages like this so far. Are you
sure this is occurring with HEAD? If so then there's definitely a bug in
the "stale types marking" code that needs finding. If you can make a repro
case I'll figure it out.

>
> 3.) On one machine the first compilation after starting SDM with
> -noprecompile never finishes. The CodeServer java process does some heavy
> work for the first minute or so and then goes to sleep and thats it. I call
> it "SDM progress dots of death". The CodeServer arguments are exactly the
> same as on other machines which work without issue. I have no idea why this
> is happening. Also this only happens with latest trunk, a build from 1st
> Sep works.
>
Hmmm, that's really strange. It doesn't sound -XcompilePerFIle related so I
probably won't take a look at it for now. Maybe Brian will want to take a
look.

>
> 4.) Not directly GWT related but you might want to know it: The new Chrome
> beta contains the change that Brian asked for which marks lines without
> source maps in gray so you know that you can not put a breakpoint on these
> lines. However for some reasons Chrome now also forbids setting breakpoints
> in the pure JS file (e.g. app-0.js) if no source map entry was found for
> that JS line. That can be quite annoying. For example I couldn't set a
> breakpoint inside a class constructor function because the whole JS
> function wasn't source mapped.
>
+skybrian

>
>
> -- J.
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/5b8b733b-ef6c-4aaa-a071-d0bf4b027ca6%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/5b8b733b-ef6c-4aaa-a071-d0bf4b027ca6%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAFw3gJ9AjhxBfycmbkuYnh461MnsACpP96PULbJ%2B2LOViyXzyA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to