Lucee6 challenges, cont'ed Getting another error on a static property with 6, over and above the one we were getting on 5.3.10 Conclusion: hard pass. (And, sorry, replicating these static issues take ages to extract a repro case, and I just... can't be arsed, sorry) This time it's not finding a static variable that is unconditionally set in a CFC. It's there. It's always there. Just... Lucee is losing the plot somehow. I have this sort of thing:

<cfcomponent extends="Parent">

	<cfscript>
		static {
			final static.MY_CONST = 3
		}
	</cfscript>
	<!--- ... etc, rest of file --->
</cfcomponent>

And Lucee is going:

Error executing bundle - test.path.to.MyTest message: The static member [MY_CONST] does not exist in the Component [<http://path.to.My|path.to.My>]

It's simply not true. It's there. It's always there. I recommend you guys add a lot of test cases around static support.

Hi Guys Do you know where all the Server Admin settings are stored. Are they put into a MySQL DB, somewhere? The reason I ask , is because we have 600 DSNs which I have successfully imported using:

ConfigImport()

The problem is, it doesn't seem to record any of these settings:

"allowAlter":true,
"allowCreate":true,
"allowDelete":true,
"allowDrop":true,
"allowGrant":false,
"allowInsert":true,
"allowRevoke":false,
"allowSelect":true,
"allowStoredProcs":true,
"allowUpdate":true,

All these settings are TRUE in the Server Admin I want to go into the DB and change them. I don't fancy having to manually change 600 DSNs manually across 6 PRE PROD/PROD boxes. UPDATE: I have actually found the DSNs in:

lucee-server.xml

But, there are no Allowed Operations attributes in the

<data-source>

node? And when we run some of the databases, the connections fail. After we manually set REVOKE/GRANT to FALSE, the connections succeed. It seems that by default, all these operations are set to TRUE, which doesn't seem to agree with: https://github.com/lucee/Lucee/blob/3a563f215bc6060f0410a36099f5310300f0cf75/core/[…]c/main/java/resource/component/org/lucee/cfml/Administrator.cfc When I manually change the values of REVOKE/GRANT in the Lucee Server Admin to FALSE, and I check the XML in:

lucee-server.xml

There is no mention of REVOKE/GRANT anywhere? So Lucee must be storing this data in a Database somewhere?

Is the 90 day slack search limit tied to the workspace plan of each individual's plan? Might have to pay if it's per user. Assume we don't send these messages off programmatically to a dev.lucee.org forum channel - can't see them (guess might be against slack TOS). Often great stuff on here I wish I'd saved.

Behaviour change in 6.0.0.393-SNAPSHOT (cf Lucee 5)

<cfscript>
startTime = parseDateTime("2022-01-02 03:04:05", "yyyy-mm-dd HH:nn:ss", "Europe/London")
upTime = startTime.diff("s", now())

writeDump([
    startTime = startTime,
    upTime = upTime
])
</cfscript>

https://trycf.com/gist/74e8f4b5563e90f56a81d411d02e332f/lucee6-beta?theme=monokai Lucee 5: the diff is positive, eg: 43246273 Lucee 6: the diff is negative, eg: -43246306 Actually it's probably this: https://luceeserver.atlassian.net/browse/LDEV-2044 ? So a bug fix.

I added a bookmark here to the #lucee channel archive on Linen (which provides a searchable archive of this whole Slack).

Aaand... other than the new static issue (still can't derive a repro for that), and that change to

.diff()

, all our tests pass on Lucee 6. cc @alexpixl8

Can someone pls run this on Lucee 6.0.0.393-SNAPSHOT https://trycf.com/gist/a33d9f3b4336eee2a2dff80c0e5205ec/lucee6-beta?theme=monokai

<cfscript>
	function pow(o1, o2) {
		return o1 ^ o2;
	}


writeOutput(pow(2,-1))
</cfscript>

I am getting: lucee.runtime.exp.NativeException: Invalid operation at java.base/java.math.BigDecimal.pow(Unknown Source)

I'm using

sessionCluster=true

on a production app that has three Lucee instances all running 5.3.10.120. Very rarely, but seemingly in the same situations, a session variable only persists on the instance it was set on, meaning the session data is inconsistent across instances. The situation(s) in question I believe all involve a redirect (using ColdBox's

relocate()

) after setting the session variable. Is this is a known issue? Is there some sort of session flush I need to execute before the relocation?

Hi all! I recently updated the docker image (commandbox:jdk11-3.7.4) and lucee version (lucee@5.3.10+120) I'm using for my app and just realized that, now, every single query is being logged to

/usr/local/lib/serverHome/WEB-INF/lucee-web/datasource.log

. (Severity = "INFO" where before it was "ERROR") I'm not sure if updating the docker image had anything to do with it but it doesn't look like I changed anything in the code; figured this might be a LogBox setting in my Coldbox.cfc but nothing's jumping out at me. Where should I look?

Good morning cfml'ers I'm doing some maintenance on an old site, adding a small fw1 app for a new feature. site is running on luce 5.3.10 + fw1 4.3, and i'm hitting something odd, which i'm hoping is just me just not remember variable scoping in cfml correctly. so the following code is in a fw1 view,

<cfscript>
if(structKeyExists(rc, "myvalue")) {
    dump(rc.myvalue);
    function test() {
        return rc;
    }
    try {
        test();
    }
    catch(any e) {
        dump(e);
    }
}
</cfscript>

which correctly dumps rc.myvalue, and then catches this error

The key [rc] does not exist.
lucee.runtime.exp.ExpressionException: The key [rc] does not exist.
	at lucee.runtime.type.scope.UndefinedImpl.get(UndefinedImpl.java:240)
	at lucee.runtime.type.scope.UndefinedImpl.get(UndefinedImpl.java:184)
	at views.main.test_cfm$cf$c7h.udfCall(/views/main/test.cfm:4)

maybe i'm not remembering this correctly, but i thought functions had access to the calling context variables

I've created an ulid extension, haven't published it yet, if you wanna try it out, it's here https://dev.lucee.org/t/add-support-for-ulids-createulid/12602/7

with a bottle of jameson and radiohead cranked up loud, I've been going thru old tickets and disabled test cases https://github.com/lucee/Lucee/pull/2065/files found a few unfixed "resolved" tickets 😞 some stuff now works 🙂

thoughts? https://luceeserver.atlassian.net/browse/LDEV-1569?focusedCommentId=53698

another breaking change for six? https://luceeserver.atlassian.net/browse/LDEV-1718

and another https://luceeserver.atlassian.net/browse/LDEV-3340

posted to the mailing list, both are much more sensible defaults https://dev.lucee.org/t/more-breaking-changes-for-6-0/12615

Hey any reason

priority

has not been implemented on

cfmail

? (ref: https://docs.lucee.org/reference/tags/mail.html#attribute-priority)

Hi Guys With respect to Lucee's BIF

ConfigImport()

, does anyone know if this object key:

maxCFThreads

Refers to:

It doesn't seem to work, when I add this property? Nothing changes...

the feedback from a json parsing error has always been a bit sub optimal.... https://luceeserver.atlassian.net/browse/LDEV-4225

[INFO]      [java]    [script] 	test.tickets.LDEV4225

[INFO]      [java]    [script] Syntax Error, invalid Expression [7] at position [1025]

[INFO]      [java]    [script] [ a a a " }7D]

[INFO]      [java]    [script]

[INFO]      [java]    [script] Syntax Error, invalid Expression [7] at position [25] in [{ content: "a a a a a " }7D]

We had some changes with the JSON Serializer that has broken the build process, bwecause of some unnecessary whitespace.

that should be fixed now

i also just added a new argument to the function serializeJson called “compact” that allows to control the output.

• compact =true (default): as before all json on a single line

• compact=false: json on multiple lines with indentions

I'm trying out the light lucee docker image. In one of my downstream image's containers, I'm getting some errors. FYI, in its Lucee admin, it shows that the S3 extension is installed. Any guesses as to what's wrong? (Lucee 5.3.10.97) https://gist.github.com/jamiejackson/b2d9d1fe68b546e7cab353a873d956cd

I try to upgrade an instance off lucee and I got an issue. I still can log under the admin of server context. But when I try to do the same for th web context I get that message : "Access is protected" my previous instance of lucee was under lucee-5.3.8.206 created with command box 5.4.2 (window). my new installation is under 5.3.10.120 created with command box 5.9.0 (window). I try to reset/set the password of the web context from the server context without any success. someone had an idea what I should do? it's a new option from lucee 5.3.10 that enable by default?

Had anybody had a chance to play with the new lucee hibernate module that Ortus is putting together? I'm not seeing a ton of change logs on it yet, and I'm wondering if the logSQL property is finally fixed :)