|
Documentation Channel for #raku | This channel is logged | Roadmap: github.com/raku/doc/wiki Set by [Coke] on 23 May 2022. |
|||
| Geth__ | ¦ doc: tbrowder self-assigned Show accessing class methods programmatically github.com/Raku/doc/issues/4163 | 12:38 | |
|
13:12
Geth__ left,
Geth joined
13:31
NemokoschKiwi joined
|
|||
| NemokoschKiwi | Cool. Updated the site, better late than never. | 14:35 | |
| Also, is it worth to "advertise" it on #raku? How much is it meant to be open for everyone? | 14:36 | ||
| Geth | doc: tbrowder++ created pull request #4164: Add a practical example of class introspection |
15:44 | |
| lizmat | I seem to have misplaced where the meeting is going to be... could someone enlighten me in privmsg? | 16:23 | |
| or here :-) | |||
| NemokoschKiwi | I think it's legitimately unknown | 16:38 | |
| lol | |||
| lizmat | well... if [Coke] doesn't come up with a URL, I think I'll come up with one on Jitsi | 16:46 | |
| [Coke] | yup, jitsi - figured we'd just reuse the last one | 16:52 | |
| one sec | |||
| ... which is not on the wiki, oops | 16:53 | ||
| meet.jit.si/raku-docs | 16:54 | ||
| (advertising elsewhere) - I have no strong feelings one way or the other. | |||
| NemokoschKiwi | oh, one more thing: github.com/Raku/doc/discussions I haven't given up on this idea yet :D | 17:35 | |
| And in particular, I'd really like to see a bit of brainstorming about, you know, the documentation of returned containers | 17:36 | ||
| That feels a lot like type information; something that should be representable in a compact way - once the design is cleared up | |||
| [Coke] | github.com/Raku/doc/discussions/4149 you mean? | 18:16 | |
| I don't think I'm getting emails on new discussions. | |||
| (or maybe just too many emails lately) | |||
| I added some notes to the top wiki page about the meeting (including the room - broke it out to avoid link scrapers which is probably overly cautious) | 18:23 | ||
| also a minor not about the infra issue to the project. emailing roman now... | |||
| sent | 18:28 | ||
| Now I will try to close at least one ticket or PR... | |||
| NemokoschKiwi | True... I wish discussions generated emails. | 18:36 | |
|
18:36
NemokoschKiwi left
18:59
sena_kun joined
|
|||
| lizmat | o/ sena_kun | 19:03 | |
| sena_kun | hi! | 19:04 | |
| anything I can help with? | |||
| lizmat | yes | 19:05 | |
| what do you think is still needed from the infra team to get the new doc site operational | |||
| because it is at least unclear to *me* what is needed | 19:06 | ||
| sena_kun | somebody who will host the website as a docker container (bonus points for reliability checks), and will redirect the domain to point to that host | 19:14 | |
| lizmat | so the docker container is all set ? | 19:20 | |
| sena_kun | Dockerfile is written, yes | 19:23 | |
| lizmat | how are updates handled ? I mean, if someone pushes to main in the doc repo, what happens? | 19:24 | |
| does someone need to push a button to update the site > | |||
| ? | |||
| sena_kun | lizmat, if you want to update the content to main, you visit a special URL with private token, then it updates the content while the site is running. we can set auto-curling it daily if needed. | 19:26 | |
| lizmat | when you're talking about reliability checks, you mean if it up? | 19:28 | |
| or more than that ? | |||
| sena_kun | 1)if it's up, if it's not, it should trigger restart; 2)in a perfect world we'll run two containers and do balancing on them, so that we can for example update the website itself without downtime (first container stops, the second one takes requests, the first one updates, when it finishes, it handles the requests, the other one updates). | 19:30 | |
| lizmat | yeah, but if the restart fails, we want to be notified, right ? | 19:32 | |
| sena_kun | sure | 19:33 | |
| lizmat | so what happens now if the special URL is called? The site stops working ? | ||
| sena_kun | no | 19:34 | |
| the special URL updates the content only | |||
| the content updates without downtime | |||
| lizmat | ah... ok, so if we would change one of the templates, *then* we would have downtime | ||
| sena_kun | yes, for about 5 minutes or something | 19:35 | |
| that's why having a couple of containers is a good, modern practice | |||
| lizmat | wow... that's.... pretty long ? | ||
| what causes that long time? | |||
| sena_kun | that's down to devops though | ||
| lizmat, caching all the Pod files in the repo takes 95% of the time | |||
| not sure what's exactly slow, I suspect it's parsing | 19:36 | ||
| lizmat | aha... ok, gotcha | ||
| hmmm... so if the contents are changed, only the changed pod files would need to be reparsed, right ? | 19:37 | ||
| sena_kun | yes | ||
| lizmat | ok, gotcha | ||
| and there's no way to do the same for the templates, because we don't have the necessary dependency graph on the templates, right? | |||
| sena_kun | no, not because of that | 19:38 | |
| the dependency graph is implemented recently btw | |||
| lizmat | ah, ok... | ||
| sena_kun | but because the templates are cached and AFAIK there is no API to say "please re-parse this file". | 19:39 | |
| lizmat | understood | 19:40 | |
| so we would need a VM that could run 2 of the Docker containers at the same time, or be down for 5 mins when the templates / code have changed | 19:41 | ||
| I'm sorry if the is the Nth time you're being asked this :-( | 19:45 | ||
| sena_kun | yes | 20:34 | |
| well, running just 2 containers is not that hard | |||
| Geth | doc: 8f9298d551 | (Tom Browder)++ | doc/Language/classtut.pod6 Add a practical example of class introspection The current docs do not show a practical, simple, and safe example of the use and implementaion of class introspection. This PR attempts to rectify the problem. |
21:51 | |
| doc: 9c8feb43fe | (Tom Browder)++ | doc/Language/classtut.pod6 fix typo |
|||
| doc: 848c19e48e | (Tom Browder)++ (committed using GitHub Web editor) | doc/Language/classtut.pod6 Merge pull request #4164 from tbrowder/introspect Add a practical example of class introspection |
|||
| [Coke] | Someone (not sena_kun) please grab this chat about todos and throw it on the raku/docs/wiki page. | 22:53 | |
| I will do so tomorrow if it's still open. | |||
| Geth | doc: 883d9feb6b | Coke++ | doc/Language/classtut.pod6 Make updated examples pass xt/ |
22:59 | |
| [Coke] | crud, I forgot how to install the deps so i can run make xtest in a new checkout | 23:34 | |