On Wed, Jul 26, 2017 at 7:55 PM, Craig Russell <[email protected]> wrote:
> Still no joy.
>
> Go to adjournment. Am I the only one who can see the "Establish pmcs" still 
> available (not done)?
>
> Am I the only one who cannot see "Add to pmc-chairs" action either available 
> or done?

I'm back from vacation.

The actions have been taken; even though some originally failed, and
were completed manually.  This left the meta-data for this month in an
inconsistent state.  I can manually correct that, is there a reason
for me to do so?

The reason "Add to pmc-chairs" doesn't show up is that there aren't
any new chairs that aren't already chairs.  Under normal conditions,
the reason why this would be the case is that each of these
individuals are chairs of another committee.

The reason "Add to pmc-chairs" isn't listed as done is that the action
failed before it could update the "done" list.

- Sam Ruby

> Craig
>
>> On Jul 21, 2017, at 1:02 PM, Craig Russell <[email protected]> wrote:
>>
>> Go to adjournment. Still no Completed action for adding new pmc chair.
>>
>> Establish pmcs fails:
>>
>> {
>>  "transcript": [
>>    "$ svn checkout --depth empty --non-interactive 
>> https://svn.apache.org/repos/private/committers/board 
>> /tmp/d20170721-14246-8gao8k",
>>    "Checked out revision 77906.",
>>    "",
>>    "$ svn update --non-interactive 
>> /tmp/d20170721-14246-8gao8k/committee-info.txt",
>>    "Updating '/tmp/d20170721-14246-8gao8k/committee-info.txt':",
>>    "A    /tmp/d20170721-14246-8gao8k/committee-info.txt",
>>    "Updated to revision 77906.",
>>    "",
>>    "$ svn commit /tmp/d20170721-14246-8gao8k/committee-info.txt 
>> --non-interactive --message Establish\\ MADlib"
>>  ],
>>  "exception": "#<NoMethodError: undefined method `id' for 
>> \"MADlib\":String>",
>>  "backtrace": [
>>    "/x1/srv/whimsy/www/board/agenda/views/actions/todos.json.rb:123:in 
>> `block (2 levels) in _evaluate'",
>>    "/x1/srv/whimsy/lib/whimsy/asf/ldap.rb:140:in `bind'",
>>    "/x1/srv/whimsy/lib/whimsy/asf/ldap.rb:140:in `bind'",
>>    "/x1/srv/whimsy/www/board/agenda/views/actions/todos.json.rb:121:in 
>> `block in _evaluate'",
>>    "/x1/srv/whimsy/www/board/agenda/views/actions/todos.json.rb:108:in 
>> `each'",
>>    "/x1/srv/whimsy/www/board/agenda/views/actions/todos.json.rb:108:in 
>> `_evaluate'",
>>    "/x1/srv/whimsy/www/board/agenda/routes.rb:272:in `block in <top 
>> (required)>'",
>>    "/x1/srv/whimsy/lib/whimsy/asf/rack.rb:220:in `call'",
>>    "/x1/srv/whimsy/lib/whimsy/asf/rack.rb:197:in `call'",
>>    "/x1/srv/whimsy/lib/whimsy/asf/rack.rb:251:in `call'",
>>    "/x1/srv/whimsy/lib/whimsy/asf/rack.rb:76:in `call'",
>>    
>> "/usr/local/rvm/gems/ruby-2.4.1/gems/passenger-5.1.2/src/ruby_supportlib/phusion_passenger/rack/thread_handler_extension.rb:97:in
>>  `process_request'",
>>    
>> "/usr/local/rvm/gems/ruby-2.4.1/gems/passenger-5.1.2/src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:160:in
>>  `accept_and_process_next_request'",
>>    
>> "/usr/local/rvm/gems/ruby-2.4.1/gems/passenger-5.1.2/src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:113:in
>>  `main_loop'",
>>    
>> "/usr/local/rvm/gems/ruby-2.4.1/gems/passenger-5.1.2/src/ruby_supportlib/phusion_passenger/request_handler.rb:416:in
>>  `block (3 levels) in start_threads'",
>>    
>> "/usr/local/rvm/gems/ruby-2.4.1/gems/passenger-5.1.2/src/ruby_supportlib/phusion_passenger/utils.rb:113:in
>>  `block in create_thread_and_abort_on_exception'"
>>  ]
>> }
>>> On Jul 21, 2017, at 8:23 AM, Sam Ruby <[email protected]> wrote:
>>>
>>> Found the syntax error and fixed it.  Created the "victims" file for
>>> the infrastructure tooling.
>>>
>>> - Sam Ruby
>>>
>>> On Thu, Jul 20, 2017 at 12:50 PM, Sam Ruby <[email protected]> wrote:
>>>> I probably won't be able to look at it until tomorrow but that traceback
>>>> should be very helpful.  Thanks!
>>>>
>>>> On Jul 20, 2017 12:41 PM, "Craig Russell" <[email protected]> wrote:
>>>>>
>>>>> Hi Sam,
>>>>>
>>>>>
>>>>>> On Jul 20, 2017, at 7:55 AM, Sam Ruby <[email protected]> wrote:
>>>>>>
>>>>>> On Wed, Jul 19, 2017 at 4:15 PM, Craig Russell <[email protected]>
>>>>>> wrote:
>>>>>>>
>>>>>>>> On Jul 19, 2017, at 1:08 PM, Sam Ruby <[email protected]> wrote:
>>>>>>>>
>>>>>>>> On Wed, Jul 19, 2017 at 3:59 PM, Craig Russell <[email protected]>
>>>>>>>> wrote:
>>>>>>>>> Today's board meeting adjournment results:
>>>>>>>>>
>>>>>>>>> New PMC chairs got half the job done. Chairs were added to LDAP
>>>>>>>>> pmc-chairs; mail to new pmc chairs didn't apparently go out so I sent 
>>>>>>>>> it
>>>>>>>>> manually.
>>>>>>>>
>>>>>>>> Fixed.
>>>>>
>>>>> This item seems to be in limbo. There is no action to "add new pmc
>>>>> chairs". It's just gone.
>>>>>
>>>>>>>>
>>>>>>>>> Establish pmcs: apparently done except chair was not identified per
>>>>>>>>> whimsy
>>>>>
>>>>> There is still an action "Establish pmcs" and it still errors out with [1]
>>>>> see below.
>>>>>>>>
>>>>>>>> I don't understand what you are trying to say here.  Can you clarify?
>>>>>>>
>>>>>>> I looked at https://whimsy.apache.org/roster/committee/streams and
>>>>>>> https://whimsy.apache.org/roster/committee/fluo and
>>>>>>> https://whimsy.apache.org/roster/committee/madlib and they are all
>>>>>>> identified as PMCs but none have a chair identified. No <== chair
>>>>>>
>>>>>> I went to take a look at the code that does this, and didn't find any.
>>>>>> Then I went and checked the svn logs to see how it was done in the
>>>>>> past.  It seems that Brett does this manually after the meeting.  It
>>>>>> just hasn't been done yet.
>>>>>>
>>>>>> This does seem ripe for automation.
>>>>>
>>>>> I agree. The code that creates the lines in committee-info.txt can
>>>>> annotate the chair.
>>>>>>
>>>>>>>>> Completed actions: doesn't show new pmc chair action
>>>>>>>>
>>>>>>>> It didn't complete :-)
>>>>>>>
>>>>>>> But it's not available as a Post Meeting Action to-do either.
>>>>>>>
>>>>>>> And Establish pmcs did complete (see above; is anything still not
>>>>>>> done?) but is still listed as a to-do.
>>>>>>
>>>>>> I made a fix anticipating that you would retry the todo; but I must
>>>>>> not have communicated that well as you chose to send out the emails.
>>>>>
>>>>> There is no action possible in the Adjournment page of the agenda tool. I
>>>>> think there is still room for improvement now. The code that detects that 
>>>>> it
>>>>> should present an action thinks that it's been done. The code that shows 
>>>>> it
>>>>> as done thinks that it is not done. One or both of these is still broken.
>>>>>
>>>>> Go to this page and see if you see that:
>>>>> Establish pmcs still wants me to Submit
>>>>>
>>>>> Completed Actions includes:
>>>>> Removed from pmc chairs
>>>>> Sent feedback
>>>>>
>>>>>> At this point, we should probably leave this be and try again next
>>>>>> month.
>>>>>
>>>>> I don't know why Establish pmcs is still pending
>>>>> Add new pmc chairs is missing in action
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Craig
>>>>>>
>>>>>>>>> I'll do mail feedback later today.
>>>>>>>>
>>>>>>>> Cool, and I'll post June minutes in the next day or so.
>>>>>
>>>>> [1] [Log] { (app.js, line 336)
>>>>> "transcript": [
>>>>>   "$ svn checkout --depth empty --non-interactive
>>>>> https://svn.apache.org/repos/private/committers/board
>>>>> /tmp/d20170720-28126-10dt4nv",
>>>>>   "Checked out revision 77881.",
>>>>>   "",
>>>>>   "$ svn update --non-interactive
>>>>> /tmp/d20170720-28126-10dt4nv/committee-info.txt",
>>>>>   "Updating '/tmp/d20170720-28126-10dt4nv/committee-info.txt':",
>>>>>   "A    /tmp/d20170720-28126-10dt4nv/committee-info.txt",
>>>>>   "Updated to revision 77881.",
>>>>>   "",
>>>>>   "$ svn commit /tmp/d20170720-28126-10dt4nv/committee-info.txt
>>>>> --non-interactive --message Establish\\ MADlib",
>>>>>   "",
>>>>>   "$ svn checkout --depth empty --non-interactive
>>>>> https://svn.apache.org/repos/private/committers/board
>>>>> /tmp/d20170720-28126-1hzfbvj",
>>>>>   "Checked out revision 77881.",
>>>>>   "",
>>>>>   "$ svn update --non-interactive
>>>>> /tmp/d20170720-28126-1hzfbvj/committee-info.txt",
>>>>>   "Updating '/tmp/d20170720-28126-1hzfbvj/committee-info.txt':",
>>>>>   "A    /tmp/d20170720-28126-1hzfbvj/committee-info.txt",
>>>>>   "Updated to revision 77881.",
>>>>>   "",
>>>>>   "$ svn commit /tmp/d20170720-28126-1hzfbvj/committee-info.txt
>>>>> --non-interactive --message Establish\\ Streams",
>>>>>   "",
>>>>>   "$ svn checkout --depth empty --non-interactive
>>>>> https://svn.apache.org/repos/private/committers/board
>>>>> /tmp/d20170720-28126-1oek1x9",
>>>>>   "Checked out revision 77881.",
>>>>>   "",
>>>>>   "$ svn update --non-interactive
>>>>> /tmp/d20170720-28126-1oek1x9/committee-info.txt",
>>>>>   "Updating '/tmp/d20170720-28126-1oek1x9/committee-info.txt':",
>>>>>   "A    /tmp/d20170720-28126-1oek1x9/committee-info.txt",
>>>>>   "Updated to revision 77881.",
>>>>>   "",
>>>>>   "$ svn commit /tmp/d20170720-28126-1oek1x9/committee-info.txt
>>>>> --non-interactive --message Establish\\ Fluo"
>>>>> ],
>>>>> "exception": "#<NoMethodError: undefined method `update' for
>>>>> :SVN:Symbol>",
>>>>> "backtrace": [
>>>>>   "/x1/srv/whimsy/www/board/agenda/views/actions/todos.json.rb:137:in
>>>>> `_evaluate'",
>>>>>   "/x1/srv/whimsy/www/board/agenda/routes.rb:272:in `block in <top
>>>>> (required)>'",
>>>>>   "/x1/srv/whimsy/lib/whimsy/asf/rack.rb:220:in `call'",
>>>>>   "/x1/srv/whimsy/lib/whimsy/asf/rack.rb:197:in `call'",
>>>>>   "/x1/srv/whimsy/lib/whimsy/asf/rack.rb:251:in `call'",
>>>>>   "/x1/srv/whimsy/lib/whimsy/asf/rack.rb:76:in `call'",
>>>>>
>>>>> "/usr/local/rvm/gems/ruby-2.4.1/gems/passenger-5.1.2/src/ruby_supportlib/phusion_passenger/rack/thread_handler_extension.rb:97:in
>>>>> `process_request'",
>>>>>
>>>>> "/usr/local/rvm/gems/ruby-2.4.1/gems/passenger-5.1.2/src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:160:in
>>>>> `accept_and_process_next_request'",
>>>>>
>>>>> "/usr/local/rvm/gems/ruby-2.4.1/gems/passenger-5.1.2/src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:113:in
>>>>> `main_loop'",
>>>>>
>>>>> "/usr/local/rvm/gems/ruby-2.4.1/gems/passenger-5.1.2/src/ruby_supportlib/phusion_passenger/request_handler.rb:416:in
>>>>> `block (3 levels) in start_threads'",
>>>>>
>>>>> "/usr/local/rvm/gems/ruby-2.4.1/gems/passenger-5.1.2/src/ruby_supportlib/phusion_passenger/utils.rb:113:in
>>>>> `block in create_thread_and_abort_on_exception'"
>>>>> ]
>>>>> }
>>>>>
>>>>>>>>
>>>>>>>>> Craig L Russell
>>>>>>>>> Secretary, Apache Software Foundation
>>>>>>>>> [email protected] http://db.apache.org/jdo
>>>>>>>>
>>>>>>>> - Sam Ruby
>>>>>>>
>>>>>>> Craig L Russell
>>>>>>> Secretary, Apache Software Foundation
>>>>>>> [email protected] http://db.apache.org/jdo
>>>>>
>>>>> Craig L Russell
>>>>> Secretary, Apache Software Foundation
>>>>> [email protected] http://db.apache.org/jdo
>>>>>
>>>>
>>
>> Craig L Russell
>> Secretary, Apache Software Foundation
>> [email protected] http://db.apache.org/jdo
>>
>
> Craig L Russell
> Secretary, Apache Software Foundation
> [email protected] http://db.apache.org/jdo
>

Reply via email to