Brighter

A .NET Command Dispatcher, with Command Processor features for QoS (like Timeout, Retry, and Circuit Breaker), and support for Task Queues.

[Ian Cooper @ICooper]

Another Brighter release! As of 10.5.0, we now support exporting AsyncAPI from Brighter-enabled applications that describe your endpoints. Similar to OpenAPI for https://t.co/jtKlOfJ00v endpoints, but this is for messaging, not HTTP.

https://t.co/xdxDvWzh0c

[Ian Cooper @ICooper]

We have released 10.3.3 or Brighter.

This includes a fix for Kafka commit errors during partition reassignment in 10.3.3. We now check whether an existing flush is running across batch, time, and partition loss triggers (the latter was not previously checked).

[Ian Cooper @ICooper]

What's Changed

Fixes

- Handle expired SQS receipt handles to prevent dispatcher crash by @iancooper in https://t.co/cw7lwc93Xt
- Resilience pipeline can be reused by @iancooper in https://t.co/f8tjpc0amo
- Shutdown issues on RabbitMQ by @iancooper in https://t.co/8yUfQDhQtF

[Ian Cooper @ICooper]

We have been using coding agents with @BrighterCommand since last year, a few observations.

- As a project, Brighter supports many transports, out/in boxes, schedulers, storage, and distributed locks to fit into environments where it is to be deployed.

[Ian Cooper @ICooper]

We have released Brighter 10.3.0, which includes a significant upgrade of our error-handling strategies - hence the minor version bump.

Brighter’s default behavior is to ack a message when an error leaves the handler pipeline. The principle here is that errors come in two forms:

[Ian Cooper @ICooper]

Solid advice.

We have a PR in to add Roslyn Analyzers to @BrighterCommand, and I think that will be exceptionally helpful when agents write Brighter code.

The advice to prefer retrieval over training may help: look at @Aaronontheweb's work here

[Ian Cooper @ICooper]

We have just released version 10.1.0 of Brighter. https://t.co/Y9iEpu4Q9B

The minor version bump is due to improvements in the management of resources we create in our factories. Brighter uses a DI-friendly framework approach, which means we implement factories for DI providers

[Ian Cooper @ICooper]

For those of you still on V9 of Brighter, our bug fix release 9.9.13 fixes an issue where the stale offset sweeper was not running and clearing stale offsets. (Fix also in 10.0.3)

[Ian Cooper @ICooper]

We have pushed 10.0.3 of Brighter. Mostly bug fixes, but includes support for TickerQ as a scheduler, and EF integration for the MongoDb Outbox. Thanks to all our existing and new contributors: https://t.co/PE6cnfl4W6

[Ian Cooper @ICooper]

To follow up on Brighter's V10 release, we now have supporting documentation for V10 on our docs site: https://t.co/pAADfNFpIf

[Ian Cooper @ICooper]

We have released V10 of Brighter. This represents a significant set of improvements and sets the groundwork for other changes in V10.X releases to come. (We will continue to support V9 with bug fixes until V11; Our release cadence for major versions is 1-2 years.) Details below.

[Ian Cooper @ICooper]

We've released Brighter **v10 RC2** (`10.0.0-preview.7`). We are close to feature complete on **V10** with this release. We need to fix bugs and be satisfied of quality before we go a final release.

[Brighter @BrighterCommand]

However, when you start to wander into areas where it needs to reason about what the code is doing, due to reliance on copy and paste, it stumbles. It can't reason about the test failing because the queue is not created; this test just tests the test itself, not the SUT.

[Brighter @BrighterCommand]

Some feedback on assigning GitHub CoPilot a Brighter issue: https://t.co/DgQyB2brq9

You can see it working here: https://t.co/iMEodBdszF

- It got a long way, fast, with a relatively detailed outline of what to do. The code was as required.

[Brighter @BrighterCommand]

It's pattern recognition, rather than reasoning. That does not diminish its value. A lot of coding tasks are "recognise and apply a pattern to the problem".