15414866596
51%
master: 51%

Ran 03 Jun 2025 10:36AM UTC

Jobs 1

Files 0

Run time –

Badge

Embed ▾

pending completion

Build # 15414866596

Build Type

push

github

Committed by

just-now

Commit Message

fix: parent context timeout is now propagated to dialContext

A new Context object was previously created for dialContext without
associating it with the top-level context. As a result, timeouts from
the top-level context were not propagated, causing ErrNoAvailableLeader errors.

The issue has been resolved by deriving dialContext from the parent context,
ensuring proper timeout and cancellation propagation.

Steps to reproduce the bug before the current commit:
 - Run dqlite demo cluster

   dqlite-demo --api 127.0.0.1:8001 --db 127.0.0.1:9001
   dqlite-demo --api 127.0.0.1:8002 --db 127.0.0.1:9002 --join 127.0.0.1:9001
   dqlite-demo --api 127.0.0.1:8003 --db 127.0.0.1:9003 --join 127.0.0.1:9001

 - Partition out the leader from the cluster

   sudo iptables -A INPUT -p tcp --sport 9001 -j DROP
   sudo iptables -A INPUT -p tcp --sport 8001 -j DROP

 - Run dqlite client to query the leader

   dqlite -s file://cluster.yaml demo .leader

Run Details

Jobs

ID	Job ID	Ran	Files	Coverage
1	15414866596.1	03 Jun 2025 10:36AM UTC	41		GitHub Action Run

Source Files on build 15414866596

Detailed source file information is not available for this build.

canonical / go-dqlite / 15414866596
51%
master: 51%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 15414866596

canonical / go-dqlite / 15414866596 51% master: 51%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 15414866596

canonical / go-dqlite / 15414866596
51%
master: 51%

README BADGES
x