RE: Release compilation does not work: maven modules and crux

[Maria Jose Esteve]

Definitely, the SDK is not the problem, or at least it is not the only problem.
I have compiled the 2020 project, both with SDK 0.9.8 and SDK 0.9.9 and the 
result is the same, release version works.
Neither is the problem crux + Maven modules.

Hiedra

De: Maria Jose Esteve 
Enviado el: viernes, 31 de diciembre de 2021 14:35
Para: users@royale.apache.org
Asunto: RE: Release compilation does not work: maven modules and crux

I have obtained the js-release folder that I used in the production deployment, 
dated Dec. 9,2020; I have released it and it works.
I also have the project code from the same date and compiled it with the 
apache-royale-0.9.8-bin-js distribution, downloaded from Jenkins as of Dec. 15, 
2020 (I had to make some changes to the pom's such as including 
true to fix the error with "fx:Array", in the library [1] ). 
The release on debug and release are perfect.

I'm going to try to compile my current project with the same SDK. I will come 
back here with the results.
Can you think of any other tests that might clear the doubts?

[1] This tag could not be resolved to an ActionScript class. It will be ignored.

^

Hiedra

De: Maria Jose Esteve 
Enviado el: viernes, 31 de diciembre de 2021 1:38
Para: users@royale.apache.org
Asunto: RE: Release compilation does not work: maven modules and crux

On December 9, 2020 I compiled a release version that worked. It had much less 
code but the structure and mvc implementations using crux was the same.
I will do a first test with SDK 0.9.9 and the code at that time and if it gives 
error I will compile the SDK to that date.

Hiedra

De: Maria Jose Esteve 
Enviado el: viernes, 31 de diciembre de 2021 0:36
Para: users@royale.apache.org
Asunto: Release compilation does not work: maven modules and crux

Hi Greg, yes.
I did a production deployment over 6 months ago and it worked. I had in mind to 
look for "that point" in the repository and maybe it's already time... I don't 
usually give up, but I lack the knowledge to solve this, I'm bugging and 
bugging Harb and I've done 100 tests without success.

Right now I'm debugging App.js, as suggested by Harb, and what I've discovered 
so far is that "other models", also located in the modules [1] of my library, 
are loaded correctly (crux)

[1] I don't use modules like Roman, I use Maven modules and, like you, I have a 
hierarchy of pom's

Hiedra

De: Greg Dove mailto:greg.d...@gmail.com>>
Enviado el: jueves, 30 de diciembre de 2021 23:23
Para: users@royale.apache.org<mailto:users@royale.apache.org>
Asunto: Re: Compiling Modules (was Re: Load time is very slow)


Sorry I have not been following these threads in detail because I have been 
(and am currently still) on vacation.
AFAIK royale modules are not reliable in release mode. I don't know anyone who 
has had experience otherwise. I did try testing them some time ago and that was 
my experience, and I believe we had similar feedback from others in the 
community (who were early users) that it was working for them in the debug 
build, but not the release build.

Perhaps it can work in very simple cases in release builds, but beyond that I 
think the work on them is not complete. If there are others in the community 
whose experience is different and can confirm that things are working for them 
in release builds, please let us know.

Maria, it is also possible that in your case, that use of Crux inside modules 
is another layer of complexity in release mode, because I did not test that 
when I did the original work on Crux. Was this working at some point in the 
past and it has now stopped working?




On Fri, Dec 31, 2021 at 11:10 AM Roman Isitua 
mailto:romanisi...@gmail.com>> wrote:
Yes.
On Thu, 30 Dec 2021, 23:03 Harbs, 
mailto:harbs.li...@gmail.com>> wrote:
Did you apply the input_file options to the module?

On Dec 30, 2021, at 11:42 PM, Roman Isitua 
mailto:romanisi...@gmail.com>> wrote:


I have applied the js compiler option as follows

-source-map=false;-compiler.show-binding-warnings=false;-js-default-initializers=true;-js-dynamic-access-unknown-members=true;
-js-compiler-option=--variable_map_output_file 
gccvars.txt;-js-compiler-option+=--property_map_output_file gccprops.txt
  


I get the same error as before when attempting to launch the jewel module.




Same error trace.

Uncaught TypeError: cm.valuesImpl.init is not a function
at Rr.Mr.yl (Overview.js:786)
at Function.iq.generateMXMLProperties (Overview.js:736)
at Rr.hq.generateMXMLAttributes (Overview.js:546)
at new Rr (Overview.js:804)
at LN.J.loadHandler (FrontEnd.js:1967)
FrontEnd.js:1640 Uncaught TypeError: M is not a function
at oM.J.handleMouseOut (FrontEnd.js:1640)
at Function.ny [as googFireListener] (FrontEnd.js:123)
at ny (FrontEnd.js:248)
at HTMLAnchorElemen

RE: Release compilation does not work: maven modules and crux

[Maria Jose Esteve]

I have obtained the js-release folder that I used in the production deployment, 
dated Dec. 9,2020; I have released it and it works.
I also have the project code from the same date and compiled it with the 
apache-royale-0.9.8-bin-js distribution, downloaded from Jenkins as of Dec. 15, 
2020 (I had to make some changes to the pom's such as including 
true to fix the error with "fx:Array", in the library [1] ). 
The release on debug and release are perfect.

I'm going to try to compile my current project with the same SDK. I will come 
back here with the results.
Can you think of any other tests that might clear the doubts?

[1] This tag could not be resolved to an ActionScript class. It will be ignored.

^

Hiedra

De: Maria Jose Esteve 
Enviado el: viernes, 31 de diciembre de 2021 1:38
Para: users@royale.apache.org
Asunto: RE: Release compilation does not work: maven modules and crux

On December 9, 2020 I compiled a release version that worked. It had much less 
code but the structure and mvc implementations using crux was the same.
I will do a first test with SDK 0.9.9 and the code at that time and if it gives 
error I will compile the SDK to that date.

Hiedra

De: Maria Jose Esteve 
Enviado el: viernes, 31 de diciembre de 2021 0:36
Para: users@royale.apache.org
Asunto: Release compilation does not work: maven modules and crux

Hi Greg, yes.
I did a production deployment over 6 months ago and it worked. I had in mind to 
look for "that point" in the repository and maybe it's already time... I don't 
usually give up, but I lack the knowledge to solve this, I'm bugging and 
bugging Harb and I've done 100 tests without success.

Right now I'm debugging App.js, as suggested by Harb, and what I've discovered 
so far is that "other models", also located in the modules [1] of my library, 
are loaded correctly (crux)

[1] I don't use modules like Roman, I use Maven modules and, like you, I have a 
hierarchy of pom's

Hiedra

De: Greg Dove mailto:greg.d...@gmail.com>>
Enviado el: jueves, 30 de diciembre de 2021 23:23
Para: users@royale.apache.org<mailto:users@royale.apache.org>
Asunto: Re: Compiling Modules (was Re: Load time is very slow)


Sorry I have not been following these threads in detail because I have been 
(and am currently still) on vacation.
AFAIK royale modules are not reliable in release mode. I don't know anyone who 
has had experience otherwise. I did try testing them some time ago and that was 
my experience, and I believe we had similar feedback from others in the 
community (who were early users) that it was working for them in the debug 
build, but not the release build.

Perhaps it can work in very simple cases in release builds, but beyond that I 
think the work on them is not complete. If there are others in the community 
whose experience is different and can confirm that things are working for them 
in release builds, please let us know.

Maria, it is also possible that in your case, that use of Crux inside modules 
is another layer of complexity in release mode, because I did not test that 
when I did the original work on Crux. Was this working at some point in the 
past and it has now stopped working?




On Fri, Dec 31, 2021 at 11:10 AM Roman Isitua 
mailto:romanisi...@gmail.com>> wrote:
Yes.
On Thu, 30 Dec 2021, 23:03 Harbs, 
mailto:harbs.li...@gmail.com>> wrote:
Did you apply the input_file options to the module?

On Dec 30, 2021, at 11:42 PM, Roman Isitua 
mailto:romanisi...@gmail.com>> wrote:


I have applied the js compiler option as follows

-source-map=false;-compiler.show-binding-warnings=false;-js-default-initializers=true;-js-dynamic-access-unknown-members=true;
-js-compiler-option=--variable_map_output_file 
gccvars.txt;-js-compiler-option+=--property_map_output_file gccprops.txt
  


I get the same error as before when attempting to launch the jewel module.




Same error trace.

Uncaught TypeError: cm.valuesImpl.init is not a function
at Rr.Mr.yl (Overview.js:786)
at Function.iq.generateMXMLProperties (Overview.js:736)
at Rr.hq.generateMXMLAttributes (Overview.js:546)
at new Rr (Overview.js:804)
at LN.J.loadHandler (FrontEnd.js:1967)
FrontEnd.js:1640 Uncaught TypeError: M is not a function
at oM.J.handleMouseOut (FrontEnd.js:1640)
at Function.ny [as googFireListener] (FrontEnd.js:123)
at ny (FrontEnd.js:248)
at HTMLAnchorElement.iy (FrontEnd.js:125)
at HTMLAnchorElement.b (FrontEnd.js:121)
FrontEnd.js:1640 Uncaught TypeError: M is not a function
at oM.J.handleMouseOver (FrontEnd.js:1640)
at Function.ny [as googFireListener] (FrontEnd.js:123)
at ny (FrontEnd.js:248)
at HTMLAnchorElement.iy (FrontEnd.js:125)
at HTMLAnchorElement.b (FrontEnd.js:121)
FrontEnd.js:1640 Uncaught TypeError: M is not a function
at oM.J.handleMouseO

Re: Release compilation does not work: maven modules and crux

[Roman Isitua]

Hi Maria,

Just a clarification. I am using maven modules in my application. I have a
hierarchy of pom's as well.

I tried to follow the below royale example strictly.

https://royale.apache.org/dividing-an-apache-royale-application-with-modules/

I am also using crux as well.

It is good to note that royale modules were working for you before. It
means something changed recently for it  to stop working.




On Fri, 31 Dec 2021, 00:35 Maria Jose Esteve,  wrote:

> Hi Greg, yes.
>
> I did a production deployment over 6 months ago and it worked. I had in
> mind to look for "that point" in the repository and maybe it's already
> time... I don't usually give up, but I lack the knowledge to solve this,
> I'm bugging and bugging Harb and I've done 100 tests without success.
>
>
>
> Right now I'm debugging App.js, as suggested by Harb, and what I've
> discovered so far is that "other models", also located in the modules [1]
> of my library, are loaded correctly (crux)
>
>
>
> [1] I don't use modules like Roman, I use Maven modules and, like you, I
> have a hierarchy of pom's
>
>
>
> Hiedra
>
>
>
> *De:* Greg Dove 
> *Enviado el:* jueves, 30 de diciembre de 2021 23:23
> *Para:* users@royale.apache.org
> *Asunto:* Re: Compiling Modules (was Re: Load time is very slow)
>
>
>
>
> Sorry I have not been following these threads in detail because I have
> been (and am currently still) on vacation.
>
> AFAIK royale modules are not reliable in release mode. I don't know anyone
> who has had experience otherwise. I did try testing them some time ago and
> that was my experience, and I believe we had similar feedback from others
> in the community (who were early users) that it was working for them in the
> debug build, but not the release build.
>
>
>
> Perhaps it can work in very simple cases in release builds, but beyond
> that I think the work on them is not complete. If there are others in the
> community whose experience is different and can confirm that things are
> working for them in release builds, please let us know.
>
>
>
> Maria, it is also possible that in your case, that use of Crux inside
> modules is another layer of complexity in release mode, because I did not
> test that when I did the original work on Crux. Was this working at some
> point in the past and it has now stopped working?
>
>
>
>
>
>
>
>
>
> On Fri, Dec 31, 2021 at 11:10 AM Roman Isitua 
> wrote:
>
> Yes.
>
> On Thu, 30 Dec 2021, 23:03 Harbs,  wrote:
>
> Did you apply the input_file options to the module?
>
>
>
> On Dec 30, 2021, at 11:42 PM, Roman Isitua  wrote:
>
>
>
>
>
> I have applied the js compiler option as follows
>
>
>
>
> -source-map=false;-compiler.show-binding-warnings=false;-js-default-initializers=true;-js-dynamic-access-unknown-members=true;
> -js-compiler-option=--variable_map_output_file
> gccvars.txt;-js-compiler-option+=--property_map_output_file gccprops.txt
>   
>
>
>
>
>
> I get the same error as before when attempting to launch the jewel module.
>
>
>
> 
>
>
>
>
>
> Same error trace.
>
>
>
> Uncaught TypeError: cm.valuesImpl.init is not a function
> at Rr.Mr.yl (Overview.js:786)
> at Function.iq.generateMXMLProperties (Overview.js:736)
> at Rr.hq.generateMXMLAttributes (Overview.js:546)
> at new Rr (Overview.js:804)
> at LN.J.loadHandler (FrontEnd.js:1967)
> FrontEnd.js:1640 Uncaught TypeError: M is not a function
> at oM.J.handleMouseOut (FrontEnd.js:1640)
> at Function.ny [as googFireListener] (FrontEnd.js:123)
> at ny (FrontEnd.js:248)
> at HTMLAnchorElement.iy (FrontEnd.js:125)
> at HTMLAnchorElement.b (FrontEnd.js:121)
> FrontEnd.js:1640 Uncaught TypeError: M is not a function
> at oM.J.handleMouseOver (FrontEnd.js:1640)
> at Function.ny [as googFireListener] (FrontEnd.js:123)
> at ny (FrontEnd.js:248)
> at HTMLAnchorElement.iy (FrontEnd.js:125)
> at HTMLAnchorElement.b (FrontEnd.js:121)
> FrontEnd.js:1640 Uncaught TypeError: M is not a function
> at oM.J.handleMouseOut (FrontEnd.js:1640)
> at Function.ny [as googFireListener] (FrontEnd.js:123)
> at ny (FrontEnd.js:248)
> at HTMLAnchorElement.iy (FrontEnd.js:125)
> at HTMLAnchorElement.b (FrontEnd.js:121)
> FrontEnd.js:1640 Uncaught TypeError: M is not a function
> at oM.J.handleMouseOver (FrontEnd.js:1640)
> at Function.ny [as googFireListener] (FrontEnd.js:123)
> at ny (FrontEnd.js:248)
> at HTMLAnchorElement.iy (FrontEnd.js:125)
> at HTMLAnchorElement.b (FrontEnd.js:121)
> FrontEnd.js:1640 Uncaught TypeError: M is not a function
> at oM.J.handleMouseOut (FrontEnd.js:1640)
> at Function.ny [as googFireListener] (FrontEnd.js:123)
> at ny (FrontEnd.js:248)
> at HTMLAnchorElement.iy (FrontEnd.js:125)
> at HTMLAnchorElement.b (FrontEnd.js:121)
> FrontEnd.js:1640 Uncaught TypeError: M is not a function
> at oM.J.handleMouseOver (FrontEnd.js:1640)
> at Function.ny [as googFireListener] (FrontEnd.js:123)
> at ny (Fro

Re: Release compilation does not work: maven modules and crux

[Greg Dove]

Maria:
"I don't use modules like Roman, I use Maven modules and, like you, I have
a hierarchy of pom's"

Ok, so there is perhaps a difference of vocabulary here, and the issue for
you is quite unrelated to the issue that Roman has.

Maven 'modules' in this case represent different compilation tasks defined
via the pom's (usually a series of swcs, and then an application which is
built from local application code, and pre-compiled code from the swcs),
whereas the royale runtime 'modules' are an emulation of the Flex
runtime-loaded 'modules'. It gets potentially more confusing if you combine
the two (which of course is possible).

So if you are not using 'royale runtime loaded modules', and just 'maven
modules' then something else may have changed.

If you have an initialize handler in your application, then try to simply
put this somewhere inside your initialize handler:
import
com.iest.winplusweb.models.MasterConfigSystemModel;MasterConfigSystemModel;


If that makes it work and it fails without doing that, then perhaps the:
-keep-code-with-metadata=Inject

is no longer working after other recent compiler changes... (just one
guess, probably not a good one).

I can't think of anything else to try offhand, but I will try to give it
some more thought.











On Fri, Dec 31, 2021 at 1:38 PM Maria Jose Esteve  wrote:

> On December 9, 2020 I compiled a release version that worked. It had much
> less code but the structure and mvc implementations using crux was the same.
>
> I will do a first test with SDK 0.9.9 and the code at that time and if it
> gives error I will compile the SDK to that date.
>
>
>
> Hiedra
>
>
>
> *De:* Maria Jose Esteve 
> *Enviado el:* viernes, 31 de diciembre de 2021 0:36
> *Para:* users@royale.apache.org
> *Asunto:* Release compilation does not work: maven modules and crux
>
>
>
> Hi Greg, yes.
>
> I did a production deployment over 6 months ago and it worked. I had in
> mind to look for "that point" in the repository and maybe it's already
> time... I don't usually give up, but I lack the knowledge to solve this,
> I'm bugging and bugging Harb and I've done 100 tests without success.
>
>
>
> Right now I'm debugging App.js, as suggested by Harb, and what I've
> discovered so far is that "other models", also located in the modules [1]
> of my library, are loaded correctly (crux)
>
>
>
> [1] I don't use modules like Roman, I use Maven modules and, like you, I
> have a hierarchy of pom's
>
>
>
> Hiedra
>
>
>
> *De:* Greg Dove 
> *Enviado el:* jueves, 30 de diciembre de 2021 23:23
> *Para:* users@royale.apache.org
> *Asunto:* Re: Compiling Modules (was Re: Load time is very slow)
>
>
>
>
> Sorry I have not been following these threads in detail because I have
> been (and am currently still) on vacation.
>
> AFAIK royale modules are not reliable in release mode. I don't know anyone
> who has had experience otherwise. I did try testing them some time ago and
> that was my experience, and I believe we had similar feedback from others
> in the community (who were early users) that it was working for them in the
> debug build, but not the release build.
>
>
>
> Perhaps it can work in very simple cases in release builds, but beyond
> that I think the work on them is not complete. If there are others in the
> community whose experience is different and can confirm that things are
> working for them in release builds, please let us know.
>
>
>
> Maria, it is also possible that in your case, that use of Crux inside
> modules is another layer of complexity in release mode, because I did not
> test that when I did the original work on Crux. Was this working at some
> point in the past and it has now stopped working?
>
>
>
>
>
>
>
>
>
> On Fri, Dec 31, 2021 at 11:10 AM Roman Isitua 
> wrote:
>
> Yes.
>
> On Thu, 30 Dec 2021, 23:03 Harbs,  wrote:
>
> Did you apply the input_file options to the module?
>
>
>
> On Dec 30, 2021, at 11:42 PM, Roman Isitua  wrote:
>
>
>
>
>
> I have applied the js compiler option as follows
>
>
>
>
> -source-map=false;-compiler.show-binding-warnings=false;-js-default-initializers=true;-js-dynamic-access-unknown-members=true;
> -js-compiler-option=--variable_map_output_file
> gccvars.txt;-js-compiler-option+=--property_map_output_file gccprops.txt
>   
>
>
>
>
>
> I get the same error as before when attempting to launch the jewel module.
>
>
>
> 
>
>
>
>
>
> Same error trace.
>
>
>
> Uncaught TypeError: cm.valuesImpl.init is not a function
> at Rr.Mr.yl (Overview.js:786)
> at Function.iq.generateMXMLProperties (Overview.js:736)
> at Rr.hq.generateMXMLAttributes (Overview.js:546)
> at new Rr (Overview.js:804)
> at LN.J.loadHandler (FrontEnd.js:1967)
> FrontEnd.js:1640 Uncaught TypeError: M is not a function
> at oM.J.handleMouseOut (FrontEnd.js:1640)
> at Function.ny [as googFireListener] (FrontEnd.js:123)
> at ny (FrontEnd.js:248)
> at HTMLAnchorElement.iy (FrontEnd.js:125)
> at HTMLAnchorElement.b (FrontEn

RE: Release compilation does not work: maven modules and crux

[Maria Jose Esteve]

On December 9, 2020 I compiled a release version that worked. It had much less 
code but the structure and mvc implementations using crux was the same.
I will do a first test with SDK 0.9.9 and the code at that time and if it gives 
error I will compile the SDK to that date.

Hiedra

De: Maria Jose Esteve 
Enviado el: viernes, 31 de diciembre de 2021 0:36
Para: users@royale.apache.org
Asunto: Release compilation does not work: maven modules and crux

Hi Greg, yes.
I did a production deployment over 6 months ago and it worked. I had in mind to 
look for "that point" in the repository and maybe it's already time... I don't 
usually give up, but I lack the knowledge to solve this, I'm bugging and 
bugging Harb and I've done 100 tests without success.

Right now I'm debugging App.js, as suggested by Harb, and what I've discovered 
so far is that "other models", also located in the modules [1] of my library, 
are loaded correctly (crux)

[1] I don't use modules like Roman, I use Maven modules and, like you, I have a 
hierarchy of pom's

Hiedra

De: Greg Dove mailto:greg.d...@gmail.com>>
Enviado el: jueves, 30 de diciembre de 2021 23:23
Para: users@royale.apache.org
Asunto: Re: Compiling Modules (was Re: Load time is very slow)


Sorry I have not been following these threads in detail because I have been 
(and am currently still) on vacation.
AFAIK royale modules are not reliable in release mode. I don't know anyone who 
has had experience otherwise. I did try testing them some time ago and that was 
my experience, and I believe we had similar feedback from others in the 
community (who were early users) that it was working for them in the debug 
build, but not the release build.

Perhaps it can work in very simple cases in release builds, but beyond that I 
think the work on them is not complete. If there are others in the community 
whose experience is different and can confirm that things are working for them 
in release builds, please let us know.

Maria, it is also possible that in your case, that use of Crux inside modules 
is another layer of complexity in release mode, because I did not test that 
when I did the original work on Crux. Was this working at some point in the 
past and it has now stopped working?




On Fri, Dec 31, 2021 at 11:10 AM Roman Isitua 
mailto:romanisi...@gmail.com>> wrote:
Yes.
On Thu, 30 Dec 2021, 23:03 Harbs, 
mailto:harbs.li...@gmail.com>> wrote:
Did you apply the input_file options to the module?

On Dec 30, 2021, at 11:42 PM, Roman Isitua 
mailto:romanisi...@gmail.com>> wrote:


I have applied the js compiler option as follows

-source-map=false;-compiler.show-binding-warnings=false;-js-default-initializers=true;-js-dynamic-access-unknown-members=true;
-js-compiler-option=--variable_map_output_file 
gccvars.txt;-js-compiler-option+=--property_map_output_file gccprops.txt
  


I get the same error as before when attempting to launch the jewel module.




Same error trace.

Uncaught TypeError: cm.valuesImpl.init is not a function
at Rr.Mr.yl (Overview.js:786)
at Function.iq.generateMXMLProperties (Overview.js:736)
at Rr.hq.generateMXMLAttributes (Overview.js:546)
at new Rr (Overview.js:804)
at LN.J.loadHandler (FrontEnd.js:1967)
FrontEnd.js:1640 Uncaught TypeError: M is not a function
at oM.J.handleMouseOut (FrontEnd.js:1640)
at Function.ny [as googFireListener] (FrontEnd.js:123)
at ny (FrontEnd.js:248)
at HTMLAnchorElement.iy (FrontEnd.js:125)
at HTMLAnchorElement.b (FrontEnd.js:121)
FrontEnd.js:1640 Uncaught TypeError: M is not a function
at oM.J.handleMouseOver (FrontEnd.js:1640)
at Function.ny [as googFireListener] (FrontEnd.js:123)
at ny (FrontEnd.js:248)
at HTMLAnchorElement.iy (FrontEnd.js:125)
at HTMLAnchorElement.b (FrontEnd.js:121)
FrontEnd.js:1640 Uncaught TypeError: M is not a function
at oM.J.handleMouseOut (FrontEnd.js:1640)
at Function.ny [as googFireListener] (FrontEnd.js:123)
at ny (FrontEnd.js:248)
at HTMLAnchorElement.iy (FrontEnd.js:125)
at HTMLAnchorElement.b (FrontEnd.js:121)
FrontEnd.js:1640 Uncaught TypeError: M is not a function
at oM.J.handleMouseOver (FrontEnd.js:1640)
at Function.ny [as googFireListener] (FrontEnd.js:123)
at ny (FrontEnd.js:248)
at HTMLAnchorElement.iy (FrontEnd.js:125)
at HTMLAnchorElement.b (FrontEnd.js:121)
FrontEnd.js:1640 Uncaught TypeError: M is not a function
at oM.J.handleMouseOut (FrontEnd.js:1640)
at Function.ny [as googFireListener] (FrontEnd.js:123)
at ny (FrontEnd.js:248)
at HTMLAnchorElement.iy (FrontEnd.js:125)
at HTMLAnchorElement.b (FrontEnd.js:121)
FrontEnd.js:1640 Uncaught TypeError: M is not a function
at oM.J.handleMouseOver (FrontEnd.js:1640)
at Function.ny [as googFireListener] (FrontEnd.js:123)
at ny (FrontEnd.js:248)
at HTMLAnchorElement.iy (FrontEnd.js:125)
at HTMLAnchorElement.b (FrontEnd.js:121)
FrontEnd.js:1640 U