serenity - The Serenity Operating System 🐞

Age	Commit message (Collapse)	Author
2022-01-24	Everywhere: Convert ByteBuffer factory methods from Optional -> ErrorOr	Sam Atkins
	Apologies for the enormous commit, but I don't see a way to split this up nicely. In the vast majority of cases it's a simple change. A few extra places can use TRY instead of manual error checking though. :^)
2022-01-01	LibSQL: Avoid unnecessary copies in Heap	Ben Wiederhake

2021-12-08	LibSQL: Avoid implicitly copying ByteBuffer	Ben Wiederhake

2021-12-04	LibSQL: Improve error handling	Jan de Visser
	The handling of filesystem level errors was basically non-existing or consisting of `VERIFY_NOT_REACHED` assertions. Addressed this by * Adding `open` methods to `Heap` and `Database` which return errors. * Changing the interface of methods of these classes and clients downstream to propagate these errors. The constructors of `Heap` and `Database` don't open the underlying filesystem file anymore. The SQL statement handlers return an `SQLErrorCode::InternalError` error code if an error comes back from the lower levels. Note that some of these errors are things like duplicate index entry errors that should be caught before the SQL layer attempts to actually update the database. Added tests to catch attempts to open weird or non-existent files as databases. Finally, in between me writing this patch and submitting the PR the AK::Result<Foo, Bar> template got deprecated in favour of ErrorOr<Foo>. This resulted in more busywork.
2021-11-10	AK: Make ByteBuffer::try_* functions return ErrorOr<void>	Andreas Kling
	Same as Vector, ByteBuffer now also signals allocation failure by returning an ENOMEM Error instead of a bool, allowing us to use the TRY() and MUST() patterns.
2021-11-08	LibSQL: Replace Result<T, E> use with ErrorOr<T>	Andreas Kling

2021-09-06	Everywhere: Make ByteBuffer::{create_*,copy}() OOM-safe	Ali Mohammad Pur

2021-09-06	Everywhere: Use OOM-safe ByteBuffer APIs where possible	Ali Mohammad Pur
	If we can easily communicate failure, let's avoid asserting and report failure instead.
2021-08-21	LibSQL: Introduce Serializer as a mediator between Heap and client code	Jan de Visser
	Classes reading and writing to the data heap would communicate directly with the Heap object, and transfer ByteBuffers back and forth with it. This makes things like caching and locking hard. Therefore all data persistence activity will be funneled through a Serializer object which in turn submits it to the Heap. Introducing this unfortunately resulted in a huge amount of churn, in which a number of smaller refactorings got caught up as well.
2021-06-19	LibSQL: BTree index, Heap, and Meta objects for SQL Storage layer	Jan de Visser
	Unfortunately this patch is quite large. The main functionality included are a BTree index implementation and the Heap class which manages persistent storage. Also included are a Key subclass of the Tuple class, which is a specialization for index key tuples. This "dragged in" the Meta layer, which has classes defining SQL objects like tables and indexes.