I found that hard to read, but I think I see on line 657 that js-output is set
to "." and that makes me wonder if the compiler will then choose whatever the
working directory is at the time it is launched. If that working directory is
changed by VSCode to be the last output directory (maybe to
Hi Alex,
>Right. The goal was to see what output options were actually being received
by the compiler in order to understand how those options could be causing
the compiler to generate nested output folders. I'm curious to know if the
js options are in the dump file. Can't tell since you cut
While investigating this issue I accidentally filed a bin folder (which
contains a build) within the source path.
This throws an error like "...not found on source path, using parent
file..." and delayed the build process for a significant couple of seconds.
After removing this accidentally
> See if the -dump-config= works
for JS. Not sure if it does, but it might help.
Creating a dump file works, but it seems to me that it rather contains a
config than errors which occur during the build [1].
[1]
true
Hey Piotr,
I'm moving this VSCode discussion about the ConcurrentModificationException
here:
https://github.com/BowlerHatLLC/vscode-as3mxml/issues/332
- Josh
On 2019/02/23 09:39:27, Piotr Zarzycki wrote:
> Hi Josh,
>
> This is what I'm getting having Win Antivirus ON [1]. Once it's occurs
Hi Olaf,
Exactly. I have in Moonshine exact path:
-js-output=D:\Work\projects\client\myapp
And it doesn't occur.
Thanks,
Piotr
pon., 25 lut 2019 o 10:28 Olaf Krueger napisał(a):
> > What happen if you put in js-output - real path instead "." - one dot ?
>
> Same behavior!
>
> Does that mean
See if the -dump-config= works for
JS. Not sure if it does, but it might help.
HTH,
-Alex
On 2/25/19, 1:28 AM, "Olaf Krueger" wrote:
> What happen if you put in js-output - real path instead "." - one dot ?
Same behavior!
Does that mean that you can't reproduce this
> What happen if you put in js-output - real path instead "." - one dot ?
Same behavior!
Does that mean that you can't reproduce this issue at your side?
Olaf
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
Hi Guys,
What happen if you put in js-output - real path instead "." - one dot ?
Thanks,
Piotr
pon., 25 lut 2019 o 09:57 Olaf Krueger napisał(a):
> Good catch Yishay, I found a similar issue at my side [1].
> But it seems to me that in my case just "bin/js-debug/bin/js-debug/..." is
>
Good catch Yishay, I found a similar issue at my side [1].
But it seems to me that in my case just "bin/js-debug/bin/js-debug/..." is
affected and created recursively.
Olaf
[1]
https://snag.gy/q8y4G2.jpg
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
But it still created nested folders n deep.
From: Yishay Weiss
Sent: Monday, February 25, 2019 10:40:54 AM
To: dev@royale.apache.org
Subject: RE: VSCode Build Taking Really Long
It looks that way. I manually removed all bin folders from the old repo clone
It looks that way. I manually removed all bin folders from the old repo clone
and it’s now much faster.
From: Olaf Krueger
Sent: Monday, February 25, 2019 10:28:03 AM
To: dev@royale.apache.org
Subject: RE: VSCode Build Taking Really Long
That means
That means that cleaning the build folder would have been enough in your
case, instead of re-cloning the repo, right?
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
"files":
[
"src/com/edscha/ebaseforms/shell/view/royale/Shell.mxml"
]
[1] https://paste.apache.org/sdgg
From: Yishay Weiss
Sent: Sunday, February 24, 2019 9:00:15 PM
To: dev@royale.apache.org
Subject: RE: VSCode Build
, February 23, 2019 11:18:57 PM
To: dev@royale.apache.org
Subject: RE: VSCode Build Taking Really Long
Is there a verbose mode for running asconfigc?
From: Yishay Weiss
Sent: Saturday, February 23, 2019 10:56:16 PM
To: dev@royale.apache.org
Subject: RE: VSCode
Is there a verbose mode for running asconfigc?
From: Yishay Weiss
Sent: Saturday, February 23, 2019 10:56:16 PM
To: dev@royale.apache.org
Subject: RE: VSCode Build Taking Really Long
CPU rarely goes over 20% and never over 57%. Turning real-time protection off
CPU rarely goes over 20% and never over 57%. Turning real-time protection off
didn’t make a big difference.
From: Josh Tynjala
Sent: Friday, February 22, 2019 7:40:45 PM
To: dev@royale.apache.org
Subject: Re: VSCode Build Taking Really Long
The fact
Hi Josh,
This is what I'm getting having Win Antivirus ON [1]. Once it's occurs
usage of extension is pointless. Everything is freezing, any rollover on
component or as3 mxml is causing output in console. - Maybe it's related to
the slowness in case of Yishay.
Yishay did you try switch OFF real
Piotr,
What happens when it crashes? Are there specific errors or stack traces that I
could possibly investigate?
- Josh
On 2019/02/22 18:01:05, Piotr Zarzycki wrote:
> Josh,
>
> In that case I need to say that internal Antivirus in Windows is making my
> life harder in case Moonshine usage
Josh,
In that case I need to say that internal Antivirus in Windows is making my
life harder in case Moonshine usage for a long time.
Maybe problems which Yishay experiencing is connecting to that.
Basically when antivirus/firewall is On Windows I'm getting constant
crashes of extension after
The fact that you're all on Windows and are using the same versions of all of
the development tools makes me think that it might be something else in your
environment. Like maybe a malware scanner or something else that might be
watching the file system?
It might be worth opening up the task
put [1]
>
>
>
> [1] https://paste.apache.org/wXhr
>
>
>
>
> From: Harbs
> Sent: Thursday, February 21, 2019 5:44:22 PM
> To: dev@royale.apache.org
> Subject: Re: VSCode Build Taking Really Long
>
> What are you using to co
Subject: Re: VSCode Build Taking Really Long
What are you using to compile?
If you’re compiling using the VS Code extension, try installing asconfigc
separately.
> On Feb 21, 2019, at 4:29 PM, Yishay Weiss wrote:
>
> Hi Guys,
>
> We have a really simple app which takes Piotr and Olaf
What are you using to compile?
If you’re compiling using the VS Code extension, try installing asconfigc
separately.
> On Feb 21, 2019, at 4:29 PM, Yishay Weiss wrote:
>
> Hi Guys,
>
> We have a really simple app which takes Piotr and Olaf less than half a
> minute to compile using VSCode.
24 matches
Mail list logo
