Ulf Wiger
Ulf Wiger
It might be possible to detect accidental reordering by saving a limited number of `am_leader` and checking lock versions. Another approach might be to double-check `am_leader` messages against the most...
Pls note PR #42 It still doesn't solve all issues, but I think it goes further in allowing the problems to be identified.
Note: some issues identified. Still debugging.
@xinhaoyuan sorry for the long delay, but would you like to inspect the proposed fix?
From an implementation point of view, it would be pretty straightforward. One would have to think through whether it could cause problems with the algorithm, but I don't think it...
Well, `locks_server` has a function `remove_agent()`, which among other things calls `remove_agent_from_lock()`. This could be a starting point for an unlock operation. In the `locks_agent` module, there is a `remove_locks()`...
Indeed. Will fix.
Well, perhaps the correct return should be `{no_locks, []}`, since when `await_all_locks()` is called, the locks_agent calls `all_locks_status()`, which can result in `no_locks`. However, the `notify()` function doesn't currently translate...
Hmm, :) Thanks. I'll take a look at this a bit later on. BR, Ulf Den 11 mars 2012 12:27 skrev Sergei Lebedev < [email protected] > : > > I...
I haven't fixed it yet. The problem is that the function '#pos-'(Rec, Attr) will never return for an empty record. The code that generates a type signature for all possible...