[Systems] developer.sugarlabs.org update hook unresponsive

James Cameron quozl at laptop.org
Sun Oct 1 23:15:13 EDT 2017


Thanks.  Site has updated.

On Sun, Oct 01, 2017 at 11:47:41PM -0300, Samuel Cantero wrote:
> On Sun, Oct 1, 2017 at 11:41 PM, James Cameron <[1]quozl at laptop.org> wrote:
> 
>     Okay, thanks.  Where's the flask app?  What's the building bot?
> 
> The code in charge of managing the hook is in freedom and it is not using kafka
> anymore. Maybe I called it wrong. I just named it "building bot" but apparently
> it was more confusing.
> 
>     It looked to me that Kafka on freedom port 9092 was meant to make this
>     async anyway;
> 
>     [2]https://github.com/sugarlabs-infra/help-rebuilder/blob/master/main.py
> 
> It was replaced (I suppose by SamP). I can see it was using kafka before: [3]
> https://github.com/sugarlabs-infra/developer-rebuilder/blob/master/main.py
> 
> Anyway, I will replace it now by this [4]https://gist.github.com/scanterog/
> 8639b74d1ba077f132675e9712465cf3
> 
> Maybe not very elegant but it should do the job. I will replace image/container
> now and test it.
> 
>     But I don't know what triggers the message from Kafka.
> 
>     If there's still a sugar-buildbot instance from back in Daniel Narvaez
>     days, I think we aren't using it and it might be time to turn it off.
> 
>     [5]http://buildbot.sugarlabs.org/ is down.
>    
>     On Sun, Oct 01, 2017 at 11:18:34PM -0300, Samuel Cantero wrote:
>     > I've recently checked it and I see the following as error:
>     >
>     >   File "/usr/local/lib/python2.7/socket.py", line 307, in flush
>     >     self._sock.sendall(view[write_offset:write_offset+buffer_size])
>     > socket.error: [Errno 32] Broken pipe
>     >
>     > This is due the python process (flask app) has received SIGPIPE signal
>     which
>     > means in this case GitHub has closed the connection. I think GH timeout
>     is only
>     > 1 sec and our building bot is taking more time. We need to reply to GH
>     when the
>     > payload arrives and then continue processing in background (async mode).
>     We
>     > might replace flask by aiohttp. Using celery is too overkill for this.
>     >
>     > Best,
>     >
>     > On Sun, Oct 1, 2017 at 10:10 PM, James Cameron <[1][6]quozl at laptop.org>
>     wrote:
>     >
>     >     Two recent commits by Walter and I have not updated
>     >     [2][7]https://developer.sugarlabs.org/
>     >
>     >     Is it failing in some way?  Can we fix it?
>     >
>     >     --
>     >     James Cameron
>     >     [3][8]http://quozl.netrek.org/
>     >     _______________________________________________
>     >     Systems mailing list
>     >     [4][9]Systems at lists.sugarlabs.org
>     >     [5][10]http://lists.sugarlabs.org/listinfo/systems
>     >
>     > References:
>     >
>     > [1] mailto:[11]quozl at laptop.org
>     > [2] [12]https://developer.sugarlabs.org/
>     > [3] [13]http://quozl.netrek.org/
>     > [4] mailto:[14]Systems at lists.sugarlabs.org
>     > [5] [15]http://lists.sugarlabs.org/listinfo/systems
> 
>     --
>     James Cameron
>     [16]http://quozl.netrek.org/
> 
> References:
> 
> [1] mailto:quozl at laptop.org
> [2] https://github.com/sugarlabs-infra/help-rebuilder/blob/master/main.py
> [3] https://github.com/sugarlabs-infra/developer-rebuilder/blob/master/main.py
> [4] https://gist.github.com/scanterog/8639b74d1ba077f132675e9712465cf3
> [5] http://buildbot.sugarlabs.org/
> [6] mailto:quozl at laptop.org
> [7] https://developer.sugarlabs.org/
> [8] http://quozl.netrek.org/
> [9] mailto:Systems at lists.sugarlabs.org
> [10] http://lists.sugarlabs.org/listinfo/systems
> [11] mailto:quozl at laptop.org
> [12] https://developer.sugarlabs.org/
> [13] http://quozl.netrek.org/
> [14] mailto:Systems at lists.sugarlabs.org
> [15] http://lists.sugarlabs.org/listinfo/systems
> [16] http://quozl.netrek.org/

> _______________________________________________
> Systems mailing list
> Systems at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/systems


-- 
James Cameron
http://quozl.netrek.org/


More information about the Systems mailing list