-
Notifications
You must be signed in to change notification settings - Fork 9
Issues: SeattleTestbed/affix
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Affix string without parameters still overwrites Affix constructor's default values
enhancement
#51
opened Jun 11, 2014 by
aaaaalbert
Affix components should (generally) support logging.
Newcomer
#35
opened Mar 11, 2014 by
JustinCappos
How do we name a branch that uses the same ip/port as the root AFFIX?
question
#24
opened Nov 22, 2013 by
monzum
Is a single AFFIX component or every component responsible for the connection name/locator?
question
#23
opened Nov 22, 2013 by
monzum
Modify parse_affix_string() in affixmisc.repy to reject certain AFFIX strings.
bug
#21
opened Nov 20, 2013 by
monzum
Write more fine grained test for the core AFFIX code.
Task
Unit Tests
#13
opened Sep 27, 2013 by
monzum
The AffixStack.copy() method has been changed to use advertise string.
question
#11
opened Sep 25, 2013 by
monzum
ProTip!
Exclude everything labeled
bug
with -label:bug.