We found and fixed a rare race condition in our session handling

1. Puma

   1 43 7,739 9.3 Ruby

   A Ruby/Rack web server built for parallelism

   

   Each server does share a "proto env" object, but it is duplicated for each Client:

   https://github.com/puma/puma/blob/0cc3f7d71d1550dfa8f545ece8...

   and Client objects are not reused:

   https://github.com/puma/puma/blob/0cc3f7d71d1550dfa8f545ece8...

2. CodeRabbit

   coderabbit.ai featured

   CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

   

3. Unicorn

   2 3 1,416 5.0 Ruby

   Unofficial Unicorn Mirror. (by defunkt)

   

4. D2L.CodeStyle

   3 1 10 5.8 C#

   Annotations and analysis tools for D2L C# code style

   

   At D2L we have a large C# code base which gets deployed in a few different subsets, but is largely a monolithic fleet of web servers.

   To prevent these kind of problems we have a few approaches, but the main way is to prevent shared mutable state. To do this we have a custom C# code analyzer (source here: https://github.com/Brightspace/D2L.CodeStyle/tree/master/src... , but it's not documented for external consumption at this point.) It goes like this:

     [Immutable]

Suggest a related project