madExcept & BugZilla

[GunterO]

Hi,

I'm in the process of switching from EurekaLog to madExcept, but ran into a problem.
Bug catching is working very well (also in our plugins, the reason why I'm moving away from Eurekalog), but sending the report to our Bugzilla server is not working.
The madExcept settings dialog for madExcept is showing 3 green check marks, and the project & data comboboxes are showing the correct data, so no problem there I guess.
But when I trigger an exception, and press "Send bug report", it is showing the "Connecting to server" dialog for about 10sec, and then a dialog saying "Sorry, sending the bug report didn't work."

Any tips to tackle / debug this problem? Or some log where I can see what exactly the problem is?

Winfows 8.1 Pro
Delphi XE6 Enterprise (20.0.16277.1276)
madExcept 4.0.11 Free version
BugZilla v4.4.2

Thanks!

[GunterO]

Hi,

Some more tests:
1. The same settings in a EurekaLog setup are working fine.
2. I checked our Apache logs, and there is some communication, but I'm not sure where it goes wrong. I included the log of a successful EurekaLog session as well:

Code: Select all

83.101.???.??? - - [13/Feb/2015:12:25:11 +0100] "POST /xmlrpc.cgi HTTP/1.1" 200 209 "-" "madExcept/4.0"
83.101.???.??? - - [13/Feb/2015:12:25:13 +0100] "POST /xmlrpc.cgi HTTP/1.1" 200 209 "-" "madExcept/4.0"
83.101.???.??? - - [13/Feb/2015:12:25:16 +0100] "POST /xmlrpc.cgi HTTP/1.1" 200 292 "-" "madExcept/4.0"
83.101.???.??? - - [13/Feb/2015:12:25:18 +0100] "POST /xmlrpc.cgi HTTP/1.1" 200 7065 "-" "madExcept/4.0"
83.101.???.??? - - [13/Feb/2015:12:25:20 +0100] "POST /xmlrpc.cgi HTTP/1.1" 200 54429 "-" "madExcept/4.0"
83.101.???.??? - - [13/Feb/2015:12:25:22 +0100] "POST /xmlrpc.cgi HTTP/1.1" 200 338 "-" "madExcept/4.0"


83.101.???.??? - - [13/Feb/2015:12:34:05 +0100] "POST /xmlrpc.cgi HTTP/1.1" 200 209 "-" "EurekaLog"
83.101.???.??? - - [13/Feb/2015:12:34:07 +0100] "POST /xmlrpc.cgi HTTP/1.1" 200 194 "-" "EurekaLog"
83.101.???.??? - - [13/Feb/2015:12:34:10 +0100] "POST /xmlrpc.cgi HTTP/1.1" 200 292 "-" "EurekaLog"
83.101.???.??? - - [13/Feb/2015:12:34:12 +0100] "POST /xmlrpc.cgi HTTP/1.1" 200 7065 "-" "EurekaLog"
83.101.???.??? - - [13/Feb/2015:12:34:14 +0100] "POST /xmlrpc.cgi HTTP/1.1" 200 207 "-" "EurekaLog"

3. Tested with the Bugzilla test server (https://landfill.bugzilla.org/bugzilla-4.4-branch), and this is not working either with madExcept 4.0.11.

[madshi]

This was solved in the meanwhile via email support. It seems that BugZilla 4 has a limited field size for the "Alias" field and madExcept was trying to write a too large value in there. This problem does not seem to exist with BugZilla 5. However, for the next build I may also have to clean up some characters which are not allowed in that field, either. Other than that, the feature appears to be working fine, though.

[GunterO]

You're welcome

I ran into another possible issue. But maybe I'm missing the whole concept here.
You're using the callstack CRC as alias field for BugZilla. This needs to be unique on the BugZilla server.
However, if some user run into the same bug, the callstack will be the same, and it can't report the bug to the server because the "Alias" is not unique.
One of our reasons to use BugZilla is to know how many times a particular bug occurs with our clients.
EurekaLog solves this via a custom field "Count":

""Count" field name" option specifies name of custom field, which EurekaLog will use for bug report counting. By default, BugZilla doesn't have any "occurrences" or "count" fields, so you can't know how many times bug has occurred. To workaround this problem, you can create a custom field in BugZilla configuration, which you will use for this purpose. You can enter name of this field here - and EurekaLog will use it to count bugs.

https://www.eurekalog.com/help/eurekalo ... gzilla.php

Is the same possible with madExcept?

Thanks!

[madshi]

It's currently not implemented, but I can add it. So I guess you would want it work like this:

1) Try to upload the bug report. If it fails:
2) Check if the error is "alias_in_use". If it is:
3) Modify the existing bug, read the counter field and increase it by one.

Correct? Do we really need to be able to define a custom name for that field? Maybe we could simply find a name that everybody could live with. I don't really want to complicate the settings dialog so much more to add a further edit box there, which would furthermore only apply to BugZilla.

[GunterO]

Yep, perfect!
No, I don't need a user configurable field. A fixed name is more then okay for me.

Thanks!

[madshi]

Ok, I'll put this on my to do list, but I'm not sure when I'll find time for this. You're the first user asking for this feature, so it's not highest priority right now, to be honest.

[GunterO]

I understand, but it would be a nice feature for everybody

[madshi]

Well, if you need/want it urgently, you can always implement it yourself and send the changes back to me. I'd be happy to integrate them into madExcept.pas... Yeah, yeah, I know, it's really my job. It's just that I've so many things on my to do list at the moment...

[GunterO]

indeed.

I fixed it at server side, in the BugZilla source code (Perl). I think this was easier then messing up your code.
But eventually, your solution will be better and easier to maintain (BugZilla updates, ...).