Precompiled 2024-05-15-553ba73

ConfigModel::apply don't fetch existing source (#25780)

we can avoid fetching existing module source when applying a new config, since all we need are the paths.

GitOrigin-RevId: 524ff3b1950b8ced14dd73f8e68e8e63609291d3

Precompiled 2024-05-15-83f6500

Add multi segment metadata to text search's backfilling state (#25752)

GitOrigin-RevId: 9afd42bb5610db0f02a294c09f70bfb3ba36c861

Precompiled 2024-05-14-c0f7a5c

feat(components): Make ActionOutcome component-aware (#25684)

GitOrigin-RevId: 4866b0099a837a062a3209fa74a4d0c09ee90493

Precompiled 2024-05-13-95543ed

remove rounding for bandwidth and db storage (#25583)

We've decided to no longer round up usage to the nearest 1KB!

GitOrigin-RevId: dcff0ed46a69d7017f0d144060559fe476074225

Precompiled 2024-05-10-d38e663

Remove block_logging from ActionCallbacks trait. (#25534)

block_logging is very confusing. It is part of ActionCallbacks trait, which means it is serialized and deserialized from protos.  However, all that obfuscates the fact that block_logging is always false for action callbacks. Thus the whole thing is redundant.

To help clean this up, remove block_logging from the trait and set it to false. We could pass log_visibility into ApplicationFunctionRunner, so we can check if we should block visibility, but this will always return false since actions have AllowedVisibility::All anyway, so passing this and creating transactions in order to do the check seem like an overkill.

GitOrigin-RevId: 3be542a7f2860e31b36a7506be1fa2054bb1b28a

Precompiled 2024-05-09-8aa6ae9

nest DeveloperQuery inside ResolvedQuery (#25381)

see docstring on ResolvedQuery.

this gets us closer to removing TableIdAndTableNumber which is a confusing concept since it mashes together tablets and table numbers.

GitOrigin-RevId: 9586355db96f0e276a37e030a4e732f49a3f4455

Precompiled 2024-05-08-0042975

Add first component paths (#25416)

The general idea is that I'll change our function execution layers to accept a `ComponentFunctionPath` and then only support `ComponentId::Root` for now.

GitOrigin-RevId: 2a53e96a98bfd3b62082737b448e43e3981c0928

Precompiled 2024-05-07-13337fd

Build tantivy index segment from revision stream (#25383)

This PR adds a function to create a tantivy segment from a stream of document revisions in descending timestamp order. We keep the invariant that convex ids are unique in tantivy segments, so we don't process deletes from the revision stream, we just skip writing them.

I also added tests for delete and replace and fixed a small bug where deleted documents weren't used if you only had OR terms in the search query.

GitOrigin-RevId: 47a940c5ec09454c1c321851a183ec2f503a073b

Precompiled 2024-05-06-b0591ed

text search walk stable index name (#25376)

like index range queries, text search queries should walk a consistent tablet. otherwise there might be weird issues where it's walking an index and the tablet changes out from under it, possibly changing the indexed fields.

GitOrigin-RevId: d576844a9a5b29a5a736057a19a819fe27a01f54

Precompiled 2024-05-03-500243c

Update npm to 1.11.3 (#25341)

GitOrigin-RevId: 46037235cb66a4448671e73956922643418eb4a1