[Hamara-devel] bugzilla error, not able to file a bug.

[Anant]

in-line :-
On Monday 23 November 2015 02:48 PM, shirish wrote:
> addition at bottom :-
>
> On 11/23/2015 08:05 PM, shirish wrote:
>> at bottom :-
>>
>> On 11/23/2015 06:40 PM, shirish wrote:
>>> in-line :-
>>>
>>> On 11/23/2015 05:42 PM, Anant wrote:
>>>> Hi Shirish,
>>>
>>> Hi Anant,
>>>
>>>> I have created a test ticket, it is working fine for me. Can you
>>>> please
>>>> help me with some more inputs, in order to find the problem.
>>>
>>> I was trying to put up a bug about packaging an app. which I shared on
>>> hamara-devel last week. It had an unusual long description of two-three
>>> lines without break/sentence completion. I copied it as it was. When
>>> trying to submit got the above error.
>>>
>>> I *think* it might be due to a spam filter or something because spam
>>> *also* does have similar content like this. You might have to either
>>> toggle that switch or better yet, have the toggle with the condition
>>> that bugs made by registered *and* approved users shouldn't need to
>>> follow that rule.
I think there is nothing like spam filtering in bugzilla itself. So it
would not be the case here.
>>>
>>>> Thanks,
>>>> Anant
>>>>
>>>
>>> <snipped>
>>>
>
> Some more inputs from bugzilla-support on the above issue -
>
>
> It has nothing to do with long unbroken lines, but with character
> sets, Unicode and such stuff. Something went wrong in your case
> completely and you need to remember if you changed something
> currently, what it was, the text you input into the bug, if Bugzilla
> uses UTF-8 in your case or not...
>
> The problem in your case is really difficult: During sending mail
> messages some code expected to get an object with the "message"
> method, but got a string instead and therefore failed. But even the
> string already is an error message from Perl internals which tells us
> that some former caller expected to get bytes instead of a Unicode
> string. So I guess there was some unwanted stringification going on,
> producing the "Wide character..." error message and was passed down
> the line to somewhere where an object was expected and which
> ultimately failed.
>
> This shouldn't have happened, so you need to debug what went wrong in
> your case. Looking at your path it seems you used install-module.pl,
> which in my opinion should be avoided as much as possible. So I would
> start with looking if all the Bugzilla modules are available using
> your package manager and if so, delete lib/* and install the packages
> using your package manager. Try again and if that doesn't help you
> need to debug the mail sending code in Bugzilla to see where the
> problem occurs.
>
> It may even be some extension or such, because sending mails in core
> Bugzilla in 5.0.1 works for me and I do provide German Umlauts
> sometimes.
>
> > The basic query though is this, if somebody tries to put up a bug and
> > for some reason it is unable to record it (like the error above), is
> > there a mechanism to have a record of the bug which was tried to put
> > up ?
>
> No and this doesn't make much sense because there always can be an
> error for some reason in every line of code executed, like in your
> case above. This is something which simply doesn't work for your
> current environment, like if your hard drive runs out of space and
> wouldn't be even possible to record any bug information anymore.
>
> You just have to live with such things.
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
>
Can you please try again to create that bug, and let me know.

Thanks,