Can we have lucee installer for Mac 😃 just like we have for windows

Another weird bug involving QoQ: https://luceeserver.atlassian.net/browse/LDEV-3849 Here's a TryCF example: https://www.trycf.com/gist/125cea59fb0c1bc068f27b3c2546e99d/lucee5?theme=monokai I wonder if perhaps this might be something related to @bdw429s’s recent QoQ changes.

Is there a way in Lucee to force the "returnFormat" of a remote function? In ACF, I could do url.returnFormat to force the return format but that "trick" does not appear to work in Lucee.

So I'm seeing weird issues with the <cflocation /> tag under 5.3.8.206. There are a couple of Jira issues regarding location & encoding. If I have the following code, then the value

x

ends up getting encoded twice:

<cflocation url="/index.cfm?#(len(x) ? '&x=' & encodeForUrl(x) : '')#" />

However, if I change the code to:

<cfset y = "/index.cfm?#(len(x) ? '&x=' & encodeForUrl(x) : '')#" />
<cflocation url="#y#" />

I get the expected results. It looks like Lucee is sometimes automatically encoding strings in the <cflocation /> tag, but ACF does not do that. What is the expected behavior?

@zackster I just tried updating from 5.3.8.206 to 5.3.9.61-SNAPSHOT and I'm getting the following exception after restarting Tomcat: java.io.IOException: Failed to download the bundle for [com.sun.jna] in version [5.10.0] from [https://update.lucee.org/rest/update/provider/download/com.sun.jna/5.10.0/?allowRedirect=true&amp;jv=11.0.13], please download manually and copy to [/opt/lucee/config/server/lucee-server/bundles]

We are totally focused on getting RC1 out with 5.3.9 at the moment.... PRs without tests are only half done, feel like writing some? you can fork the repo and drop them into a /tests folder and Github Actions will run them for you. https://github.com/lucee/extension-hibernate/blob/5.4/.github/workflows/main.yml#L56 We use H2 for most of the Orm tests (as it's standalone), examples here https://github.com/lucee/Lucee/blob/6.0/test/orm/Hibernate.cfc#L20

What is the last version enhancement before Lucee 5 becomes LTS only and 6 is the primary focus? @zackster

Morning Lucee channel! I recently upgraded from 5.3.7.47 to the latest 5.3.8.206 and noticed an issue with QoQ. I had a select statement that was properly looking at a null column but after upgrading returned no results. Didn’t know what the issue was initially, but after a bunch of code breaks and dumps tracked it down to this.

SELECT id WHERE field IS NULL

worked initially, returning results, but after upgrade returned nothing

SELECT id WHERE field = ''

this is what I finally figured out works after upgrading Just wondering if this is known, or am I the only one using QoQ still? 😄

I posted about this a few days ago and didn't get a response, so I posted on Lucee Forum. What's the expected behavior of

<cflocation />

under Lucee with regards to encoding? I'm finding that it sometimes automatically encodes parameters, but not in all situations. Automatic encoding of parameters breaks ACF compatibility, because ACF doesn't do this. https://dev.lucee.org/t/cflocation-encoding-of-url/9606

I'd put that in a CONTRIBUTING.md rather than README.md. README.md should be able the application. CONTRIBUTING.md should be able the project (all IMO, obvs)

Is there a good way to clear the cache for a specific query instead of the entire query cache (using cachedWithin to put it in the cache)? We see this post about a “tags” argument/attribute but there is no documentation on how to use it with queryExecute and the tags aren’t mentioned anywhere in the docs. Any help on clearing the cache of a specific query would be much appreciated. Thoughts?

I have a cfhttp call that is running a basic GET request to an API endpoint that simply returns a small data object (struct). If I hit the api endpoint directly in the browser it returns data every time with 200 status and data returned. However, when I try and call the endpoint using cfhttp() I occasionally see an error:

string	key [filecontent] doesn't exist

To try and mitigate this occasional error I run the cfhttp in a while loop and give it up to 4 attempts to call the api. However, I still see the above error more often than should be possible. Is there anything I can do to further mitigate this issue - is there an issue with cfhttp?

hi, how can i make sure the query is returned all rows

for(i in myquery) {
                    var aData = [];
                    st[aData]['RowNum'] = i.currentrow;
}

@Simone just dump the query. Then look at the data. It should tell you why. If you still can't see it, in your approach dump the record i and call flush just after that. Or use a try/catch block and in the catch statement dump i

i've updated the docs, they were a little out of date https://docs.lucee.org/guides/Various/lucee-maven.html

how we right in cfscript <cfoutput query="q"> <cfset QueryAddRow(myqry, 1)> <cfset QuerySetCell(myqry, "a", "c", #q.CurrentRow#) /> <cfset QuerySetCell(myqry, "b", "d", #q.CurrentRow#) /> </cfoutput> i tried use for(i in q) but i.currentrow does not exists in this

5.3.8.206 is not showing the compress-extension-1.0.0.2.lex as an option should it or are they now built in by default?

Is there any way to get the SQL statement (and params) out of a

database

exception? If has

queryError

and

Sql

(nice capitalisation btw) there, but that is not what was sent to the DB: it's a string with the param placeholders swapped out for the data values.

Here's some code: https://trycf.com/gist/26026a9e3ce1827161ea3db19a02723c/lucee5?theme=monokai To me, ColdFusion is doing the right thing, and Lucee makes me go "WTF are you like, seriously?"

@zackster is there a reliable download link for your performance analyzer, I can see it in lucee admin and forgebox but not on https://download.lucee.org/ I would like to include it in a build pipeline

Is this weird? The type changes to actual boolean on the 2nd dump. Or maybe I’m misunderstanding how

booleanFormat()

works? https://trycf.com/gist/e63f40983cb86a0b178bcc1ff4e8215f/lucee5?theme=monokai

Any CommandBox experts around? I was hoping to use DocBox from a Commandbox commandline on a codebase involving static methods. I reported an issue with getComponentMetaData omitting static methods and properties a while back (https://luceeserver.atlassian.net/browse/LDEV-3362) and it was fixed in Lucee 6.0.0.144, so I was hoping that a hearty config set server.defaults.app.cfengine=lucee@6.0.0-SNAPSHOT+14 and CommandBox restart would lead to CommandBox itself using Lucee ´6 - but as the docbox result is still very empty for anything static, I assume that this config setting only applies to servers started from within CommandBox. Is there some way to change the very engine CommandBox itself is using in order to use DocBox on static methods and properties?

Hey is there any way to get the underlying connection object from a data source name? For some failsafe checks I need to ensure that some JDBC settings are in place (specifically the

allowMultiQueries

setting passed in the connection string).

Id personally go DB and store previous run time maybe even start/finish in a table. Bonus is you get to see how often people are kicking off the process. Tho I am in the boat of never manually kicking off scheduled processes. Expanding on this, we normally go off the start time and make sure the job hasn't run for at least x minutes which is normally double normal run time. In case process exploded and never recorded an end time. We also track wether it was a system called job or if a user kicked it off manually based off token security so we can ask why someone thought they needed to manually.

FYI, the ESAPI extension most recent snapshots are labeled SNAPHOT instead of SNAPSHOT

Hi there @zackster, would it be possible for this troublesome bug to get resolved, please? https://luceeserver.atlassian.net/browse/LDEV-3750

When I dump a query, I get some metadata about it: How do I extract that from the query object? I am specifically after the

cached

value.

getMetadata

only returns column info, not stuff about the query object itself. Note: I am not asking about the

result

option that one can pass to a

queryExecute

call. I only have the query object; I am not in control of the initial call, so I cannot use the

result

. Cheers.

valueList

is marked as deprecated on Lucee (ref: https://docs.lucee.org/reference/functions/valuelist.html). Is it really for Lucee to be deprecating something in CFML, given it's up to Adobe what is and is not deprecated in their language? What's the perceived gain in marking it thus, other than making devs writing cross-platform from going "oh FFS". Which to me is not a gain. (yes, I have read https://docs.lucee.org/reference/deprecated.html. That is not what I am asking).