home.social

#jepsen — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #jepsen, aggregated by home.social.

fetched live
  1. A new #Jepsen release to support caching expensive generators and final reads for cycle-detection tests: github.com/jepsen-io/jepsen/re

  2. A new #Jepsen release to support caching expensive generators and final reads for cycle-detection tests: github.com/jepsen-io/jepsen/re

  3. Delighted to announce the release of #Jepsen 0.3.12, now available on Clojars and GitHub, as usual.

    github.com/jepsen-io/jepsen/re

  4. Delighted to announce the release of #Jepsen 0.3.12, now available on Clojars and GitHub, as usual.

    github.com/jepsen-io/jepsen/re

  5. Как Jepsen ломает распределённые базы: разбор бага в CockroachDB

    Запись вернула ошибку, но значение всё равно оказалось в базе. Именно такие сбои Jepsen вытаскивает из распределённых систем: в статье разбираем реальный баг CockroachDB, путь от странного симптома до причины и то, почему на расследование ушло два месяца. Разобрать баг

    habr.com/ru/companies/otus/art

    #Jepsen #CockroachDB #распределённые_базы_данных #консистентность #линеаризуемость #сериализуемость #транзакции #отказоустойчивость #конкурентные_ошибки #тестирование_сбоев

  6. A new #Jepsen report, on #MariaDB #Galera Cluster 12.1.2. Two cases of write loss, along with P4 (Lost Update) and Stale Read in healthy clusters.

    jepsen.io/analyses/mariadb-gal

  7. A new #Jepsen report, on #MariaDB #Galera Cluster 12.1.2. Two cases of write loss, along with P4 (Lost Update) and Stale Read in healthy clusters.

    jepsen.io/analyses/mariadb-gal

  8. A new #Jepsen report, on MariaDB Galera Cluster 12.1.2. Two cases of write loss, along with P4 (Lost Update) and Stale Read in healthy clusters.

    jepsen.io/analyses/mariadb-gal

  9. A new #Jepsen report, on MariaDB Galera Cluster 12.1.2. Two cases of write loss, along with P4 (Lost Update) and Stale Read in healthy clusters.

    jepsen.io/analyses/mariadb-gal

  10. I arrived a “ACID compliant transfer of bindings” and I’m wondering if @aphyr of #jepsen fame has been consulted. #regicideReport @cstross

  11. I arrived a “ACID compliant transfer of bindings” and I’m wondering if @aphyr of #jepsen fame has been consulted. #regicideReport @cstross

  12. A new #Jepsen report: we demonstrate data loss and persistent split-brain in the NATS streaming system, in response to simulated power failures/OS crashes.

    jepsen.io/analyses/nats-2.12.1

  13. A new #Jepsen report: we demonstrate data loss and persistent split-brain in the NATS streaming system, in response to simulated power failures/OS crashes.

    jepsen.io/analyses/nats-2.12.1

  14. A new #Jepsen release, 0.3.10, brings improved support for controllable random value generation, and running tests inside Antithesis. Jepsen's composable generator system has also been extracted to a minimal library, making it easier to re-use in other systems.

    github.com/jepsen-io/jepsen/re

  15. A new #Jepsen release, 0.3.10, brings improved support for controllable random value generation, and running tests inside Antithesis. Jepsen's composable generator system has also been extracted to a minimal library, making it easier to re-use in other systems.

    github.com/jepsen-io/jepsen/re

  16. allow me to have a little nerd crush because I'm watching a talk about #jepsen and for me it's pretty much the coolest thing ever about testing AND databases 😍

  17. allow me to have a little nerd crush because I'm watching a talk about #jepsen and for me it's pretty much the coolest thing ever about testing AND databases 😍

  18. A new #Jepsen report! We tested early builds of Capela, an unreleased distributed programming environment, and found twenty-two issues, including four language problems, fourteen crashes or non-fatal panics, performance degradation, and three safety issues including lost update.

    jepsen.io/analyses/capela-dda5

  19. A new #Jepsen report! We tested early builds of Capela, an unreleased distributed programming environment, and found twenty-two issues, including four language problems, fourteen crashes or non-fatal panics, performance degradation, and three safety issues including lost update.

    jepsen.io/analyses/capela-dda5

  20. 🚀✨ In a groundbreaking announcement, #Jepsen reveals that systems are *gasp* difficult to test in the most obvious places—cue the #fuzzer blind spots conspiracy 🤔. But don't worry, they've got #Kyl on the case, so sleep easy knowing your #bugs will continue thriving in the shadows 🐛🔍.
    tigerbeetle.com/blog/2025-06-0 #testing #blindspots #innovation #HackerNews #ngated

  21. 🚀✨ In a groundbreaking announcement, #Jepsen reveals that systems are *gasp* difficult to test in the most obvious places—cue the #fuzzer blind spots conspiracy 🤔. But don't worry, they've got #Kyl on the case, so sleep easy knowing your #bugs will continue thriving in the shadows 🐛🔍.
    tigerbeetle.com/blog/2025-06-0 #testing #blindspots #innovation #HackerNews #ngated

  22. A new #Jepsen report! We worked with TigerBeetle to find seven crashes, elevated latencies during single-node failures, and requests which were retried forever in version 0.16.11. We found only two safety issues: missing results for queries with multiple predicates, and incorrect timestamps in a debugging API. As of version 0.16.45, TigerBeetle had addressed every issue, except for indefinite retries.

    jepsen.io/analyses/tigerbeetle

  23. A new #Jepsen report! We worked with TigerBeetle to find seven crashes, elevated latencies during single-node failures, and requests which were retried forever in version 0.16.11. We found only two safety issues: missing results for queries with multiple predicates, and incorrect timestamps in a debugging API. As of version 0.16.45, TigerBeetle had addressed every issue, except for indefinite retries.

    jepsen.io/analyses/tigerbeetle

  24. A small issue in Amazon RDS for PostgreSQL: at the "Repeatable Read” isolation level, which in PostgreSQL normally means Snapshot Isolation, Amazon RDS for PostgreSQL clusters appear to exhibit Long Fork. We observed this behavior in healthy clusters, in versions ranging from 13.15 to 17.4. jepsen.io/analyses/amazon-rds-

    #Jepsen

  25. A small issue in Amazon RDS for PostgreSQL: at the "Repeatable Read” isolation level, which in PostgreSQL normally means Snapshot Isolation, Amazon RDS for PostgreSQL clusters appear to exhibit Long Fork. We observed this behavior in healthy clusters, in versions ranging from 13.15 to 17.4. jepsen.io/analyses/amazon-rds-

    #Jepsen

  26. A new #Jepsen report! We worked with Buf to analyze the safety of Bufstream, a Kafka-compatible streaming system. We found three safety and two liveness issues in Bufstream 0.1.0, including the loss of acknowledged writes in healthy clusters. These problems were resolved by version 0.1.3.

    jepsen.io/analyses/bufstream-0

  27. A new #Jepsen report! We worked with Buf to analyze the safety of Bufstream, a Kafka-compatible streaming system. We found three safety and two liveness issues in Bufstream 0.1.0, including the loss of acknowledged writes in healthy clusters. These problems were resolved by version 0.1.3.

    jepsen.io/analyses/bufstream-0

  28. #Jepsen 0.3.6 is now available on GitHub and Clojars. This is a sizeable release. It includes a significant correctness bugfix for a rare bug that could make operations in the history print with the wrong data. It also adds a new namespace for composing databases, nemeses, and generators when working with systems where each node has a different role. Kafka-style tests gain new powers and are significantly faster.

    github.com/jepsen-io/jepsen/re

  29. #Jepsen 0.3.6 is now available on GitHub and Clojars. This is a sizeable release. It includes a significant correctness bugfix for a rare bug that could make operations in the history print with the wrong data. It also adds a new namespace for composing databases, nemeses, and generators when working with systems where each node has a different role. Kafka-style tests gain new powers and are significantly faster.

    github.com/jepsen-io/jepsen/re

  30. A new, short #Jepsen report is out on jetcd 0.8.2. Jetcd is the official Java client library for etcd. We show that it contains an improper retry mechanism which causes lost update, circular information flow, and aborted read. Please enjoy!

    jepsen.io/analyses/jetcd-0.8.2

  31. A new, short #Jepsen report is out on jetcd 0.8.2. Jetcd is the official Java client library for etcd. We show that it contains an improper retry mechanism which causes lost update, circular information flow, and aborted read. Please enjoy!

    jepsen.io/analyses/jetcd-0.8.2

  32. Datomic's also published a companion blog post to this work (blog.datomic.com/2024/05/Jepse) and extensively revamped documentation! (docs.datomic.com/datomic-overv)

    #Jepsen

  33. Pleased to announce a new #Jepsen report on Datomic Pro 1.0.7075. Datomic is an unusual system in many ways. Temporal! Immutable! Datalog! Strong Session Serializable*! We found that Datomic appears to offer Strong Session Serializable inter-transaction semantics, up to Strong Serializable when using sync or update transactions. However, *within* a transaction, updates appear as if executed concurrently, rather than sequentially. We hope you enjoy the report. 😃

    jepsen.io/analyses/datomic-pro