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/
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 public_json ldap-committees "2016-04-11 02:02:02 +
[ldaps://
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/
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 public_json ldap-groups "2016-04-11 01:36:01 +
[ldaps://ldap
On Sun, Apr 10, 2016 at 9:20 PM, sebb wrote:
> The pmc chairs LDAP group gives karma to update the LDAP groups for
> any PMC, not just ones own. However Whimsy only enables the update
> buttons for the PMC chair.
>
> Historically when a PMC chair is unavailable, the rest of PMC has been
> able to
[
https://issues.apache.org/jira/browse/WHIMSY-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234393#comment-15234393
]
Sam Ruby commented on WHIMSY-56:
I think we are saying the same thing. In particular, note
On 11 April 2016 at 02:22, John D. Ament wrote:
> +1
> You also have the case of AD&D that may require outside input.
AD&D?
Not sure what it has to do with Dungeons and Dragons...!
> On Sun, Apr 10, 2016 at 9:21 PM sebb wrote:
>
>> The pmc chairs LDAP group gives karma to update the LDAP group
+1
You also have the case of AD&D that may require outside input.
On Sun, Apr 10, 2016 at 9:21 PM sebb wrote:
> The pmc chairs LDAP group gives karma to update the LDAP groups for
> any PMC, not just ones own. However Whimsy only enables the update
> buttons for the PMC chair.
>
> Historically w
The pmc chairs LDAP group gives karma to update the LDAP groups for
any PMC, not just ones own. However Whimsy only enables the update
buttons for the PMC chair.
Historically when a PMC chair is unavailable, the rest of PMC has been
able to call on another chair to do the update. Maybe this should
[
https://issues.apache.org/jira/browse/WHIMSY-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234389#comment-15234389
]
Sebb commented on WHIMSY-56:
That works for me.
Except the update of the chair: I think that h
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/
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 public_json ldap-committees "2016-04-11 00:47:01 +
[ldaps://
[
https://issues.apache.org/jira/browse/WHIMSY-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234379#comment-15234379
]
Sam Ruby commented on WHIMSY-56:
As to your last comment, I don't see a reason to optimize
Sebb created WHIMSY-56:
--
Summary: Project Chair change resolution
Key: WHIMSY-56
URL: https://issues.apache.org/jira/browse/WHIMSY-56
Project: Whimsy
Issue Type: Wish
Reporter: Sebb
Might
On Sun, Apr 10, 2016 at 7:10 PM, John D. Ament wrote:
> I saw the change to the board report. Just curious, why is there a
> shortened form displayed on the report?
Short version of the answer: to make the text that shows up in the
browser tab meaningful.
Of course, there isn't any strong requi
I saw the change to the board report. Just curious, why is there a
shortened form displayed on the report?
John
On Sun, Apr 10, 2016 at 6:43 PM Sam Ruby wrote:
> On Sun, Apr 10, 2016 at 4:33 PM, John D. Ament
> wrote:
> > Well, there's definitely something up w/ the johnzon report. Now I get
[
https://issues.apache.org/jira/browse/WHIMSY-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234318#comment-15234318
]
Sam Ruby commented on WHIMSY-27:
Root cause: server was expecting the client to pass up the
[
https://issues.apache.org/jira/browse/WHIMSY-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Ruby reassigned WHIMSY-27:
--
Assignee: Sam Ruby
> Updating a resolution during a board meeting fails silently
> -
On Sun, Apr 10, 2016 at 4:33 PM, John D. Ament wrote:
> Well, there's definitely something up w/ the johnzon report. Now I get this
There were two bugs, only one was unique to the johnzon resolution.
Both are fixed now, and I've deployed and verified the fixes. And I
made a fix to the title of
[
https://issues.apache.org/jira/browse/WHIMSY-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234307#comment-15234307
]
Sebb commented on WHIMSY-28:
I suspect that many people only want to vote on the entire resolut
[
https://issues.apache.org/jira/browse/WHIMSY-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234282#comment-15234282
]
Sam Ruby commented on WHIMSY-28:
If you go to the current resolutions in the agenda tool, y
[
https://issues.apache.org/jira/browse/WHIMSY-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234280#comment-15234280
]
Sebb commented on WHIMSY-28:
I assume that validity of names encompasses checking the ASF e-mai
Well, there's definitely something up w/ the johnzon report. Now I get this
{
"transcript": [
"$ svn checkout --depth empty
https://svn.apache.org/repos/private/foundation/board
/tmp/d20160410-17871-1n4xpey",
" U /tmp/d20160410-17871-1n4xpey",
"Checked out revision 67660.",
"$
Cool, thanks, I'll give it a shot later.
On Sun, Apr 10, 2016 at 7:59 AM sebb wrote:
> Should be fixed now.
>
> On 10 April 2016 at 09:42, sebb wrote:
> > Looks like that app has not been fully migrated from the original whimsy
> host.
> >
> > If it's urgent, you could try using whimsy-old.apac
Thanks for the stack traceback!
Unfortunately, what I can glean from the traceback is that a commit
was NOT attempted, and the code treated that as a commit failure and
retried the operation until the retry count was exceeded; at which
point it claimed that there was a commit failure.
I've update
[
https://issues.apache.org/jira/browse/WHIMSY-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234192#comment-15234192
]
Sam Ruby commented on WHIMSY-28:
[~curc...@apache.org] perhaps those should be separate JIR
Should be fixed now.
On 10 April 2016 at 09:42, sebb wrote:
> Looks like that app has not been fully migrated from the original whimsy host.
>
> If it's urgent, you could try using whimsy-old.apache.org instead for
> that service.
>
> On 9 April 2016 at 21:06, John D. Ament wrote:
>> Tried to su
Looks like that app has not been fully migrated from the original whimsy host.
If it's urgent, you could try using whimsy-old.apache.org instead for
that service.
On 9 April 2016 at 21:06, John D. Ament wrote:
> Tried to subscribe myself to incubator-wave-private
>
> #
> /srv/whimsy/www/commit
28 matches
Mail list logo
