BranchStack caching misbehaves

Bug #948339 reported by Aaron Bentley on 2012-03-06
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
High
Vincent Ladeuil
bzr (Ubuntu)
High
Jelmer Vernooij

Bug Description

As seen in:
https://code.launchpad.net/~abentley/bzr/config-cache-bugs/+merge/96227

Setting values via the config stack triggers a write even though the branch is locked. (test_set_delays_write)

Retrieving values via the config stack of an unlocked branch does not trigger a read, even if the branch is explicitly unlocked (test_use_fresh_values)

Related branches

Vincent Ladeuil (vila) on 2012-03-13
Changed in bzr:
status: Triaged → In Progress
assignee: nobody → Vincent Ladeuil (vila)
importance: Medium → High
Vincent Ladeuil (vila) wrote :

> Setting values via the config stack triggers a write even though the branch is locked. (test_set_delays_write)

Fixed in the associated branch.

> Retrieving values via the config stack of an unlocked branch does not trigger a read, even if the branch is explicitly unlocked (test_use_fresh_values)

See https://code.launchpad.net/~vila/bzr/948339-config-caching/+merge/97256 for why the cost of addressing this is way too high when the aim is to reduce IOs.

Vincent Ladeuil (vila) on 2012-03-29
Changed in bzr:
milestone: none → 2.6b2
status: In Progress → Fix Released
Jelmer Vernooij (jelmer) on 2012-07-11
Changed in bzr (Ubuntu):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Jelmer Vernooij (jelmer)
Jelmer Vernooij (jelmer) on 2012-07-20
Changed in bzr (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers