search : parser

select a category, or use search below
(searches all categories and all time range)

displaying top 100 results

Tracker Issue Parser glitch on `+=`
Parser glitch on `+=`
Parser bug in function with typo in it
Bug 82775:When doing a cached FTP, then checking for an EXISTSFILE, returns the error Parser key cannot by null
2612578 CF-3496254 Rupesh K. It is not as easy as REGEX. It is a JavaCC based SQL parser. Unless it is absolutely critical, which I don't see in this case, there is not much value in changing the parser.
2682660 CFB-3781535 Ram K. We use Rhino parser. But expression in ## is not a valid JS syntax, so the JS parser is doing the correct thing by throwing syntax error.
2611687 CF-3600686 Awdhesh K. This need risky change in language parser. Will take up later.
Comment on The parser / compiler falsely identifies methods as operators. by Aaron N.
element list (zingchart-rhino.min.js#8(eval)#1) at org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3785) at org.mozilla.javascript.DefaultErrorReporter.error(DefaultErrorReporter.java:89) at org.mozilla.javascript.Parser.addError(Parser.java:230) at org.mozilla.javascript.Parser.addError(Parser
Comment on The parser / compiler falsely identifies methods as operators. by John W.
2596894 CF-3498448 Rupesh K. This is how loggers are designed. CRLF is stripped from messages so that the log parsers can work without any issues.
2613487 CF-3307400 Rupesh K. This is a bug with the JSON parser that we use. This is also a very edge case.
Comment on The parser / compiler falsely identifies methods as operators. by John W.
2682660 CFB-3781535 External U. Which 3rd Party JS Parser do I need to submit this bug to then?
2682686 CFB-3758872 extuser Code coloring is really, really bad. HTML comments seem to really interfere with the parser. It's almost unusable.
Comment on The parser / compiler falsely identifies methods as operators. by John W.
2608368 CF-4110354 External U. Should be handled. All operators should be... including > which one might think would confuse the parser (given it's also the character for the end of a tag, but the parser should be cleaver enough to understand the context of the usage. That said, not sure
2611757 CF-3595245 External U. The fact that this crashes shows an inconsistency in the parser. Code that normally runs but doesn't when preceeded by certain constructs is strange and hard to avoid. Furthermore, crashes within the parser do not indicate where the line failed, which makes
2596977 CF-3231457 Awdhesh K. This is an edge case where parser breaks while parsing a method chain where one of the function name is one of the ColdFusion special keys like is, contains, EQ etc. Making required changes in the parser at this moment would be bit risky.
2682653 CFB-3787600 External U. I've looked at this file in both the CFML and HTML Editor the HTML editor is ok, but i the CFML Editor it is all green as noted. It would seem line 15 is throughing the parser, removing the ! in the second to become fixes the file. Engineering team, I'd hope
2596827 CF-3616590 External U. Remember that everything was tag-based original and so string interpolation used the expression parser from the tag-based world, along with cfset and cfif etc so everything was consistent. cfscript is essentially a whole separate parser but clearly reuses
page. Errors on that page and in logs refer to Solr service failing to start. Errors seen include: "Error","localhost-startStop-1","11/02/16","11:55:26",,"Unable to initialise Solr service: java.lang.NoClassDefFoundError: org/apache/tika/parser/Parser" "Error","localhost-startStop-1
The parser will throw exception if closure used with arguments in a new object creation syntax
The parser / compiler falsely identifies methods as operators.
Glitch in CFML parser for writeDump() / writeLog() / throw()
Comment on org.eclipse.jetty.http.HttpParser$IllegalCharacterException causing high CPU usage by Chad M.
2879837 CF-4198362 Nitin K. Fixed in CF2018 As it involves parser level changes, we have taken the fix in the next release of ColdFusion(Aether) 
Comment on The parser / compiler falsely identifies methods as operators. by John W.
Comment on The parser / compiler falsely identifies methods as operators. by Doug C.
2608442 CF-4093045 Awdhesh K. Need to change the core of CF which involves parser and code generation. Its little bit risky to make changes now. will take it up later.
2608724 CF-4016861 External U. We lose embedded files regularly. Had to write our own mail parser to work around it but would prefer a fix
2609771 CF-3777403 External U. I'm seeing this too. It's a parser bug by the looks of it, as this variation works fine: #time#: #TimeFormat(time, "hh:mm:ss")# (#dateadd("s", 0, time)#) -- Adam
2611035 CF-3648781 Rupesh K. Thank you everyone for pitching in. It definitely makes sense and we should fix it. We investigated this and it does require a fundamental change in the parser as Sean already pointed out. Deferring it to the next release.
2596827 CF-3616590 External U. ACF does not accept cfscript expressions inside #..# in tag-based code. It has two expression parsers: one for tag-based code expressions, and one for cfscript. Pretty sure .. will not work either, for exactly the same reason.
2612779 CF-3430402 External U. I tried the same with a Livecycle pdf form which ended with an error message of "Parser configuration problem: namespace reporting is not enabled" Again - on windows this was successful
2613914 CF-3148699 Rupesh K. This requires parser changes, which is too risky to be taken up at this stage.
2598381 CF-3041399 Adam C. The parser should be able to distinguish between the usage in a function signature and a switch statement. Plus if it works in tags, it should work in script.
2682632 CFB-3803692 External U. There are, of course, various things to fix this specific code example (e.g. move the css to a .css file). However the root problem is that the syntax parser is not properly recognizing # escaping inside cfoutput, which it should.
2682660 CFB-3781535 Adobe D. JavaScript is parsed by a third-party JS parser and it throws error for invalid JS syntax. (Comment added from ex-user id:dsarkar)
2682663 CFB-3779414 Adobe D. JavaScript is parsed by a third-party JS parser. It flags error for tag ot # in script block. (Comment added from ex-user id:dsarkar)
2682666 CFB-3775884 extuser Is this every going to get fixed? I can't turn off the XML parser, and this error effectively makes the builder useless for developing CFM pages.
2682729 CFB-3737552 Adobe D. Snigdha log a separate bug for parser error. Test this bug with proper server.xml and close it. (Comment added from ex-user id:kartik)
Comment on The parser will throw exception if closure used with arguments in a new object creation syntax by Luis M.
Comment on The parser will throw exception if closure used with arguments in a new object creation syntax by Suchika S.
2611035 CF-3648781 Rupesh K. I did not talk about any blocker so far. I am questioning whether this syntax can cause confusion and whether this is really required given that more and more code is being written in script only. Yes, the CFML parser does run in two modes - one for tag and another one
4901051 CF-4203360 Core Runtime Any Servlet filter that doesn't have the pattern attribute causes startup to fail Problem Description: If a Tomcat valve is added to server.xml (such as mod_cfml) and it lacks the attribute "pattern", Coldfusion will fail on startup with on ServerConfigParser.fixAttribute(ServerConfigParser
2608716 CF-4018933 Milan C. Our team try to actively find any possible language bugs, so that is a continuous process. In this bug, valueList was reported as an example. We found that valueList had a special handling from our parser so it was breaking. As part of our fix we found that same check
3707850 CF-4200150 Core Runtime : Parser/Compiler Edward Keighley Context validation error for cfcase Problem Description: An implicit array inside a tag appears to cause a compiler exception in an unrelated tag, but only if there are enough other variable references within the same script
3581064 CF-4199987 Ashudeep S. Yeah i know this is an issue with chaining kind of syntax in our parser.This will be a problem with any reserved keywords being used at the second and subsequent levels during function chaining and we are going to fix it.
Comment on org.eclipse.jetty.http.HttpParser$IllegalCharacterException causing high CPU usage by Chad M.
Comment on org.eclipse.jetty.http.HttpParser$IllegalCharacterException causing high CPU usage by Piyush K.
2609222 CF-3909707 External U. Yep, you are right. The entire issue was that I did: x = cfwddx(action="cfml2wddx", input="something") the x= must have confused the parser. I do think the error should have been clearer though. At worst, shouldn't it have worked, but X simply be undefined?
2609712 CF-3796626 Adobe D. Added new attribute parserKey to cfftp tag which when given the value "unix" or "windows" does not trigger SYST command and CFFTP ListDir works fine even if SYST command is disabled in the FTP server. (Comment added from ex-user id:nawani)
2609712 CF-3796626 External U. Filed #CF-3849151 to rename the "parserkey" attribute to "systemtype", since that's what the attribute is asking for: the "system type". That matches the JVM property: org.apache.commons.net.ftp.systemType ("system type" not "parser key") Thanks!, -Aaron
2610249 CF-3714942 External U. In itself this isn't a big issue. I'm reporting it because it represents what I suspect is a larger class of errors where the cfscript parser masks underlying syntax errors.
2596827 CF-3616590 External U. Interpolated strings are (treated as) tag-based code. Like I said: two expression parsers - one created for tag-based code that is used for expressions in cfset, cfif, interpolated strings etc - and one created for cfscript-based code.
2612578 CF-3496254 External U. It's obviously not critical. But, I have reworked queries to QofQ in the past and got bit because they had comments. I figured it was a simple matter of you stripping them out *before* you hand the string of SQL to the JavaCC SQL Parser.
2613550 CF-3239392 External U. New Solution!!! DirectoryIndex dex index.html ... should have been ... DirectoryIndex index.cfm index.html Looks as if the parser used to modify httpd.conf in the install is making some mistakes. and the x in the php module shouldn't be there at all
2682283 CFB-4130080 Milan C. being parser fix, need to test it thoroughly with lot of files. just opening the files and checking for the errors shown in red in file(should be consistent with earlier builds) should be OK. no need to test other features but to test a lot of applications and files.
2682312 CFB-4121980 Milan C. being parser fix, need to test it thoroughly with lot of files. just opening the files and checking for the errors shown in red in file(should be consistent with earlier builds) should be OK. no need to test other features but to test a lot of applications and files
Comment on The parser will throw exception if closure used with arguments in a new object creation syntax by Suchika S.
Comment on The parser will throw exception if closure used with arguments in a new object creation syntax by Suchika S.
Comment on The parser will throw exception if closure used with arguments in a new object creation syntax by Suchika S.
Comment on The parser / compiler falsely identifies methods as operators. by Aaron N.
2609172 CF-3916195 Net Protocols : FTP Chris Morbitzer CFFTP not working, CF10 Update 15 Problem Description: We updated our CF10 installation to Update 15 and now our cfftp tags are throwing the error: "The tag handler ftp does not have a setter for the attribute parserKey specified in the Tag
3349643 CF-4199409 CFComponent Luis Majano Metadata not trimmed on comment based annotations Problem Description: If you use comment based annotations and and spacing or tabs to align them, the parser will not trim the selections and the data is lost. Steps to Reproduce: {code
| 2| myList = "a,b,c"; (x)3| myList.listEach(function(element) {}); 4| //a comment 5| //another comment Actual Result: Syntax error on line 3. - Line 3's syntax error message is: "com.adobe.editor.cfml.parser.generated.ASTcfcomment cannot be cast to com.adobe.editor.cfml.parser
that the ColdFusion code parser is split into two different "systems": one for tags and one for script, so compiling a statement that has elements from both the tag lexicon and the script lexicon will require not insubstantial re-engineering on your part? And Railo doesn't suffer from this as they approach code
org.eclipse.jetty.http.HttpParser$IllegalCharacterException causing high CPU usage
4768365 CF-4203301 Core Runtime : Parser/Compiler Struct and Array Literals in parenthesis cannot be returned. Problem: Any expression(s) should be able to be wrapped in parenthesis (to either aid in order of operands or not) however simply trying to compile "return ([]);" or "return ({});" throws
5485904 CF-4204099 Core Runtime : Parser/Compiler Struct Member Function is invalid construct Problem Description: I som situations I want to find out how some code was called. I use function callStackGet and loop through the result. ColdFusion throws an exception. Steps to Reproduce: {code
2596827 CF-3616590 External U. Why would strings - which cannot possibly have tags in them - use the tag-version of the parser? That's not me disagreeing, I completely believe you: it's just general derision. Its a CFML expression, and how it is parsed should be tag/script agnostic, given
2612578 CF-3496254 External U. Adam, I understand what you're saying about it being the responsibility of the SQL engine to deal with the comments. Rupesh, is the "JavaCC SQL Parser" you mention a third party product? Can I submit a ticket for their SQL engine to handle ANSI SQL comments? Again
Comment on The parser / compiler falsely identifies methods as operators. by John W.
.adobe.coldfusion.bootstrap.Bootstrap.main(Bootstrap.java:161) Caused by: java.lang.NoSuchMethodError: org.apache.jasper.xmlparser.ParserUtils.(Z)V at com.adobe.coldfusion.launcher.ServerConfigParser.parse(ServerConfigParser.java:55) at com.adobe.coldfusion.launcher.Launcher.run(Launcher.java:193) ... 6 more Expected: After upgrade
or uploadall Actual Result: error message llegal char StackTrace java.nio.file.InvalidPathException: Illegal char at index 39: d:\wwwroot\uploads\news\documents\?.txt" at sun.nio.fs.WindowsPathParser.normalize(Unknown Source) at sun.nio.fs.WindowsPathParser.parse(Unknown Source) at sun.nio.fs.WindowsPathParser
Result: Successful error-free validation Any Workarounds: the following Java-based code try { /*Set up XML parser*/ documentBuilderFactoryInstance = createobject("java","javax.xml.parsers.DocumentBuilderFactory").newInstance(); /* Specify that the parser produced by this code provide support
, when runing Axis2 from inside CF10, Adobe injects their own version of CodeGeneratorEngine into Axis (called CFCodeGeneratorEngine ). it appears that they're doing it for performance reasons. You see, earlier in the CreateObject() process, CF10 has already used Apache HttpClient and a sax parser
.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:145) ~[groovy-2.3.9.jar:2.3.9] at com.predic8.xml.util.ExternalResolver.resolve(ExternalResolver.groovy:80) ~[soa-model-core-1.5.4.jar:?] at com.adobe.amp.soapproxy.ApiManagerWsdlParser.getResourceToken(ApiManagerWsdlParser.java:45) ~[apim-soapproxy.jar:?] at com.adobe.amp.soapproxy.ApiManagerWsdlParser.parsex(ApiManagerWsdlParser
parsed by XML parsers. Steps to Reproduce: Run a missing REST function Actual Result: non-XML structure text "Not Found" Expected Result: Valid XML with error message, customizable by us. Any Workarounds: None. ----------------------------- Additional Watson Details
anything WHERE email = ? ] Any Workarounds: Removing the offending single-quote works, but the parser *worked* in CF11.
2608442 CF-4093045 External U. "Need to change the core of CF which involves parser and code generation" There is not need for that. The only thing you need to do is to move those 'private' methods out of that page. There are several well defined patterns to do these kinds of changes
) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228) at org
're reading the situation wrong, Chris... SQL-style comments are the remit of the SQL parser to remove. *CFML* comment I could understand being extracted before the SQL string was passed to the SQL engine. In a moment the date and time of which should be noted down... I agree with Rupesh here. -- Adam
Comment on The parser / compiler falsely identifies methods as operators. by Aaron N.
Bug with parameter parser in Query.cfc
2598218 CF-3041607 Language : Tags Phil Haeusler Bug 83185:CFFTP unable to connect to WFTPD FTP server Problem: CFFTP unable to connect to WFTPD FTP server. Attempting to connect to a WFTPD server using CFFTP returns an internal CF exception. Unknown parser type: WIN32 A N (WFTPD by Texas
2608130 CF-4185061 Text Search : Solr Aaron Neff [ANeff] Bug for: cfsearch type is case-sensitive cfsearch type is case-sensitive Doc description for cfsearch's type attribute is: ----------- Specifies the parser that the engine uses to process the criteria. Standard Dis
2608169 CF-4173282 Core Runtime : Parser/Compiler Henry Ho Trusted cache does not eliminate all file io checking Problem Description: With trusted cache enabled, one would expect it to not stress the disk io as much but CPU snapshot in VisualVM tells us that if cfinterface is used, or if a cfc
2608778 CF-4000264 Database Peter Boughton QueryExecute when ? and = in string - "Lesser number (0) of positional parameters are defined for sql query" Problem Description: QueryExecute has a buggy SQL parser - it thinks a URL inside a string is a positional parameter. The presence of a question
with the other two I mentioned. It seems to be related to the functions which take name/value pairs for arguments. The parser doesn't seem to "understand" them in some (completely valid) situations. -- Adam ----------------------------- Additional Watson Details ----------------------------- Watson Bug ID