Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

6.1.0 stable regressions

Description

I’m seeing a lot of problems with the latest stable release

running this tweaked version of the simple benchmarks, I am seeing a range of very odd errors

using a fresh install of 6.0.3.1 upgraded to 6.0.1.243, running via the browser using mapping /benchmark pointing to the custom/benchmark

best run via tomcat manually as there’s a lot of console logging, the runner code is meant to catch errors with try catches, but they are also being not caught/logged in the browser but they are visible in the console logging?

GitHub - lucee/lucee-testlab at debugging-21_july_2024

all sorts of strange things happen, some of the errors seems to cascade after one thing goes wrong

I’m seeing templates run via internal request, inside parallel arrayEach-es picking up older code somehow, despite stopping, clearing classes and restarting

i.e in the above branch, the qoq hsqldb query is commented out, but i’m still seeing those errors been thrown, i don’t know how even???

QoQ somehow ignoring dbtype=”query” and throwing an error either from the default datasource or missing default datasource

falling back onto the classic listener?

truncated class files

I have also been testing with backporting https://luceeserver.atlassian.net/browse/LDEV-5023 onto 6.1.0.243 which reveals other problems, hidden by that regression

75% Done
Type
Key
Summary
Priority
Story Points
Assignee
Status

Activity

Show:
Michael Offner
changed the Status19 August 2024 at 19:41
New
Resolved
Zac Spitzer
updated the Rank24 July 2024 at 07:23
None
Ranked higher
Zac Spitzer
updated the Description21 July 2024 at 09:23
I’m seeing a lot of problems with the latest stable release running this tweaked version of the simple benchmarks, I am seeing a range of very odd errors using a fresh install of 6.0.3.1 upgraded to 6.0.1.243, running via the browser using mapping /benchmark pointing to the custom/benchmark best run via tomcat manually as there’s a lot of console logging, the runner code is meant to catch errors with try catches, but they are also being not caught/logged in the browser but they are visible in the console logging? [https://github.com/lucee/lucee-testlab/tree/debugging-21_july_2024|https://github.com/lucee/lucee-testlab/tree/debugging-21_july_2024|smart-link] all sorts of strange things happen, some of the errors seems to cascade after one thing goes wrong I’m seeing templates run via internal request, inside parallel arrayEach-es picking up older code somehow, despite stopping, clearing classes and restarting i.e in the above branch, the qoq hsqldb query is commented out, but i’m still seeing those errors been thrown, i don’t know how even??? QoQ somehow ignoring dbtype=”query” and throwing an error either from the default datasource or missing default datasource falling back onto the classic listener? truncated class files
I’m seeing a lot of problems with the latest stable release running this tweaked version of the simple benchmarks, I am seeing a range of very odd errors using a fresh install of 6.0.3.1 upgraded to 6.0.1.243, running via the browser using mapping /benchmark pointing to the custom/benchmark best run via tomcat manually as there’s a lot of console logging, the runner code is meant to catch errors with try catches, but they are also being not caught/logged in the browser but they are visible in the console logging? [https://github.com/lucee/lucee-testlab/tree/debugging-21_july_2024|https://github.com/lucee/lucee-testlab/tree/debugging-21_july_2024|smart-link] all sorts of strange things happen, some of the errors seems to cascade after one thing goes wrong I’m seeing templates run via internal request, inside parallel arrayEach-es picking up older code somehow, despite stopping, clearing classes and restarting i.e in the above branch, the qoq hsqldb query is commented out, but i’m still seeing those errors been thrown, i don’t know how even??? QoQ somehow ignoring dbtype=”query” and throwing an error either from the default datasource or missing default datasource falling back onto the classic listener? truncated class files I have also been testing with backporting [https://luceeserver.atlassian.net/browse/LDEV-5023|https://luceeserver.atlassian.net/browse/LDEV-5023|smart-link] onto 6.1.0.243 which reveals other problems, hidden by that regression
Zac Spitzer
updated the Epic Child21 July 2024 at 09:22
None
LDEV-5023
Zac Spitzer
updated the Description21 July 2024 at 09:21
I’m seeing a lot of problems with the latest stable release running this tweaked version of the simple benchmarks, I am seeing a range of very odd errors using a fresh install of 6.0.3.1 upgraded to 6.0.1.243, running via the browser using mapping /benchmark pointing to the custom/benchmark best run via tomcat manually as there’s a lot of console logging, the runner code is meant to catch errors with try catches, but they are also being not caught/logged in the browser but they are visible in the console logging? [https://github.com/lucee/lucee-testlab/tree/debugging-21_july_2024|https://github.com/lucee/lucee-testlab/tree/debugging-21_july_2024|smart-link] all sorts of strange things happen, some of the errors seems to cascade after one thing goes wrong I’m seeing templates run via internal request, inside parallel arrayEach-es picking up older code somehow, despite stopping, clearing classes and restarting QoQ somehow ignoring dbtype=”query” and throwing an error either from the default datasource or missing default datasource falling back onto the classic listener? truncated class files
I’m seeing a lot of problems with the latest stable release running this tweaked version of the simple benchmarks, I am seeing a range of very odd errors using a fresh install of 6.0.3.1 upgraded to 6.0.1.243, running via the browser using mapping /benchmark pointing to the custom/benchmark best run via tomcat manually as there’s a lot of console logging, the runner code is meant to catch errors with try catches, but they are also being not caught/logged in the browser but they are visible in the console logging? [https://github.com/lucee/lucee-testlab/tree/debugging-21_july_2024|https://github.com/lucee/lucee-testlab/tree/debugging-21_july_2024|smart-link] all sorts of strange things happen, some of the errors seems to cascade after one thing goes wrong I’m seeing templates run via internal request, inside parallel arrayEach-es picking up older code somehow, despite stopping, clearing classes and restarting i.e in the above branch, the qoq hsqldb query is commented out, but i’m still seeing those errors been thrown, i don’t know how even??? QoQ somehow ignoring dbtype=”query” and throwing an error either from the default datasource or missing default datasource falling back onto the classic listener? truncated class files
Zac Spitzer
changed the Assignee21 July 2024 at 09:19
Unassigned
Michael Offner
Zac Spitzer
changed the Priority21 July 2024 at 09:19
New
Blocker
Zac Spitzer
updated the Labels21 July 2024 at 09:19
None
regression
Zac Spitzer
updated the Description21 July 2024 at 09:19
I’m seeing a lot of problems with the latest stable release running this tweaked version of the simple benchmarks, I am seeing a range of very odd errors using a fresh install of 6.0.3.1 upgraded to 6.0.1.243, running via the browser using mapping /benchmark pointing to the custom/benchmark [https://github.com/lucee/lucee-testlab/tree/debugging-21_july_2024|https://github.com/lucee/lucee-testlab/tree/debugging-21_july_2024|smart-link] all sorts of strange things happen, some of the errors seems to cascade after one thing goes wrong I’m seeing templates run via internal request, inside parallel arrayEach-es picking up older code somehow, despite stopping, clearing classes and restarting QoQ somehow ignoring dbtype=”query” and throwing an error either from the default datasource or missing default datasource falling back onto the classic listener? truncated class files
I’m seeing a lot of problems with the latest stable release running this tweaked version of the simple benchmarks, I am seeing a range of very odd errors using a fresh install of 6.0.3.1 upgraded to 6.0.1.243, running via the browser using mapping /benchmark pointing to the custom/benchmark best run via tomcat manually as there’s a lot of console logging, the runner code is meant to catch errors with try catches, but they are also being not caught/logged in the browser but they are visible in the console logging? [https://github.com/lucee/lucee-testlab/tree/debugging-21_july_2024|https://github.com/lucee/lucee-testlab/tree/debugging-21_july_2024|smart-link] all sorts of strange things happen, some of the errors seems to cascade after one thing goes wrong I’m seeing templates run via internal request, inside parallel arrayEach-es picking up older code somehow, despite stopping, clearing classes and restarting QoQ somehow ignoring dbtype=”query” and throwing an error either from the default datasource or missing default datasource falling back onto the classic listener? truncated class files
Zac Spitzer
updated the Epic Child21 July 2024 at 09:17
None
LDEV-5038
Zac Spitzer
updated the Sprint21 July 2024 at 09:15
None
6.1.1
Zac Spitzer
updated the Description21 July 2024 at 09:14
None
I’m seeing a lot of problems with the latest stable release running this tweaked version of the simple benchmarks, I am seeing a range of very odd errors using a fresh install of 6.0.3.1 upgraded to 6.0.1.243, running via the browser using mapping /benchmark pointing to the custom/benchmark [https://github.com/lucee/lucee-testlab/tree/debugging-21_july_2024|https://github.com/lucee/lucee-testlab/tree/debugging-21_july_2024|smart-link] all sorts of strange things happen, some of the errors seems to cascade after one thing goes wrong I’m seeing templates run via internal request, inside parallel arrayEach-es picking up older code somehow, despite stopping, clearing classes and restarting QoQ somehow ignoring dbtype=”query” and throwing an error either from the default datasource or missing default datasource falling back onto the classic listener? truncated class files
Zac Spitzer
updated the Affects versions21 July 2024 at 09:13
None
6.1.0.243
Zac Spitzer
updated the Epic Child21 July 2024 at 09:06
None
LDEV-5035
Zac Spitzer
updated the Epic Child21 July 2024 at 09:06
None
LDEV-5036
Zac Spitzer
created the Issue21 July 2024 at 09:06
Unresolved

Details

Assignee

Reporter

Labels

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Sprint

Affects versions

Priority

Created 21 July 2024 at 09:06
Updated 19 August 2024 at 19:41

Flag notifications