this bug is really odd <https://github.com/zspitze...
# lucee
z
this bug is really odd https://github.com/zspitzer/LDEV-4620 @bdw429s any thoughts?
b
Since the error is in resolution of a CFC path, I assume it's related to Lucee's CF Mappings or Component lookup paths
I'd find out what mapping, custom tag path, or Component path is responsible for resolving
new Query()
and put in some debugging to see • if it's loaded at the point of the error • what the logic is doing that's searching for the component
Also, adding a sleep prior to running the
new Query()
code will rule out a Lucee-not-ready-yet scenario.
z
Tried a sleep, didn't help. Also added a redirect so it's running in a second request, no help I wish I could repo outside of github actions, then I could step debug. The initial deploy is all single threaded, so I dont think it's a race condition, .495 is a major rewrite of the deploy, mostly to handle switching modes which is basically a heart transplant (we solved some odd bugs surfaced whilst trying to solve that)
Backporting a fix from 494 from 495 to rule that change out and manually uploading that version
Ahhh found a related deeper regression which last worked with light-6.0.0.53!
Screenshot_20230709-143943.png