-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathchangelog.txt
70 lines (45 loc) · 1.97 KB
/
changelog.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
Most recent changes first
# From 75aba99012d40fc9d3 to 250ce38bfe8562
- It is now possible to launch instances of a component (for consensus).
stack:add_component(hierarchical_consensus, c_round_1).
- resolved an initialisation race condition
- You may delete the start_link functions from your components.
- adds stack:rank(Node) to get back deterministic 1..N position of Node in
stack:nodes()
changed files:
include/stack_state.hrl
src/component.erl
src/stack.erl
src/stacknodes.erl
# From eb7c78ef6d9be370f to 75aba99012d40fc9d3
Improved launch.sh robustness by adding time-delayed retries to stack:connect.
No longer fails on e.g. n2 loading before n1 and trying to connect to
unavailable n1.
Changed files: stack.erl
# From lsinf2345-framework-b51dadab5f1fbdd2.zip
changed files:
launch.sh
src/component.erl
src/dancing_robots.erl
src/fll.erl
src/fll_transmit.erl
src/sl.erl
src/stack.erl
- component:start_timer now sends only once, you must call it again in your
timeout event handler to get more timeout events (as in the book algos)
- component:start_timer takes different event triggers as its second argument
e.g. component:start_timer(2000, timeout_gc).
- sl.erl updated to use the new timer, check your code for the same problem
- Dancing robots app has been updated to use new timers. Step counting stop condition revised.
The following changes smooth out some problems with application initialisation
(nodes seen by p at init) and make it easier to start and shut down all nodes
- launching component on all connected nodes now provided by stack:launch_cluster_application(Component)
- shutting down all stack nodes now provided by stack:halt_cluster.
- added launch.sh which launches n nodes in xterms, usage: ./launch.sh 5
suggested way to run the program is now:
./rebar clean compile eunit
./launch.sh 5
and in one of the Erlang shells:
stack:launch_cluster_application(dancing_robots).
then when finished, in one of the nodes:
stack:halt_cluster().