Re: [rt-users] vanished lines in rt 3.6.1 reply
Hello, --Am 12. Februar 2007 15:38:56 -0500 schrieb Kevin Falcone [EMAIL PROTECTED]: I've created a local ticket that looks something like this (by replying a lot) and haven't been able to replicate your problem. I, too, have reported such an error months ago. You will find the error description and the proof of the error in http://rt3.fsck.com/Ticket/Display.html?id=7539 (user: guest, password: guest) Dirk. ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] vanished lines in rt 3.6.1 reply
On Feb 6, 2007, at 7:12 AM, Sven Sternberger wrote: I now recognized the following: I create a ticket with a line which something like /^\w+/ RESULT: ok I reply on these transaction and enter again /^\w+/ RESULT: ok I reply on the reply transaction with an /^\w+/ RESULT: the newly entered line vanish So it is pretty clear that the quote mechanism is broken if you have more than one reply level Hi Sven I'm trying to duplicate this so that I can write a test and fix this, but I'm having trouble duplicating it. Are you replying in the web interface or in a mail client? I've created a local ticket that looks something like this (by replying a lot) and haven't been able to replicate your problem. bash foo bash2 bar cpan baz cpan foo cpan install Math::Trig frob foo foo Does this look like what you're seeing when lines disappear? It would be interesting to see the HTML of the page where cpan lines disappear Thanks -kevin ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] vanished lines in rt 3.6.1 reply
Hello! I'm surprised that i got no further reaction on my bug report (#8114), I think that the issue I reported is major bug because in our environment these vanished lines (even if they are in db) means data loss. Is this something only our installation suffers? I also wrote a bug report. But the open bug pages seems to be out of service: http://rt3.fsck.com//NoAuth/Buglist.html or are there really no bugs ;-) regards! sven On Fri, 2007-01-12 at 16:58 +0100, Sven Sternberger wrote: Hello! I upgraded the perl module Text::Quoted to the version 1.8, but the problem is still the same I tried to track down the problem, it only happens when I made a reply to an transaction, a reply to the ticket is always ok. The weird thing is that sometimes the first reply is okay but in the second reply the new entered lines are vanished again (the lines from the first try are still visible) It is not the word cpan which triggers the problem, but anything in the form /^\w+/ (this is an regexp). I now recognized the following: I create a ticket with a line which something like /^\w+/ RESULT: ok I reply on these transaction and enter again /^\w+/ RESULT: ok I reply on the reply transaction with an /^\w+/ RESULT: the newly entered line vanish So it is pretty clear that the quote mechanism is broken if you have more than one reply level best regards! sven ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] vanished lines in rt 3.6.1 reply
Hello! I upgraded the perl module Text::Quoted to the version 1.8, but the problem is still the same I tried to track down the problem, it only happens when I made a reply to an transaction, a reply to the ticket is always ok. The weird thing is that sometimes the first reply is okay but in the second reply the new entered lines are vanished again (the lines from the first try are still visible) It is not the word cpan which triggers the problem, but anything in the form /^\w+/ (this is an regexp). I now recognized the following: I create a ticket with a line which something like /^\w+/ RESULT: ok I reply on these transaction and enter again /^\w+/ RESULT: ok I reply on the reply transaction with an /^\w+/ RESULT: the newly entered line vanish So it is pretty clear that the quote mechanism is broken if you have more than one reply level best regards! sven ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
[rt-users] vanished lines in rt 3.6.1 reply
Hello! strange effect in our RT 3.6.1 installation. I entered the following lines in the web gui as reply: From the cmd-shell: perl -MCPAN -e shell cpan test Math::Trig (just to make sure I won't have to start from scratch again afterwards) cpan install Math::Trig That went ok as well ... I recognized that the lines which starts with cpan vanished in the ticket display. In the resulting email and with the command line client they show up. I tried to track down the problem, it only happens when I made a reply to an transaction, a reply to the ticket is always ok. The weird thing is that sometimes the first reply is okay but in the second reply the new entered lines are vanished again (the lines from the first try are still visible) It is not the word cpan which triggers the problem, but anything in the form /^\w+/ (this is an regexp). I use ScientificLinux 4 which is a recompiled version of RHEL4. regards sven Perl v5.8.5 under linux Apache2::Const v2.01; Apache2::Log v2.01; Apache2::RequestIO v2.01; Apache2::RequestRec v2.01; Apache2::RequestUtil v2.01; Apache2::Response v2.01; Apache2::ServerUtil v2.01; Apache2::Status v3.00; Apache::DBI v0.94; Apache::Session v1.6; Apache::Session::Generate::MD5 v2.1; Apache::Session::Lock::MySQL v1.00; Apache::Session::MySQL v1.01; Apache::Session::Serialize::Storable v1.00; Apache::Session::Store::DBI v1.02; Apache::Session::Store::MySQL v1.04; APR v0.009000; APR::Error v0.009000; APR::Pool v0.009000; APR::Table v0.009000; APR::Util v0.009000; AutoLoader v5.60; base v2.06; Benchmark v1.06; bytes v1.01; Cache::Simple::TimedExpiry v0.23; capitalization v0.03; Carp v1.03; CGI v3.11; CGI::Cookie v1.26; CGI::Util v1.5; Class::Container v0.11; Class::Data::Inheritable v0.02; Class::ReturnValue v0.51; Clone v0.18; constant v1.04; Cwd v2.19; Data::Dumper v2.121; Date::Format v2.22; Date::Parse v2.27; DBD::mysql v2.9004; DBI v1.40; DBIx::SearchBuilder v1.43; DBIx::SearchBuilder::Union v0; DBIx::SearchBuilder::Unique v0.01; Devel::StackTrace v1.11; Devel::StackTraceFrame v0.6; Devel::Symdump v2.05; Digest::base v1.00; Digest::MD5 v2.36; DynaLoader v1.05; Encode v2.01; Encode::Alias v2.00; Encode::Byte v2.00; Encode::Config v2.00; Encode::Encoding v2.00; Encode::Guess v2.00; Encode::Unicode v2.00; Errno v1.09; Exception::Class v1.19; Exception::Class::Base v1.2; Exporter v5.58; Exporter::Heavy v5.58; Fcntl v1.05; fields v2.03; File::Basename v2.73; File::Glob v1.03; File::Path v1.06; File::Spec v3.19; File::Spec::Unix v1.5; File::Temp v0.14; FileHandle v2.01; HTML::Element v3.16; HTML::Entities v1.27; HTML::Formatter v2.03; HTML::FormatText v2.01; HTML::Mason v1.3101; HTML::Mason::ApacheHandler v1.69; HTML::Mason::Exception v1.1; HTML::Mason::Exception::Abort v1.1; HTML::Mason::Exception::Compilation v1.1; HTML::Mason::Exception::Compilation::IncompatibleCompiler v1.1; HTML::Mason::Exception::Compiler v1.1; HTML::Mason::Exception::Decline v1.1; HTML::Mason::Exception::Params v1.1; HTML::Mason::Exception::Syntax v1.1; HTML::Mason::Exception::System v1.1; HTML::Mason::Exception::TopLevelNotFound v1.1; HTML::Mason::Exception::VirtualMethod v1.1; HTML::Mason::Exceptions v1.43; HTML::Parser v3.35; HTML::Scrubber v0.08; HTML::Tagset v3.03; HTML::TreeBuilder v3.18; HTTP::Date v1.46; I18N::LangTags v0.33; I18N::LangTags::Detect v1.03; integer v1.00; IO v1.21; IO::File v1.10; IO::Handle v1.24; IO::InnerFile v2.102 ; IO::Lines v2.103 ; IO::Scalar v2.105 ; IO::ScalarArray v2.103 ; IO::Seekable v1.09; IO::Wrap v2.102 ; IO::WrapTie v2.102 ; IPC::Open2 v1.01; IPC::Open3 v1.0106; lib v0.5565; List::Util v1.14; locale v1.00; Locale::Maketext v1.09; Locale::Maketext::Fuzzy v0.02; Locale::Maketext::Lexicon v0.36; Locale::Maketext::Lexicon::Gettext v0.11; Log::Dispatch v2.11; Log::Dispatch::Base v1.09; Log::Dispatch::File v1.22; Log::Dispatch::Output v1.26; Log::Dispatch::Screen v1.17; Log::Dispatch::Syslog v1.18; Mail::Address v1.62; Mail::Field v1.62; Mail::Field::AddrList v1.62; Mail::Field::Date v1.62; Mail::Header v1.62; Mail::Internet v1.62; MIME::Base64 v3.01; MIME::Body v5.403 ; MIME::Decoder v5.403 ; MIME::Decoder::Binary v5.403 ; MIME::Decoder::NBit v5.403 ; MIME::Decoder::QuotedPrint v5.403 ; MIME::Entity v5.404 ; MIME::Field::ContDisp v5.403 ; MIME::Field::ConTraEnc v5.403 ; MIME::Field::ContType v5.403 ; MIME::Field::ParamVal v5.403 ; MIME::Head v5.403 ; MIME::Parser v5.406 ; MIME::QuotedPrint v3.01; MIME::Tools v5.411 ; MIME::Words v5.404 ; mod_perl v2.01; mod_perl2 v2.01; ModPerl::Const v2.01; Module::Versions::Report v1.02; overload v1.01; Params::Validate v0.74; POSIX v1.08; re v0.04; Regexp::Common v2.120;
Re: [rt-users] vanished lines in rt 3.6.1 reply
On Thu, Jan 11, 2007 at 05:54:24PM +0100, Sven Sternberger wrote: Sven Hello! Sven Sven strange effect in our RT 3.6.1 installation. I entered the following Sven lines in the web gui as reply: The problem here is that CPAN looks an awful lot like a standard message quoting style. And RT uses a heuristic to figure out what text looks like it's quoted. : Sven Sven From the cmd-shell: perl -MCPAN -e shell Sven Sven cpan test Math::Trig Sven Sven (just to make sure I won't have to start from scratch again afterwards) Sven Sven cpan install Math::Trig Sven Sven That went ok as well ... Sven Sven Sven I recognized that the lines which starts with cpan vanished in the ticket display. Sven In the resulting email and with the command line client they show up. Sven Sven I tried to track down the problem, it only happens when I made a reply Sven to an transaction, a reply to the ticket is always ok. Sven The weird thing is that sometimes the first reply Sven is okay but in the second reply the new entered lines are vanished again Sven (the lines from the first try are still visible) Sven Sven It is not the word cpan which triggers the problem, but anything Sven in the form /^\w+/ (this is an regexp). Sven ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
