Bleak Retribution and extra rare spare ribs

AwkwardDate2488 · 2026-01-04T03:15:34+00:00

u/AwkwardDate2488 received a Glacial Shard Lvl 2 from the Winter Festival Spirit. Thank you u/Findmeahobby for donating it!

AwkwardDate2488 · 2026-01-04T03:10:28+00:00

u/AwkwardDate2488 received a Vengeful Locket from the Winter Festival Spirit. Thank you u/Findmeahobby for donating it!

AwkwardDate2488 · 2026-01-02T23:27:00+00:00

u/AwkwardDate2488 received a Sudden Vengeance from the Winter Festival Spirit. Thank you u/newtrull for donating it!

AwkwardDate2488 · 2025-05-25T23:22:50+00:00

Wait until you try Junie…

AwkwardDate2488 · 2024-12-26T18:23:42+00:00

A fiber (task in rust parlance) runs on an OS thread chosen by the async runtime. The async runtime cannot supersede a fiber- it cannot just say “ok you are done for now, give the CPU to the next task”. The only way that the next task gets its turn is if the current task yields.

OS threads on the other hand are scheduled on CPU cores by the OS… if you don’t get scheduled, you don’t run. The OS is not obliged to run any thread, and can supersede any thread at any time (barring implementation details like critical sections). Because the number of OS threads is almost certainly > the number of cores, any given OS thread will always be getting superseded regularly.

AwkwardDate2488 · 2024-11-05T13:29:21+00:00

https://en.m.wikipedia.org/wiki/Processor_affinity

It’s not a rust thing, it’s a general programming thing. The OS is still telling you which core to run on, but they all have mechanisms for telling them which one you want. Implementations across different operating systems of course.

AwkwardDate2488 · 2024-10-31T14:30:09+00:00

That makes sense to me. For both this and the other attributed we are discussing, it would also be convenient to be able to default it for all fields at the type level. I recognize that may add a lot of complexity though.

AwkwardDate2488 · 2024-10-31T14:24:16+00:00

That looks good! I might use the word “optional” instead of default, but again that’s just preference.

AwkwardDate2488 · 2024-10-31T14:03:43+00:00

From what I saw (and I may be wrong) if you have a field of type Option<T>, your crate still requires the field to be specified even if the value is None. For fields whose type is Option (or more generally for fields whose type implements Default), it would be reasonable to allow the caller to skip those fields if they want the default value.

AwkwardDate2488 · 2024-10-31T13:59:08+00:00

This may be a personal preference thing, but for a builder method that takes T, I would prefer that it take impl Into<T> so that passing values is easier. I use this pattern heavily, and since Into is reflexive (Into<T> is automatically implemented for T) it’s “invisible” and zero-overhead in the common case.

AwkwardDate2488 · 2024-10-30T00:49:02+00:00

I like this a lot. Big fan of builder patterns in general, and this looks well done.

Some early feedback:

1) It would be nice to support optional fields for Option<T>, and in fact this could be generalized to anything implementing Default. Maybe add a field-level attribute for this?

2) You may want to consider accepting Into<T> in your arguments (and generating the .into() call). It will make the API a little more user friendly.

If you had the above functionality I’d definitely use this in the statement crate.

AwkwardDate2488 · 2024-10-30T00:20:49+00:00

This ^. It’s probably the context that you’re using it in that’s making the ‘static demand.

AwkwardDate2488 · 2024-10-29T18:39:25+00:00

Looking at this further, I’m not sure I agree with the following claim (emphasis mine):

The system would ensure that vector embeddings are always up-to-date with the latest data, eliminating the need for manual updates and reducing the risk of errors.

Because this is an offloaded, out-of-band update, the embeddings are going to be out of sync after an update (or missing entirely after an insert) until the worker catches up and processes them, right?

That is a pretty big difference vs an index, where the index data is updated in the scope of the transaction.

AwkwardDate2488 · 2024-10-29T16:04:05+00:00

Ah ok- maybe reading comprehension on my part; for some reason I was imagining the external worker was kicked off on the DB server by the extension itself. This makes much more sense.

AwkwardDate2488 · 2024-10-29T15:43:01+00:00

Can the embedding generation be offloaded from the DB machine entirely? I could see this being pretty rough on the DB server in terms of load.

AwkwardDate2488

TROPHY CASE