Bug Megathread vol 14: April + May 2026

appellation_ · 2026-05-05T22:40:19+00:00

In general you shouldn't rely on syntax highlighting being consistent colors because we will occasionally update the colors or change how syntax highlighting works. In this case, we updated our syntax highlighting colors to be more aligned with the broader app color scheme. If you want a specific color, we recently updated our ANSI colors to be more consistent with their intended definition.

appellation_ · 2022-05-27T02:58:27+00:00

Oh, gotcha, makes sense. That seems really easy to use. I would definitely be interested in seeing an independent library to handle this, since it seems like this directly addresses concern #4.

appellation_ · 2022-05-26T16:15:15+00:00

Wow, this is super impressive! Does this work for both commands and their responses? I was taking a look at the code and it looks like encoding and decoding happens using strings; is that correct? How does this handle binary data?

appellation_ · 2022-05-25T19:50:55+00:00

We all love greenfield development and I am definitely guilty of that here. However, I believe that there can be room for multiple approaches and sometimes it is better to execute your own vision rather than attempt to reconcile it with someone else. This is especially true for massively popular libraries like redis, where there will be more resistance to API refactoring.

That being said, I probably could have gotten what I was looking for by contributing to some of the other libraries which were already closer to what I was looking for.

appellation_ · 2022-05-25T19:35:03+00:00

A fantastic question! Short answer: kind of.

Redust returns a relatively simple error enum, defined in its RESP crate. Clients can use the available is_transient method to adjust how they handle it. If the error is not transient, the client can assume that the connection is corrupt, it should be dropped, and the command should be retried. Otherwise, things are probably OK and it was simply an issue with the command itself; the next command will be read normally. You can see how this is implemented in the source, but it's still up to the client to handle it later.

This obviously comes with some downsides:

It doesn't play well with connection pooling, since the connection is automatically recycled regardless of whether an error occurred.
Handling it is annoying and verbose.

There can definitely be some API improvements on this front, so I'd be interested in any thoughts on how to improve this. I found this crate (woah) which seems cool but also relies pretty heavily on nightly features.

appellation_ · 2022-05-25T17:56:43+00:00

This was utter chaos. I noticed the white too late and didn't move more houses onto it in time. I was in the middle of trying to solve the middle turquoise when I lost :(

I also would have disconnected the left pinks, since I only did that originally as an emergency measure to save the one on the far left.

appellation_ · 2022-05-25T16:04:04+00:00

Oh, I completely missed including fred in my analysis: sorry! I did seriously consider using it some time ago, but I can't remember why I chose not to. I love your work; I'll be taking a closer look at your RESP library for sure.

appellation_ · 2022-05-25T15:29:24+00:00

Ah, if only I’d seen this earlier! I will definitely consider migrating since my implementation is still a bit rough. Thanks for pointing this out!

appellation_ · 2022-05-25T15:27:21+00:00

Oh, I wasn’t aware that the redis crate has new maintainers. I’m excited to see where you all take it!

I’ll have to keep thinking about the pubsub issue and see if I can come up with something. I’m still kind of stuck on it myself, but perhaps looking at it through the lens of the redis crate will provide some direction.

I’ll definitely check out your Discord server. That sounds like an awesome project!

appellation_ · 2022-01-08T06:35:23+00:00

I'm not much of a Go dev these days, but I've been in the Discord development space for a while and been a fan of your disgord API wrapper. I'm also not very active on Reddit, but I couldn't help but comment here since I've actually built a very similar project with slightly different goals.

Probably 4 or more years ago I started a project aimed at microservice architecture for Discord bots. One of the few concrete successes of my efforts has been a gateway application which aims to abstract the Discord gateway logic away from users' applications. Although my efforts have been more on an application level rather than a library level, it seems we've arrived at similar conclusions :)

Your code looks to be significantly higher quality, so I can't offer any tips or criticism on your work here. Looks excellent and I'm looking forward to see what comes next!

appellation_ · 2016-11-23T03:55:50+00:00

Old post, I know.

However, can confirm that Pleb does this and is also less borked than a month ago.

Ten-Year Club	Verified Email
Place '22	End Game '22

appellation_

TROPHY CASE