| Romster | do you mind unset CC CXX in go and docker ports, i have CC and CXX set for ccache and it brakes on go and docker. | 06:44 |
|---|---|---|
| Guest72693 | Romster, I don't set these flags | 07:20 |
| Romster | i do | 08:21 |
| Romster | also identify your nick | 08:21 |
| spaceone | can you please set me on bcc? | 08:58 |
| spaceone | on jenkins | 08:58 |
| *** prologic has joined #circuits | 11:04 | |
| prologic | sorry about that | 11:04 |
| prologic | Romster, sorry I don't get what you're saying | 11:04 |
| prologic | what's this about CC and CXX flags for docker/go crux ports? | 11:04 |
| prologic | spaceone, you want cc on the CI issue? | 11:04 |
| Romster | i set CC and CXX for ccache and only go and docker fail with that set. | 11:20 |
| Romster | i was asking if you could unset them variables in docker and go if possible. | 11:21 |
| Romster | else i'll just keep working around it. | 11:21 |
| prologic | that's precisely what I said though | 11:57 |
| prologic | I don't set any such variables | 11:57 |
| prologic | in those ports | 11:57 |
| prologic | http://codepad.org/lYOLzTVg | 11:58 |
| Romster | i know i set it in pkgmk.conf and i edit each of those to add unset CC CXX | 12:14 |
| Romster | nevermind. | 12:14 |
| prologic | ooh | 12:24 |
| prologic | sorry I misunderstood what you were saying | 12:24 |
| prologic | you want me to modify them to explicitely unset CC and CXX | 12:24 |
| prologic | because building them breaks with ccache? | 12:24 |
| prologic | in case you have ccache setup with CC/CXX? | 12:24 |
| spaceone | prologic: i want BCC instead of CC | 12:31 |
| prologic | not really sure that's even possible :) | 12:32 |
| prologic | you're either watching the issue(s) | 12:32 |
| prologic | or you're not | 12:33 |
| prologic | :) | 12:33 |
| spaceone | not the issue | 12:33 |
| spaceone | the jenkins mails | 12:33 |
| prologic | oh | 12:33 |
| prologic | no nevermind the jenkins mails | 12:33 |
| prologic | it's going away | 12:33 |
| prologic | See Issue #85 | 12:33 |
| prologic | ShinginaPanda is effectively dead | 12:33 |
| prologic | as of today | 12:33 |
| spaceone | ok | 12:34 |
| Romster | prologic> in case you have ccache setup with CC/CXX? <- correct | 13:06 |
| prologic | yeah sorry | 13:09 |
| prologic | I completely misunderstood what you were asking/saying | 13:09 |
| prologic | communication failure there :) | 13:09 |
| Romster | buidl -_- | 13:30 |
| Romster | thanks for that. | 13:30 |
| prologic | nps | 13:30 |
| prologic | meh | 13:30 |
| Romster | them ports must be special and use them vars internally or something. | 13:30 |
| prologic | didn't realize the default branch is now 3.1 | 13:30 |
| prologic | so my commit got messed up | 13:30 |
| prologic | had to completely redo it all :/ | 13:30 |
| Romster | or they use go with CC/CXX | 13:30 |
| Romster | argh, git checkout 3.0, .... do ya work. git checkout 3.1 ; git pull . 3.0 ; git push | 13:31 |
| Romster | git checkout 3.0 | 13:31 |
| prologic | sorry what? | 13:33 |
| prologic | git is foreign to me | 13:33 |
| prologic | you want the updates in 3.1 too? | 13:33 |
| Romster | i can do that. | 13:33 |
| prologic | well | 13:34 |
| prologic | I haven't upgraded to 3.1 yet | 13:34 |
| prologic | is it officially out yet? | 13:34 |
| Romster | no not yet ti's being tested and fixing the few remaining issues still. there is beta builds of the 3.1 iso though. | 13:37 |
| prologic | and btw | 13:37 |
| prologic | what you suggest above will not work | 13:37 |
| prologic | you can't simply pull from the 3.0 branch | 13:37 |
| prologic | it will and does cause merge conflicts | 13:37 |
| prologic | anyway I'm happy to cherrypy the changes and apply them to 3.1 too | 13:38 |
| prologic | but I'm not on 3.1 atm so I can't really test against a 3.1 system | 13:38 |
| Romster | what on earth did you do... | 13:38 |
| Romster | you pushed to 3.1 | 13:38 |
| Romster | http://crux.nu/gitweb/?p=ports/contrib.git;a=commitdiff;h=aa52405728acbf17c7678d11a28d02c4342c5468 | 13:39 |
| Romster | i merged the stuff. | 13:39 |
| prologic | no I pushed to 3.0 | 13:39 |
| Romster | h that's on 3.0 tag sorry | 13:39 |
| Romster | oh* | 13:40 |
| Romster | i've compiled it on 3.1 already it all builds. | 13:40 |
| Romster | working on branches in git is a little foreign at first. | 13:41 |
| prologic | hmm | 14:04 |
| prologic | 123d.circuits.io is rather nice | 14:04 |
| *** An_Ony_Moose has joined #circuits | 14:35 | |
| *** royalt has joined #circuits | 20:57 | |
| *** SkremoMcThrftsto has joined #circuits | 21:42 | |
| prologic | morn’n all | 21:45 |
| *** SkremoMcThrftsto has quit IRC | 21:47 | |
| *** royalt has quit IRC | 21:52 | |
| *** Workster has joined #circuits | 22:03 | |
| c45y | o/ prologic | 22:34 |
| prologic | aye c45y :) | 22:47 |
| prologic | how was your weekend? | 22:48 |
| prologic | busy? | 22:48 |
| c45y | Umm not too bad | 22:49 |
| c45y | I got hooked on an indie game | 22:49 |
| c45y | and spent nearly all of my weekend playing | 22:49 |
| c45y | http://store.steampowered.com/app/280220/ | 22:50 |
| c45y | stupidly addictive | 22:50 |
| c45y | I did however work out how to make the web interface subscribe to the irc events | 22:50 |
| c45y | still having a hard time getting my head around it | 22:50 |
| prologic | oh? hard time? | 22:52 |
| prologic | how can I help clear things up? :) | 22:52 |
| c45y | I've got the events being hooked and fired into a ring buffer that the web manages | 22:57 |
| c45y | I'm stuck on getting their type | 22:57 |
| c45y | need to see if its a NICK or PRIVMSG | 22:57 |
| c45y | etc | 22:57 |
| prologic | oh ic | 23:01 |
| prologic | that’s easy :) | 23:01 |
| prologic | http://codepad.org/kjhDRFry | 23:02 |
| prologic | Which btw (in Python) is just a convenience for: | 23:02 |
| prologic | e.__class__.__name__ | 23:02 |
| prologic | we use the class’s name as the name of the event | 23:02 |
| prologic | d’uh :) | 23:02 |
| prologic | Btw, was this not documented nicely anywhere? | 23:02 |
| c45y | not really without getting into it too deep | 23:15 |
| c45y | the tutorial is lacking a bit imo | 23:15 |
| c45y | knowing nothing about the structure and trying to jump in and get 'something' working was hard | 23:15 |
| prologic | *nods* | 23:19 |
| prologic | Do we need another more realistic tutorial perhaps? | 23:19 |
| prologic | i.e: How to build a simple web app? | 23:19 |
| prologic | or sometthing | 23:19 |
| prologic | And where would we document this “how to get the event’s name” is it enough to document in the API Docs or would you also like to see this in the “Users Manual"? | 23:20 |
| prologic | I’m sorta inclinced to document in bohth places | 23:20 |
| prologic | not sure on the tutorial though if we need another one and what it should be based on | 23:20 |
| prologic | the whole dog pound style tutorial is just a stupidly contriived example of circuits components and it’s message bus | 23:21 |
| c45y | Yea it was mostly useless | 23:25 |
| c45y | I think a socket / network example would be better suited | 23:25 |
| c45y | with sender/reciever or something | 23:25 |
| c45y | with cross communication between the two | 23:25 |
| prologic | hang on | 23:28 |
| prologic | a socket server example | 23:28 |
| prologic | and a separate socker client example? | 23:28 |
| prologic | i.e: a walk through of examples/echoserver.py and examples/telnet.py? | 23:29 |
| prologic | the beauty here is that if we went through a walk through of examples/telnet.py it actually combbines two things | 23:29 |
| prologic | stdin + tcp client | 23:29 |
| prologic | so you have an idea there of how to combine things there | 23:29 |
| prologic | the examples/ecoserver.py is well rather trivial | 23:29 |
| prologic | class EchoServer(TCPServer0: | 23:29 |
| prologic | def read(self, sock, data): | 23:29 |
| prologic | return data | 23:29 |
| prologic | done | 23:29 |
| prologic | no seriously :) | 23:30 |
| c45y | yea actually | 23:37 |
| c45y | that might be better to get this telnet example less hidden | 23:37 |
| c45y | # Define a separate channel for this component so we don't clash with | 23:37 |
| c45y | # the ``read`` event of the ``stdin`` component. | 23:37 |
| c45y | in particular I was missing | 23:38 |
| prologic | *nods* gotcha | 23:42 |
| prologic | so how about this | 23:42 |
| prologic | I write two new tutorials | 23:42 |
| prologic | a walk through of writing an echo server | 23:42 |
| prologic | and a walk through of writing a telnet client | 23:42 |
| c45y | echo is trivial really | 23:43 |
| c45y | def read: self.fire(write(blah))) | 23:44 |
| prologic | indeed | 23:46 |
| prologic | so no point in walking through it? | 23:46 |
| c45y | i think telnet would cover it | 23:47 |
| c45y | hmm broke my event handling :/ | 23:47 |
| c45y | Should....@handler(event="Log", channel="irc_event") | 23:48 |
| c45y | handle | 23:48 |
| c45y | self.fire( | 23:48 |
| c45y | Log("*** {0:s} has left {1:s}".format(source[0], channel)), | 23:48 |
| c45y | "irc_event" | 23:48 |
| c45y | ) | 23:48 |
| prologic | no event= | 23:48 |
| prologic | just *names | 23:48 |
| prologic | so @handler(“Log”, …) | 23:48 |
| c45y | hmm docs say event= is available | 23:48 |
| prologic | hmm | 23:48 |
| c45y | kk | 23:48 |
| c45y | http://circuits.readthedocs.org/en/latest/api/circuits.core.handlers.html#circuits.core.handlers.handler | 23:49 |
| prologic | that should not be the case | 23:49 |
| prologic | lemme check the docs | 23:49 |
| c45y | Optionally, the method may have an additional first argument named event. If declared, the event object that caused the handler to be invoked is assigned to it. | 23:49 |
| prologic | @handler(“*names, **kwargs) | 23:49 |
| prologic | no event keyword argument there | 23:49 |
| prologic | oh | 23:50 |
| prologic | that’s talking about the actual event handler | 23:50 |
| prologic | damnit | 23:50 |
| prologic | not the decorator | 23:50 |
| prologic | e.g: | 23:50 |
| c45y | O i c | 23:50 |
| prologic | def foo(self, event, *args, **kwargs): | 23:50 |
| prologic | wher eyou can capture the “actual event” | 23:50 |
| c45y | yea I gotcha now | 23:50 |
| prologic | and introspect it | 23:50 |
| prologic | is that not clear enough in that doc string? | 23:50 |
| c45y | "This module define the @handler decorator/function and the HandlesType type." | 23:50 |
| c45y | kinda made me think it was talking about @handler | 23:50 |
| c45y | ll | 23:50 |
| prologic | hmm | 23:51 |
| prologic | I’ll review the docstrings for that module | 23:51 |
| prologic | and decorator | 23:51 |
| prologic | try to mke that a bit clearer | 23:51 |
| prologic | it’s basically talking about the difference between: | 23:51 |
| prologic | def foo(self, *args, **kwargs): | 23:51 |
| prologic | and | 23:51 |
| prologic | def foo(self, event, *args, **kwargs): | 23:51 |
| prologic | you can decide if you need th event object or not | 23:51 |
| prologic | or just it’s data | 23:51 |
| prologic | sometimes having the event object is haandy in some use cases | 23:52 |
| prologic | like logging | 23:52 |
| prologic | otherwise you don’t care and onyl want the data | 23:52 |
| c45y | gotcha | 23:52 |
| prologic | I take all feedback rather seriously | 23:53 |
| prologic | so lemme know if we can imrpve the docs in any way | 23:53 |
| prologic | I’ll write up an issue for writing a new telnet tutorial | 23:53 |
| c45y | I think my lack of understanding is contributing a lot to my confusion | 23:53 |
| c45y | also my brain after hours of reading a stupid concepts guideline | 23:54 |
| c45y | im using this as a break between modules in this book | 23:54 |
| prologic | https://bitbucket.org/circuits/circuits/issue/86/telnet-tutorial | 23:54 |
| c45y | perhaps not the greatest way to learn something :P | 23:54 |
| prologic | sorry what poor guidelines? | 23:55 |
| prologic | what book? | 23:55 |
| prologic | :) | 23:55 |
Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!