Having an issue where time is not correct when inserting into mysql. My Lucee server is set to EST & showing correct time. MySQL database is showing correct EST when select now(); I've tried with both timestamp and datetime fields and the time is off 4 hours when the insert happens using createdAt = now(); Anyone have a clue what I could be missing?

I'm having an issue where I assign a variable from an XML node. I can cfoutput the variable I only get the value which seems correct. If I use cfdump on the variable I only get the value, which seems correct. If I use ISXML(value) on the value in a CFdump, it returns true! Which seems to be a problem. If I use the variable in a query, the query fails and there is XML in the query statement that I didn't put there. Here is the SQL revealed in the error: Select full_name from qryClients where client_number="<?xml version="1.0" encoding="UTF-8"?><ClientSourceRecordIdentifier>9302045948</ClientSourceRecordIdentifier>" Is there a way to clean this XML cruft out of the variable? The variable by itself is supposed to be 9302045948.

Howdy folks... can someone provide information on how to actually use LUCEE_ENABLE_WARMUP environment variable, with regards to "typical" workflow? I have a Lucee app/docker that is having issues when deployed to a relatively high traffic kubernetes environment, and the application is using ColdSpring/FW1. Our most recent deployment saw three containers start up, and one of them started spewing an error on every request, that certain classes were "not found" when referenced by EntityNew(), etc. even though the components were in the directories for the ORM/ColdSpring to find. The assumption here is that the server needs to be warmed up first, before it gets hammered with that traffic. So i started working on it this morning. When I build the image locally, i had env variable LUCEE_ENABLE_WARMUP set to true, but when I ran the image with that set, it starts up and then shuts down. When I set it back to false and ran the same image without (re)building it, it starts up and runs fine, but I don't notice any improvement in time-to-first-request/response, so I can't really tell if the setting is doing what it should. There's not much about this var in the documentation, so I'm just not sure how it should be used. TIA for any info!

just updated the docs with information about using

configImport()

with the

Web.cfc

and

Server.cfc

startup listeners, best tried with 5.3.10.84-SNAPSHOT https://docs.lucee.org/guides/cookbooks/Startup_Listeners.html

Also, we have a new beta for the image extension https://dev.lucee.org/t/image-extension-2-0-0-16-beta/11293

Yo. Any reason why on some of our Lucee instances the

cf_session_data

table is created as:

CREATE TABLE `cf_session_data` (
  `expires` varchar(64) NOT NULL,
  `cfid` varchar(64) NOT NULL,
  `name` varchar(255) NOT NULL,
  `data` longtext NOT NULL,
  UNIQUE KEY `ix_cf_session_data` (`cfid`,`name`,`expires`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;

And on others:

CREATE TABLE `cf_session_data` (
  `expires` varchar(64) NOT NULL,
  `cfid` varchar(64) NOT NULL,
  `name` varchar(255) NOT NULL,
  `data` longtext NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

All are MySQL 8, Lucee 5.3.9.160. One difference is that the ones that have the KEY are driven by a commandbox docker image, the others are just driven by the standard lucee docker image. I can't think why that would matter though? I'm not so worried about the charset/collation stuff, but I am concerned about the lack of unique key. I have found this: https://docs.lucee.org/guides/Various/FAQs/technical-FAQs/database-session.html#tip-manually-check-cf_session_data-table-for, but that alludes to how the table might not be set up properly, rather than why it might not be set up properly. Other googling only turned up with the same issue; no actual answers.

G'Day all... I have a strange issue with cfmail and email attachments... If the name of an email attachment contains enough diacritical characters then when the email is delivered the attachment filename will be corrupted. For example 'ThêQuickBrownFoxJúmpsOverTheDog.docx' is fine but 'ThêQuickBrøwnFoxJúmpsOverTheDog.docx' results in a file name resembling '=UTF-8QTh=C3=AAQuickBr=C3=B8wnFoxJ=C3=BAmpsOverTheDog.docx='. I'm guessing this is an issue with the length of the filename and handling of utf-8 characters because even a relatively short name like 'ThêQúickƁrøwñƑøx.docx' is corrupted into '=UTF-8QTh=C3=AAQ=C3=BAick=C6=81r=C3=B8w=C3=B1=C6=91=C3=B8x.docx='. The same files sent via Gmail to the same recipient are delivered with the filenames as you would expect. I'm thinking this is a Lucee bug but thought I would check here in case someone has seen this before (I couldn't find it in the backlog). Tested on 5.3.10.79-RC and 5.3.9.141 - and yes, I have the charset attribute set to 'utf-8'

Just released! 5.3.9.166 Stable https://dev.lucee.org/t/lucee-5-3-9-165-stable-release/11319

Lucee code parsing bug here it seems: https://trycf.com/gist/3024664fd918d90d8932a4e68fd28e60/lucee5?theme=monokai

st = {}

[
	"tahi",
	"rua",
	"toru",
	"wha"
].each((n) => writeOutput(n))

Errors with:

Invalid Syntax Closing []] not found on line 5

st = {}; // <--- say hello to my little friend

[
	"tahi",
	"rua",
	"toru",
	"wha"
].each((n) => writeOutput(n))

Works fine 😐

I have updated the lucee github actions to list failed test cases up front and center on the Github Actions Summary page https://luceeserver.atlassian.net/browse/LDEV-4252

Very broad question here. These days, how much memory do you allocate to a Docker container running Lucee (from the official image) for a low traffic web app? I've just found out we're allocating "only"(?) 4GB between three instances of our app on the same VPS... medium, low and very low traffic respectively.

It seems like now there is only two people working on Lucee. My prs are no longer being merged in and have sat there for months and months. That is the main reason I stopped working on Lucee and I am sure most of the community can see this

Probable Lucee bug with

isObject

& `isValid`: https://trycf.com/gist/68714a07fd05f75f9edb7c05b7db0a47/lucee5?setupCodeGistId=816ce84fd991c2682df612dbaf1cad11&amp;theme=monokai Compare behaviours of CF's baseline expectations, and Lucee. Lucee's behaviour is inconsistent with CF's, and also internally inconsistent. Or am I missing something?

If I get an exception in a scheduled task that calls a page in my app: 1. the exception is only logged in the server context application log 2. it does not fire my onError handler in app.cfc 3. Fusion reactor shows 2 entries in transaction error history a. 1 with an app/txn name of 'MyApplication' - literally - that is not what my app is called 😉 b. 1 with a app/txn name of ROOT - also not what my app is called. Is this what is expected? I assume the lucee scheduler runs everything in some special process that bypasses the normal event handlers. running 5.3.9.160. Thanks

5.3.9.166 is available via maven https://mvnrepository.com/artifact/org.lucee/lucee/5.3.9.166

Curious if there a setting for Lucee to output error messages with the variable name as it is in the code, i.e. camelCase - while “niceLocation” vs “NICELOCATION” might seem trivial enough, In one application I require many variables which kind of need to sound similar as they iterate on similar values, leading to rather long variable names (may not be ideal, but that’s beside the point here - it helps others/clients understand what is happening in the code). So when Lucee 'shouts' back [UPSSYSTEMRUNTIMEINCLUDINGAGEINGRESERVEINMINUTESONLY] doesn’t exist”, it takes my old brain a bit longer to read it than if it were to show “upsSystemRuntimeIncludingAgeingReserveInMinutesOnly”. Cheers!

Hi. I'm trying to download file by CFHTTP Lucee 5.3.9.166. Web-server response has header "Content-Type: application/pdf;charset=binary" and I get "Lucee 5.3.9.166 Error (java.nio.charset.UnsupportedCharsetException) Message: binary". ACF works fine with the same code. If web-server doesn't return "charset=binary" it works fine. Any ideas how to fix it?

so @garciadev let's figure out this one? https://cfml.slack.com/archives/C06TA0A9W/p1667921083984159?thread_ts=1667914889.808289&amp;cid=C06TA0A9W

Heads-up: we pushed our prod env from 5.3.9.160 to 5.3.9.166 today and it went smoothly and seems to have solved the

org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for servlet [CFMLServlet] in context with path [] threw exception [null] with root cause

thing that was flooding the logs.

Any reason this is not just a bug in Lucee?

i=1
do {
    x = randRange(1,10)
    if (x > 5) {
        continue
    }
    writeOutput(x)
} while(++i <= 10)

Syntax Error, Invalid Construct

If one puts a semi-colon after the

continue

, it works. It works as one would expect on CF. https://trycf.com/gist/063a476b5ab7d0e67300fab8e2e55802/lucee5?theme=monokai Looks to me like it doesn't occur to Lucee that

}

can be considered the end of the previous statement, as much as

;

could be. I thought this had been raised previously, but didn't find anything in Jira. I might have been thinking of another situation where behaviour is similarly bung/unexpected. I def know I raised a ticket about

break

, but I was wrong with that one cos there was some legit uncertainty about whether or not the statement had ended with that one.

hi, is it possible to dynamically change the root of lucee using application.cfc? I have thought of this solution, but not so if it is the best way ...

// application.cfc
component {

  if( cookie.keyExists("snapshot") && cookie.snapshot.len() ){
    this.root = getDirectoryFromPath( getCurrentTemplatePath() );
    this.mappings["/"] = this.root & "../" & cookie.snapshot;
  }
  
  // ...
  
}

Also, I don't know how to deal with static assets (css/js/images) because those mapped in the application.cfc are not called

Hi there, I am going through a spectacularly large component that has spectacularly large and complex functions. I would just love to document the whole thing as

"Dragons live here : do not EVER consider editing or even trying to understand anything in here."

But of course this isn't helpful for anyone. The CFC is entirely cfscript. (Side quest : is there a way to display a literal AT symbol in slack - Eg. AT:hint complains about having multiple possible matches?) Now, I know I can create anything I like as an annotation,

@mybullshitannotation this is some some text

However - I can't seem to find a list of the ones that I can use that have a "special" meaning. That is - is there a list that would contain

returnFormat, returnType, hint, etc

Or is simply a one-to-one for the tag attributes from the cffunction docs here? Are there any differences? Are they documented anywhere? - if not I feel a doc PR coming along. More specifically - to my current need - how do I annotate an argument in cfscript? I know that the following provides the "hint";

@argumentOne This a hint

But... how do I annotate for; the datatype of the argument? if it is required? or is Just "free text" for arguments as a result of Lucee treating annotations differently to ACF (Lucee believes an annotation is just a comment and should not effect code operation , (which I like BTW). So it would seem nonsensical to have special handling of argument attributes in annotations? I don't mind, either way - I just can't find anything specifically about it in the docs. As always thanks!

XMLValidate error with valid xml https://luceeserver.atlassian.net/browse/LDEV-2909 has been fixed in 5.3.9.169 and 5.3.10.92

Logs being written out to the wrong context https://luceeserver.atlassian.net/browse/LDEV-4263 has been fixed in 5.3.9.170

NPE in CFMLFactoryImpl.getPageContextImpl https://luceeserver.atlassian.net/browse/LDEV-4162 has been backported to 5.3.8.232

NPE PageContextImpl.java:574 - parallel processing, i.e. each() etc https://luceeserver.atlassian.net/browse/LDEV-4204 has been backported to 5.3.8.231

Hey - latest MS Sql Server extension is - 9.4.1.jre16. I assume I don't need JRE 16 installed somewhere for it to use, right, since Lucee doesn't support 16, IDT? thanks!