Closed GoogleCodeExporter closed 8 years ago
I was able to reproduce the bug on Windows with several versions of Node.js.
Cause seems to be in ChromiumDebugPluginUtil.java, where the following regular
expression is used to sanitize a file name:
private static final Pattern FILE_NAME_BAD_CHARS = Pattern.compile("[?<>/]");
Suggested fix:
Change the regular expression to [^A-Za-z0-9]
This would replace all characters that are not alphanumerical.
Original comment by zirg...@gmail.com
on 25 Nov 2011 at 2:00
Zirgion, thank you for your help.
You are right about diagnose. However RegExp probably should allow full
alpha-number category to support non-english names, but that are details.
We are planning on releasing 0.3.2 with the patch soon.
Would you like also to try the quick 7k patch file "issue_53_patch.jar" that I
published in the mail group (see instructions)?
http://groups.google.com/group/chromedevtools-dev/browse_thread/thread/9e33db90e
fdbdc92
So that we have some report about whether it works "in the field".
Original comment by peter.ry...@gmail.com
on 25 Nov 2011 at 2:55
fixed in HEAD
Original comment by peter.ry...@gmail.com
on 6 Dec 2011 at 7:57
Hey Peter,
Do you know when this will be released ?
Thanks.
Original comment by lenin.ku...@gmail.com
on 7 Dec 2011 at 3:43
Hey Lenin,
Should be on update site in a week.
Peter
Original comment by peter.ry...@gmail.com
on 7 Dec 2011 at 7:34
Fixed in 0.3.2
Original comment by peter.ry...@gmail.com
on 13 Dec 2011 at 12:13
Original issue reported on code.google.com by
peter.ry...@gmail.com
on 23 Nov 2011 at 4:24