All work
- injected methods produce confusing stacktraces with parallel eachLDEV-5557
- NPE on CallStackGet() with 5.3LDEV-4416Resolved issue: LDEV-4416Michael Offner
- Improve performance of cfdump by removing file system exists checkLDEV-3697
- Log trace of cflocation and allow option to AbortLDEV-3720Resolved issue: LDEV-3720Igal Sapir
- NPE with CallStackGetLDEV-3616Resolved issue: LDEV-3616Pothys - MitrahSoft
- Syntax Error, invalid Expression when evaluating function which takes no argumentsLDEV-2762Michael Offner
- add optional offset argument to callStackGet()LDEV-1328Resolved issue: LDEV-1328Igal Sapir
- CallStackGet()...function and GetFunctionCalled name-casing as compared to ACF.LDEV-2590
- Add option to show cfml stack trace in cftraceLDEV-1648
- callStackGet() function no longer returns full paths to templateLDEV-1036Resolved issue: LDEV-1036Michael Offner
10 of 10
injected methods produce confusing stacktraces with parallel each
Description
Environment
None
Attachments
1
Details
Details
Assignee
Unassigned
UnassignedReporter
Zac Spitzer
Zac Spitzer
Priority
NewLabels
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
Created 30 April 2025 at 12:39
Updated 14 May 2025 at 07:00
docs does somewhat complex injecting methods approach and when there’s an error, the stacktrace is quite wrong and not so useful
the exception message is throw callStackGet('string') whch has the right paths
this is happening inside a each(parallel), i think we could set the caused by for the exception here?