Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Issue 1435283: unit address sometimes changes #3215
Merged
Commits
Show all changes
71 commits
Select commit
Hold shift + click to select a range
d52f8a3
Initial skeleton
2cbe7c2
Build and type fixes
cc135a5
Implementation improvements
3680537
Store default private address in a transaction
b932194
Implement DefaultPublicAddress
aba6899
Initial tests
ebc99b6
Test extension and bugfix
da80257
Test extension
7d185e0
Test extension
1b88d35
Test extension
648bd50
Test extension
5e454ce
Test completion
d0acc7d
Changed signature of unit PublicAddress and PrivateAddress plus chang…
4460db5
Test fix
8abe427
Test fixes
0b49c1d
Test fixes
df17b80
Test fix
255db0e
Change SelectAddress functions to return a network.Address
acc91a8
Test fix
a6e5b78
Client facade address fixes
fac903a
Test fix
acfc894
Test fix
7b3dff9
Test fix
d733443
Initial tests for ExactMatchScope
d0ead5b
Test extension
06ff699
Comment update
3c8d3e9
Add error logging
60d856c
Function rename
aa469c1
Test improvement
4c5441b
Error tracing
cca2453
Whitespace tinkering
c131f2d
Whitespace tinkering
d1a1d72
Add comments
d9c644c
Add comments
e36773e
Better code formatting
8c3a83a
Move import
39b2cdb
Restore megawatcher behaviour
f345ac9
Test unit.PublicAddress and PrivateAddress are stable
5b8a53e
Rename Default to Preferred
6fe7a15
Set preferred addresses on address setting
f42f321
Comment and naming updates
2cc10b1
Correctly set updated addresses on machine doc and better error handling
e137af3
Minor tweaks
015ae17
Test and comment improvements
2f612ee
Improved error handling
7c846df
Network select address functions now return an ok value as well
b1b567f
Test fixes
18b17a4
Test fix
28db34b
Test fix
41380c1
Tweak
c3bec6d
Error and test tweaks
2db0b44
Semantic preservation
4783df8
Better error handling
325e008
More betterer error handling
e3e217c
Remove lies
e439f77
Even more betterer error handling
92bcccd
Minor tweak
c1394c3
Transaction update
afdd3df
Remove code that causes tests to fail
6247617
Not working assert
1382c69
Add comments for later work
c0323df
Fetching of all addresses for picking preferred address is now done i…
0c87d5b
Remove short circuit and update comment
7927957
Add transaction assert (currently failing)
0ee7d88
Working assertion
e0b33fe
Race condition tested
057cb9b
Extend race condition tests
8c32c92
Test extensions
e827129
Add test
cb3f70c
Remove debug logging
530a60e
Method renames
Jump to file or symbol
Failed to load files and symbols.
| @@ -1,86 +0,0 @@ | ||
| -Bazaar Pipelines | ||
| -================ | ||
| - | ||
| -Pipelines are implemented using a bazaar plugin. | ||
| - | ||
| - $ mkdir -p ~/.bazaar/plugins | ||
| - $ bzr branch lp:bzr-pipeline ~/.bazaar/plugins/pipeline | ||
| - | ||
| -Basic info for pipelines can be found using `bzr help pipeline`. | ||
| - | ||
| -Pipelines require lightweight checkouts, but that is how `cobzr` and how the | ||
| -recommendations are specified in the `bazaar-usage.txt` document. | ||
| - | ||
| - | ||
| -Why use pipelines | ||
| -================= | ||
| - | ||
| -Pipelines could be thought of as a doubly linked list of dependent branches. | ||
| - | ||
| -Often when working you need to break up the implementation, either because the | ||
| -work can be more easily reviewed as a collection of small independent changes, | ||
| -or the work can be landed incrementally. | ||
| - | ||
| -Another reason is to avoid mixing new work with other refactoring that occurs | ||
| -during the process of writing the new work. Often when adding new features, | ||
| -other parts of code need to change. The branch is easier to review if the | ||
| -prerequisite changes happen seperately. | ||
| - | ||
| -Sometimes you don't know you want to refactor things until half of it is done | ||
| -already. In this situation you can create a new pipe before the current one, | ||
| -and move the changes into it. | ||
| - | ||
| - $ bzr add-pipe --before some-refactoring-work | ||
| - $ bzr merge -i :next | ||
| - | ||
| -This enters you into an interactive merge of the changes from the next branch | ||
| -in the pipeline. | ||
| - | ||
| - | ||
| -Merging trunk | ||
| -============= | ||
| - | ||
| -When merging trunk into a pipeline, you should move to the first branch in the | ||
| -pipeline. | ||
| - | ||
| - $ bzr switch :first | ||
| - $ bzr merge <trunk> | ||
| - # resolve any conflicts that may be there | ||
| - $ bzr commit -m "Merge trunk" | ||
| - $ bzr pump | ||
| - | ||
| -The pump command is effectively merging each pipe into the next pipe and | ||
| -commits without changing the current active pipe. The pump command starts | ||
| -with the active pipe. If there are conflicts from any particular merge, the | ||
| -pumping stops, and the active branch is set to be the branch that had the | ||
| -conflicts ready for you to fix the conflicts. | ||
| - | ||
| - | ||
| -Useful aliases | ||
| -============== | ||
| - | ||
| - $ bzr alias pipes="show-pipeline" | ||
| - | ||
| -Show the branches in the pipeline. All branches are considered a pipeline | ||
| -with one branch, so you can run this on any branch (actually a lightweight | ||
| -checkout). The current pipe is shown with an `*` at the start of the line. | ||
| - | ||
| - $ bzr alias next="switch-pipe :next" | ||
| - $ bzr alias prev="switch-pipe :prev" | ||
| - | ||
| -These two aliases allow you to move around the pipeline using: | ||
| - | ||
| - $ bzr next # move to the next branch in the pipeline | ||
| - $ bzr prev # move to the previous branch in the pipeline | ||
| - | ||
| - | ||
| - $ bzr alias pdiff="diff -r branch::prev" | ||
| - | ||
| -Show me the differences that this branch has introduced compared to the | ||
| -previous branch in the pipeline. | ||
| - | ||
| - $ bzr alias unpumped="missing --mine :next" | ||
| - | ||
| -Show the revisions that are in the current branch that are not yet in the next | ||
| -branch in the pipeline. | ||
| - |
Oops, something went wrong.