Submit queue ui is borken about contrib HOT 7 CLOSED

When I access it now I don't get an error but all the fields are blank (I just get the section headings).
I assume you are talking about http://submit-queue.k8s.io/

from contrib.

@brendandburns did you change something? I'll look at this later today if I
don't hear anything.

On Fri, Sep 11, 2015 at 11:43 PM, David Oppenheimer <
[email protected]> wrote:

When I access it now I don't get an error but all the fields are blank (I
just get the section headings).
I assume you are talking about http://submit-queue.k8s.io/

—
Reply to this email directly or view it on GitHub
#78 (comment).

from contrib.

I didn't change anything since wed. I'm looking at it now though...

from contrib.

Broken again?

from contrib.

Yeah, it's the same thing. For the life of me I have no idea what is causing it. The error is b/c we're trying to json serialize a channel object, but I have no idea where that channel is stored, or what causes it to happen.

I bounced the job and it's back. I'll add a health check so that it automatically restarts to stop the bleeding, but we should figure out why its happening.

from contrib.

Yeah, just FYI, the health check isn't catching this.

On Wed, Sep 16, 2015 at 7:43 PM, Brendan Burns [email protected]
wrote:

Yeah, it's the same thing. For the life of me I have no idea what is
causing it. The error is b/c we're trying to json serialize a channel
object, but I have no idea where that channel is stored, or what causes
it to happen.

I bounced the job and it's back. I'll add a health check so that it
automatically restarts to stop the bleeding, but we should figure out why
its happening.

—
Reply to this email directly or view it on GitHub
#78 (comment).

from contrib.

haven't added it yet :P

On Thu, Sep 17, 2015 at 1:52 PM, Daniel Smith [email protected]
wrote:

Yeah, just FYI, the health check isn't catching this.

On Wed, Sep 16, 2015 at 7:43 PM, Brendan Burns [email protected]
wrote:

Yeah, it's the same thing. For the life of me I have no idea what is
causing it. The error is b/c we're trying to json serialize a channel
object, but I have no idea where that channel is stored, or what causes
it to happen.

I bounced the job and it's back. I'll add a health check so that it
automatically restarts to stop the bleeding, but we should figure out why
its happening.

—
Reply to this email directly or view it on GitHub
<#78 (comment)
.

—
Reply to this email directly or view it on GitHub
#78 (comment).

from contrib.