http://coldfusion.com logo
#adobe
Title
# adobe
b

bdw429s

02/10/2022, 5:57 AM
@Mark Takata (Adobe) There aren't any "features" of the bug tracker where rejecting a ticket doesn't E-mail the reporter, are there? This ticket of mine was closed (and for terrible reasons, I might add) a few months ago and I've searched my E-mail and can confirm I was never notified at all. https://tracker.adobe.com/#/view/CF-4212129 Also, for crying out loud, can we get this ticket re-opened and some sensible discussion going please? The reason for closing it was basically, "well, that's how it works, so it must be as designed!"
a

Adam Cameron

02/10/2022, 8:28 AM
That is appalling behaviour from the CF Team there, @Mark Takata (Adobe). As well as sensible discussion taking place, I think heads need to be knocked together over this one.
m

miguel-f

02/10/2022, 12:30 PM
Yeah we have reported to Adobe before (before Mark) a few times on the fact that no notification is sent when ticket status changes. And that they do not add a note detailing why the status changed to whatever. Poor customer service.
a

Adam Cameron

02/10/2022, 1:30 PM
To me in this case it seems like the notification was actively suppressed when the ticket was updated. I mean there was a comment from someone on the CF team at the time. If I was unkind (moi?) I would suspect that the notification was suppressed specifically because the response from the CF Team was so poor.
m

Mark Takata (Adobe)

02/10/2022, 3:38 PM
So, I'm gonna go ahead and stick my foot firmly in the middle of this. First off, it is not a bug, by definition. It is doing exactly what it was built to do. So, being completely clear, that's the situation. NOW, before you start throwing things at me, is this functionality GOOD? No. I agree that leveraging the internal error msg is both generally a bad call and in this case particularly a very bad developer experience which likely should be altered. which is a feature request. And a very good and useful feature request.
Which, I might add, I am now entering into the system for this item as a feature request, which I will bring up at the next core meeting.
Feature request number is: CF-4212752. Feel free to vote it up if you'd like, I'm actually asking for more than just the java class name listed, I'm asking for them to look at anything that's being handled in this way.
a

Adam Cameron

02/10/2022, 6:41 PM
I do not want to get into whether this should be considered a bug or not, but just to call you on some faulty reasoning:
It is doing exactly what it was built to do.
Yeah but if what it was being built to do is wrong, then it's still a bug. If you write a function called
pi
and it returns
3
because you specifically decided "we're only using this in the bible, and god's understanding of trigonometry is a bit bronze age", then it's still a bloody bug because it's wrong. "wrong" can be "because it's inappropriately inaccurate (as in here), or "because it's a security vulnerability". Poor design decisions are bugs.
m

Mark Takata (Adobe)

02/10/2022, 7:56 PM
Adam, we can go back and forth endlessly on this. If poor design decisions are bugs, then my entire life is pretty much a bug. I prefer to think of it as a creative set of feature requests, which keep getting denied. Hence, why I need a beer at noon on a Thursday. šŸ™‚
šŸ¤” 1
a

Adam Cameron

02/10/2022, 8:20 PM
then my entire life is pretty much a bug
I think it's important to note that it wasn't me who said that.
Adam, we can go back and forth endlessly on this.
And that just sounds like a dare.
b

bdw429s

02/10/2022, 9:49 PM
It is doing exactly what it was built to do.
@Mark Takata (Adobe) The docs I linked to in the comments of the ticket clearly state the len() function accepts two things ā€¢ strings ā€¢ binary How can you possibly stand by the idea that accepting a UDF is working as designed. It's certainly not working as documented. So at least one of these two simply cannot be correct. You must either update the docs to match the function or the function to match the docs. But they can't be different and us still pretend everything is fine.
šŸ‘ 1
Feature request number is: CF-4212752. Feel free to vote it up if you'd like
That ticket not only has nothing to do with mine, it makes zero sense and it written by someone who has no clue what's going on. Firstly, they think
cfindex2ecfm917914804$funcBAR@2d10b587
is an "error" when it's nothing of the sort! It's the name of the class in memory, not an error at all. I have no issues with the fact that certain classes have the ability to represent themselves as a string-- that is wholly unrelated to the input validation of the
len()
function.
If we want to vote for an enhancement, let's have Adobe match Lucee's behavior of adding "array" to the list of acceptable inputs which operates as a shortcut for
arrayLen()
But it should still be rejecting inputs which are not documented as valid inputs for the function. There's really no other argument to be made there!
m

Mark Takata (Adobe)

02/10/2022, 11:09 PM
Well, I just told the staff to close my ticket. So there you go.
2 Views