https://www.olowe.co/about.html
From Oliver Lowe to ~otl/untangledco
User @emptycode1782 posted a comment on the video https://www.youtube.com/watch?v=9Q9Vocd8u54 and again I wanted to put it out to a more public forum rather rather than be lost in deep YouTube comments. --- so i wonder how do you guys get into these specific areas. For now im just a beginner focusing on C# and trying to get into back end, its kinda obvious what i have to look for in short run, there are courses, github projects, books, lots of articles and Microsoft docs. But i wonder, beyond these obvious areas, how does one get into more specific areas, how do you find them and how do you get into them, is it just passion and messing around with code and fundamentals for a
From Oliver Lowe to ~otl/untangledco
Someone posted a comment on the video https://www.youtube.com/watch?v=fl7p0SiqGeY and I thought it would be nicer to reply here for everyone to see, then post a link back, rather than formatting stripped nested YouTube comments. --- Hey man its great to see you back! I have to ask something. 1) How do you determine whether you want to use a buffered channel vs unbuffered channel and which one should you choose if you’re not sure. 2) Let’s suppose you have a goroutine which has a select statement. When would you need to use “worker” go routines inside it and shift
From Oliver Lowe to ~sircmpwn/godocs.io
> oh for fucks sake > > > curl -i https://godoc.srcbeat.com > HTTP/2 502 > alt-svc: h3=":443"; ma=2592000 > server: Caddy > content-length: 0 > date: Sun, 01 Sep 2024 04:47:21 GMT Hahaha don't worry I'm hacking at it so it's up and down. I'll post here and to the list lists.sr.ht/~otl/untangledco when it's stable. Hope it's helpful :)
From Oliver Lowe to ~sircmpwn/godocs.io
Wonder if it's the same problem as last time - running out of storage space? I set up an instance, had a quick poke around, and found the packages table in the database stores raw source bytes in the database: CREATE TABLE packages ( platform text NOT NULL, import_path text NOT NULL, module_path text NOT NULL, series_path text NOT NULL, version text NOT NULL, reference text NOT NULL, commit_time timestamptz NOT NULL, name text NOT NULL,
From Oliver Lowe to ~otl/untangledco
Nice work! Applied https://github.com/untangledco/streaming/commit/e3efd43f94e6f502942e52c0a77474c1ab474962
From Oliver Lowe to ~gjnoonan/public-inbox
> I am mid-way through rebasing a stack of patches, then got distracted > and have not pushed up the newer changes. Nice - looking forward to it. I'll set it up for the list at lists.sr.ht/~otl/untangledco and the Twitch IRC channel when it's ready!
From Oliver Lowe to ~otl/untangledco
> +func encode(file *File) ([]byte, error) { > + buf := new(bytes.Buffer) > + > + if err := binary.Write(buf, binary.LittleEndian, &file.Header); err != nil { > + return nil, fmt.Errorf("binary.Write failed: %v", err) > + } Callers do not need to know about the implementation of encode() i.e. don't need to know which function returned an error. The important context that the caller would like to know is that encoding the global header failed. The error message can be something short like "encode global header: %v". A message as short as "global header: %v" could be OK, too, because callers of encode know that they are trying to encode stuff:
From Oliver Lowe to ~otl/untangledco
Thanks again! Before I review this, do you have any questions? You mentioned using a LLM - just want to make sure that you understand what your patch actually contains.
From Oliver Lowe to ~sircmpwn/godocs.io
Yeah this was reported about a week ago [1]. Wondering if there's some way we can help Adnan (the maintainer, I think) out. Adnan works on godocs.io in their free time [2]. Just found the project's tickets [3], may start having a look through there... [1]: https://lists.sr.ht/~sircmpwn/godocs.io/%3CCAP8dQmszan-055BDbLdGVB0yzkgrnLfhq3M-yvP-XXmSp==6Rg@mail.gmail.com%3E [2]: https://lists.sr.ht/~sircmpwn/godocs.io/%3CCAP8dQmsUhNiqUXbA-Cq5hFAw=yBTvp-2__2h43JY-eDPkNyn1Q@mail.gmail.com%3E#%3CCYJ0LIUUSND7.33TGGAR89NUIS@maolood.com%3E [3]: https://todo.sr.ht/~sircmpwn/gddo
From Oliver Lowe to ~otl/untangledco
Having some specific guides to point to I think makes it easier for others to contribute. It saves time if someone reads it before, and it helps to stave off that "taking it personally" thing (which I certainly get sometimes!) if they read it after submitting a change too. --- Not sure about the bit talking about how we may rework ourselves for trivial changes. Thoughts? README.md | 39 +++++++++++++++++++++++++++++++++------ 1 file changed, 33 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index c9585f3..ca4fa5b 100644 [message trimmed]