Re: ICLA — Gosha Arinich aka goshakkk

2016-08-30 Thread Sam Ruby 
On Tue, Aug 30, 2016 at 1:11 PM, Craig Russell  wrote:
> This morning I had a similar issue, but with the email:cc: !binary encoding.
>
> Patching the subject line handling doesn’t fix the cc line.
>
> I’m concerned that *any* UTF8 encoding of email fields will cause the same 
> issue.
>
> Can we find the place where the !binary encoding is chosen instead of 
> “normal” UTF8?

It presumably would be here:

https://github.com/apache/whimsy/blob/5b3fff5fffeb98027a3e6201e38c2a0dc725d19b/www/secretary/workbench/file.cgi#L55

What bothers me most is that this generally worked in the past and I
don't know of anything that changed recently that could have affected
this.

I continue to maintain that the overall process (extracted from the
email with one program, results saved into a number of svn properties,
to later be extracted by parsing the results of the svn command line,
with the results inserted into an outbound email) is fragile.

Patching the secretary workbench until it works again (for a while?)
is possible, but I encourage you to find the exact email that you had
a problem with here: https://whimsy.apache.org/secmail/, click on both
raw and then headers and see the results.

With secmail, the raw email is retained on the server, and the process
is parse raw email, insert results into outbound email.  Not only are
there less moving parts, but (a) if there is a problem you can see the
intermediate results on the server, (b) any fixes that are made will
effectively be applied retroactively as the new parsing will be done
against the original (raw) message, and (c) I have a script
(parsemail.rb) that will download and parse all emails that have ever
been archived for secretary@ and run parse against them.

> Thanks,
>
> Craig

- Sam Ruby

>> On Aug 28, 2016, at 5:37 PM, Sam Ruby  wrote:
>>
>> On Sun, Aug 28, 2016 at 8:04 PM, Craig Russell  
>> wrote:
>>> Can you please take a look and see why the rescue didn’t work?
>>
>> Logs can be found here:
>>
>> https://whimsy.apache.org/members/log/
>>
>> In particular, https://whimsy.apache.org/members/log/whimsy_error.log
>>
>> What I am still seeing is:
>>
>> _ERROR #> to UTF-8>, referer:
>> https://whimsy.apache.org/secretary/workbench/file.cgi
>>
>> And further up the stack traceback:
>>
>> _WARN   
>> /usr/local/rvm/gems/ruby-2.3.1/gems/mail-2.6.4/lib/mail/message.rb:1887:in
>> `to_s', referer:
>> https://whimsy.apache.org/secretary/workbench/file.cgi
>> _WARN   /x1/srv/whimsy/www/secretary/workbench/file.cgi:318:in `block
>> in send_email', referer:
>> https://whimsy.apache.org/secretary/workbench/file.cgi
>>
>> So, you are not hitting the exception handler, and you are dying later
>> when trying to convert the message (which includes a binary subject)
>> into a string.
>>
>> The reason why you are not hitting the exception handler is that you
>> are not calling force_encoding.  A second problem is that if an
>> exception were to be raised, you wouldn't be catching it as the
>> exception needs to be qualified: Encoding::UndefinedConversionError
>>
>>> Thanks,
>>>
>>> Craig
>>
>> - Sam Ruby
>>
 On Aug 28, 2016, at 4:30 PM, Sam Ruby  wrote:

 On Sun, Aug 28, 2016 at 6:15 PM, Craig Russell  
 wrote:
> I’m blind here. I can’t see the pending.yml. I can’t see the error 
> console. I don’t even know if my change was pushed to production.
>
> What tools do I need to see what’s going on?

 What code is actually deployed can be seen on the last two lines of
 the status page: https://whimsy.apache.org/status/

 Nothing in the (current) workbench shows the raw contents of
 pending.yml.  It would be easy to add as a new CGI script.  It could
 even be added as a new action in file.cgi.

 Alternately, we could ask for you to be added to have shell access to
 whimsy-vm3.

> Thanks,
>
> Craig

 - Sam Ruby

>> On Aug 28, 2016, at 2:30 PM, Craig Russell  
>> wrote:
>>
>>>
>>> On Aug 28, 2016, at 6:04 AM, Sam Ruby  wrote:
>>>
>>> On Sat, Aug 27, 2016 at 11:23 PM, Craig Russell
>>>  wrote:
 The processing of email::subject seems to be localized to file.cgi ca. 
 261

   # override subject?
   if vars.email_subject and !vars.email_subject.empty?
 if vars.email_subject =~ /^re:\s/i
   subject vars.email_subject
 else
   subject 'Re: ' + vars.email_subject
 end
   end

 I can’t see where the actual problem is, but is there a way to either;

 1. have whichever component created vars.email_subject recognize UTF-8 
 characters and pass them as characters instead of binary

Re: ICLA — Gosha Arinich aka goshakkk

2016-08-30 Thread Craig Russell 
This morning I had a similar issue, but with the email:cc: !binary encoding. 

Patching the subject line handling doesn’t fix the cc line.

I’m concerned that *any* UTF8 encoding of email fields will cause the same 
issue. 

Can we find the place where the !binary encoding is chosen instead of “normal” 
UTF8?

Thanks,

Craig

> On Aug 28, 2016, at 5:37 PM, Sam Ruby  wrote:
> 
> On Sun, Aug 28, 2016 at 8:04 PM, Craig Russell  
> wrote:
>> Can you please take a look and see why the rescue didn’t work?
> 
> Logs can be found here:
> 
> https://whimsy.apache.org/members/log/
> 
> In particular, https://whimsy.apache.org/members/log/whimsy_error.log
> 
> What I am still seeing is:
> 
> _ERROR # to UTF-8>, referer:
> https://whimsy.apache.org/secretary/workbench/file.cgi
> 
> And further up the stack traceback:
> 
> _WARN   
> /usr/local/rvm/gems/ruby-2.3.1/gems/mail-2.6.4/lib/mail/message.rb:1887:in
> `to_s', referer:
> https://whimsy.apache.org/secretary/workbench/file.cgi
> _WARN   /x1/srv/whimsy/www/secretary/workbench/file.cgi:318:in `block
> in send_email', referer:
> https://whimsy.apache.org/secretary/workbench/file.cgi
> 
> So, you are not hitting the exception handler, and you are dying later
> when trying to convert the message (which includes a binary subject)
> into a string.
> 
> The reason why you are not hitting the exception handler is that you
> are not calling force_encoding.  A second problem is that if an
> exception were to be raised, you wouldn't be catching it as the
> exception needs to be qualified: Encoding::UndefinedConversionError
> 
>> Thanks,
>> 
>> Craig
> 
> - Sam Ruby
> 
>>> On Aug 28, 2016, at 4:30 PM, Sam Ruby  wrote:
>>> 
>>> On Sun, Aug 28, 2016 at 6:15 PM, Craig Russell  
>>> wrote:
 I’m blind here. I can’t see the pending.yml. I can’t see the error 
 console. I don’t even know if my change was pushed to production.
 
 What tools do I need to see what’s going on?
>>> 
>>> What code is actually deployed can be seen on the last two lines of
>>> the status page: https://whimsy.apache.org/status/
>>> 
>>> Nothing in the (current) workbench shows the raw contents of
>>> pending.yml.  It would be easy to add as a new CGI script.  It could
>>> even be added as a new action in file.cgi.
>>> 
>>> Alternately, we could ask for you to be added to have shell access to
>>> whimsy-vm3.
>>> 
 Thanks,
 
 Craig
>>> 
>>> - Sam Ruby
>>> 
> On Aug 28, 2016, at 2:30 PM, Craig Russell  
> wrote:
> 
>> 
>> On Aug 28, 2016, at 6:04 AM, Sam Ruby  wrote:
>> 
>> On Sat, Aug 27, 2016 at 11:23 PM, Craig Russell
>>  wrote:
>>> The processing of email::subject seems to be localized to file.cgi ca. 
>>> 261
>>> 
>>>   # override subject?
>>>   if vars.email_subject and !vars.email_subject.empty?
>>> if vars.email_subject =~ /^re:\s/i
>>>   subject vars.email_subject
>>> else
>>>   subject 'Re: ' + vars.email_subject
>>> end
>>>   end
>>> 
>>> I can’t see where the actual problem is, but is there a way to either;
>>> 
>>> 1. have whichever component created vars.email_subject recognize UTF-8 
>>> characters and pass them as characters instead of binary
>>> 
>>> 2. recognize that this has happened here and replace the subject with 
>>> an innocuous subject based on the document type.
>> 
>> All of your analysis seems to be on target.
>> 
>> This is from the log:
>> 
>> [Sat Aug 27 18:36:03.233539 2016] [cgi:error] [pid 3570:tid
>> 139833343252224] [client 73.15.26.163:62667] AH01215: _ERROR
>> #> UTF-8>, referer:
>> https://whimsy.apache.org/secretary/workbench/file.cgi
>> 
>> Looking at pending.yml with the interactive ruby shell:
>> 
>> $ irb
>> irb(main):001:0> require 'yaml'
>> => true
>> irb(main):002:0> pending = YAML.load_file('pending.yml')
>> => [{"doctype"=>"icla",
>> "source"=>"Gosha-Arinich-me-goshakkk.name--icla.pdf",
>> "realname"=>"Heorhi Arynich", "pubname"=>"Gosha Arinich",
>> "email"=>"m...@goshakkk.name", "filename"=>"heorhi-arynich.pdf",
>> "nname"=>"Gosha Arinich", "nemail"=>"m...@goshakkk.name",
>> "iname"=>"Gosha Arinich", "iemail"=>"m...@goshakkk.name",
>> "uname"=>"Gosha Arinich", "uemail"=>"m...@goshakkk.name",
>> "pname"=>"Gosha Arinich", "pemail"=>"m...@goshakkk.name",
>> "memail"=>"m...@goshakkk.name", "gname"=>"Gosha Arinich",
>> "gemail"=>"m...@goshakkk.name", "contact"=>"Gosha Arinich",
>> "cemail"=>"m...@goshakkk.name", "ipodling"=>" ",
>> "email:addr"=>"m...@goshakkk.name",
>> "email:id"=>"",
>> "email:name"=>"Gosha Arinich",

RECOVERY: whimsy.apache.org (whimsy.apache.org (https)) is back up!

2016-08-30 Thread Ping My Box 

Hello,
The https service at whimsy.apache.org (whimsy.apache.org (https)) seems to be 
back in working order again.

With regards,
Ping My Box - https://www.pingmybox.com/

ALERT: whimsy.apache.org (whimsy.apache.org (https)) is DOWN!

2016-08-30 Thread Ping My Box 

Hello,
The https service at whimsy.apache.org (whimsy.apache.org (https)) has been 
reported as down by our monitoring system:

Component:  response
Error code: Internal Server Error or equivalent bad message received: HTTP/1.1 
400 svn iclas ["svn: E000110: Unable to connect to a repository at URL 
'https://svn.apache.org/repos/private/documents/iclas'", "svn: E000110: Error 
running context: Connection timed out"]
Debug output:
--
[Tue Aug 30 06:27:16 2016]: Initialising socket
[Tue Aug 30 06:27:16 2016]: Looking up hostname whimsy.apache.org...
[Tue Aug 30 06:27:16 2016]: Connecting to 207.244.88.137:443
[Tue Aug 30 06:27:17 2016]: Connected, sending HTTPS payload.
[Tue Aug 30 06:27:17 2016]: Reading response header from server
[Tue Aug 30 06:27:41 2016]: Caught exception: Internal Server Error or 
equivalent bad message received: HTTP/1.1 400 svn iclas ["svn: E000110: Unable 
to connect to a repository at URL 
'https://svn.apache.org/repos/private/documents/iclas'", "svn: E000110: Error 
running context: Connection timed out"]


--

With regards,
Ping My Box - https://www.pingmybox.com/