So I went off and made some improvements to the OSGI bundle error reporting • we optional print out errors to console (i.e. during build, smoketest in your face ) • includes the bundle name (i.e. s3, hibernate, etc) when throwing an OSGI bundle error https://luceeserver.atlassian.net/browse/LDEV-4108 i.e. during a build, it now outputs https://github.com/lucee/Lucee/runs/7577886443?check_suite_focus=true#step:20:383 what does this mean for lucee users? the lucee devs can now see these problems immediately

We are switching from CF2018 to lucee and I ran into a problem with some java objects that we use to get google analytics data. When one of them is initialized I get 'No matching Constructor for com.google.api.services.analytics.Analytics$Builder(com.google.api.client.http.javanet.NetHttpTransport, com.google.api.client.json.jackson2.JacksonFactory, lucee.runtime.java.JavaObject) found'. The third argument is showing as lucee.runtime.java.JavaObject, when the object I am passing is a com.google.api.client.http.HttpRequestInitializer. It has the correct class when I dump it out, but not when I try to pass it to the other object.

@zackster So I had more time last night to break one of my Lucee servers to try to figure out why I can't upgrade from 5.3.8.206 to 5.3.9.141.

i have a bunch of url and some of them are optional, i am trying to loop over them and if they exists and defined, i want to use only that, my only concern right now is the placement of ? and & operator where i am messing up the code

Lucee now has testcoverage for CFLDAP, now on to the real meat, removing old jars https://github.com/lucee/Lucee/compare/6.0.0.218...195861f

Improving Lucee exception messages is a great way to get involved in open source, if you ever see something which could be improved, just fire off a PR, it's really easy to do, just • do a search on github https://github.com/lucee/Lucee/search?q=a+timeout+occurred • open a result, switch the to 6.0 branch, i.e. https://github.com/lucee/Lucee/blob/6.0/loader/src/main/java/lucee/runtime/lock/LockTimeoutException.java • click the edit icon https://github.com/lucee/Lucee/blob/6.0/loader/src/main/java/lucee/runtime/lock/LockTimeoutException.java which opens the web based editor https://github.com/lucee/Lucee/edit/6.0/loader/src/main/java/lucee/runtime/lock/LockTimeoutException.java • make your changes and file off a pull request the exception formatting house rules in Lucee is that all variables should be wrapped in

[brackets]

this enables our grouping up in Sentry of related errors and when there is a list of options, there should be a space between options i.e.

[application, session]

not

[application,session]

First word in an exceptions should also be Capitalized (edited)

reckon I have finally solved LDEV-3431 fix javax.mail.Provider: com.sun.mail.imap.IMAPProvider not a subtype https://github.com/lucee/Lucee/pull/1741 so now we have test coverage! which means other bugs can be addressed with test cases like https://luceeserver.atlassian.net/browse/LDEV-4115

You know the query

returntype="array"

parameter? Is there a way to do that by default at the application level so we don’t have to specify it on every query? If it does exist, I can’t seem to find it in the docs.

something we have been working on to help make uncoordinated DDOS attacks less effective allow reducing the priority of concurrent requests https://dev.lucee.org/t/allow-reducing-the-priority-of-concurrent-requests/10807 https://luceeserver.atlassian.net/browse/LDEV-4123 https://github.com/lucee/Lucee/commit/beee2e20c6a9ec2080d20125d4a0e2eed2348a7ce

I tried to find info on dev.lucee.org first, but came up empty. Will there be a 5.3.10 release or is the next release 6.0? Any ideas on timeframes yet for 6.0?

I have found a bug. We are trying to check if a given string is Json. The string we are putting into the isJson function happens to be a hexadecimal string.

isJson("7E58651173259DD1");

results in

lucee.runtime.exp.NativeException: Too many nonzero exponent digits.

isJson("5E7770101309BD75");

results in

lucee.runtime.exp.NativeException: Exponent overflow.

(tested on lucee deviant-lucee 5.3.9.146 )

Bullet dodged, that was going to be photo for my next Lucee release notes post https://twitter.com/vicenews/status/1555561830025773056?s=21&t=8l0ovYvyuNNEW7vYly0CNw

Friday update, got open PRs down to 125 https://github.com/lucee/Lucee/pulls • 6.0.0.229 • 5.3.10.48 • 5.3.9.155 deets on the dashboard https://luceeserver.atlassian.net/jira/dashboards/10700e actually this is a good overview https://luceeserver.atlassian.net/issues/?jql=status%20in%20(Deployed%2C%20Done%2C%20QA)%20ORDER%20BY%20updated%20DESC

Thoughts on this breaking-change for 6.0, I wanna make feature detection cleaner (i.e. is ESAPI installed) https://luceeserver.atlassian.net/browse/LDEV-4134

@zackster Did you ever identify a service for testing LDAP (like how you use Greenmail for POP/IMAP/SMTP)?

we have a regression with 5.3.9 which is hard to repo on mac M1s (i can reproduce on my i7 windows laptop) https://luceeserver.atlassian.net/browse/LDEV-4004 https://github.com/lucee/Lucee/blob/5.3/test/tickets/LDEV4004-v2.cfc the test case is ugly, but when i tried to clean it up further it stopped repo-ing anyone on a mac M1 care to try and help? add

return (path contains "4004");

here to just run these tests https://github.com/lucee/Lucee/blob/5.3/ant/run-testcases.xml#L170

Hi

Question on log file settings...

Another question re log file settings. Say I have a log file created with

<cflog file="my.log">

(recap: despite being documented as not being implemented, this actually has been, and it "works"). This log file is not listed in

/lucee/admin/web.cfm?action=server.logging

, which is in itself perhaps an issue, but I can poss understand how Lucee might decide it's not its business to manage custom logs. Or is this part of "not implemented"? Anyhow, not the main question here. Given there's no way to set things like "Max Files" and "Max File Size (in bytes)" as one might for Lucee's own logs, should I take from this that Lucee will not do anything by way of log retention policy for these "custom" logs? (This would actually be exactly what I want to happen, in this case, as it happens). There's no docs I can find one way or the other on this. Perhaps another symptom of "not implemented"? To be clear (to try to focus replies staying on-topic), the question is this:

should I take from this that Lucee will not do anything by way of log retention policy for these "custom" logs?

Question/observation regarding the search in Lucee's docs. When investigating the above stuff about log file config, I was trying to find something / anything documented. I settled on "appender" being a good search term that is relevant to log file settings, but unlikely to crop up in too many other places. [cont'ed in thread]

So... I'm generating a pdf file using cfdocument that includes a link into our website that will only work if the user is logged in, otherwise they get redirected to the login page. If I open the pdf in adobe acrobat and am logged into the website then the link works fine. If I open the pdf in a browser (Chrome, Firefox and Brave were tested) and am logged into the website in the same browser then: --- If I copy the link from the pdf into a new tab the link works fine, but --- If I click the link directly in the browser tab (or right-click and open in new tab) then my session is not found, OnSessionStart is triggered and as I have a new sessionId I get logged out. So the link works in two of the three ways it can be used to access the page. But what is going on with the 'in-browser' click that it triggers a new session?

I am noticing that cfscript.me is down - are there any alternative recommendations for cfml tags to cfscript conversion tools for vscode or sublime text?

Under Lucee 5.3.9.141, I'm getting an unexpected results with

isNumeric()

with a value run through the

numberFormat()

function. I would expect the following code to return

true

, but it's returning `false`:

dump(isNumeric(numberFormat(-2360, "9,999.9")));

However, all of the following variations do return `true`:

dump(isNumeric(-2360));
dump(isNumeric(-2360.0));
dump(isNumeric("-2360.0"));
dump(isNumeric(numberFormat(-236, "9,999.9")));

Now strangely enough, it appears that ACF & Lucee both have the same behavior. You can see this behavior on TryCF: https://www.trycf.com/gist/6928301c037034c917e8771700dad03c/lucee5?theme=monokai Am I misunderstanding something or should

isNumeric(numberFormat(-2360, "9,999.9"))

indeed be returning

true

?

Very excited to announce our new Redis extension for LUcee: https://www.ortussolutions.com/blog/want-native-redis-support-in-luceecfml-ortus-redis-extension-v200-released

anyone got any ideas? https://dev.lucee.org/t/strange-problem-with-zip4j-since-2-11-0-compress-extension/10861

Using lucee 5.3.3+62 Has anyone experienced an issue regarding the math function

sqr()

with an error returning

ClassFormatError:Incompatible magic value 0 in class file lucee/runtime/functions/math/Sqr

? This is happening when a component is getting initialized, but the

sqr

function is not yet executed in a different function further down in the component. I have tested the

sqr

function itself in commandbox::repl and it works fine, but receive an error when placed in a script component function, even when I plugged in a plane number and tried testing both the

sqr

function and the

sqr

member function with the following in my code.

testSquareRoot = sqr(25);

testSquareRoot = sqr(number=25);

testSquareRoot = (25).sqr();

I've updated lucee docs to show introduced data for arguments and attributes (if specified) https://luceeserver.atlassian.net/browse/LD-151 i.e. https://docs.lucee.org/reference/functions/iscustomfunction.html https://dev.lucee.org/t/docs-now-show-introduced-versions-for-arguments-and-attributes/10869