for SD

History

Earlier Later

2009-08-26 14:06:31 spang@bestpractical.com 1377 7446405e-ebea-11dd-8386-e1c54aff8af6

alias cli bug (502)

created set to 2009-08-26 14:06:31
summary set to alias cli bug
component set to cli
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
status set to new
milestone set to diana
reporter set to spang@bestpractical.com

2009-08-26 14:04:21 spang@bestpractical.com 1376 7446405e-ebea-11dd-8386-e1c54aff8af6

write tutorial document (469)

milestone changed from cavil to diana

2009-08-26 14:04:13 spang@bestpractical.com 1375 7446405e-ebea-11dd-8386-e1c54aff8af6

sd needs wizard on first run (416)

milestone changed from cavil to diana

2009-08-26 14:04:05 spang@bestpractical.com 1374 7446405e-ebea-11dd-8386-e1c54aff8af6

need better online help when you type "ticket" (387)

milestone changed from cavil to diana

2009-08-26 12:49:24 spang@bestpractical.com 1373 7446405e-ebea-11dd-8386-e1c54aff8af6

Comment on: try getting username/password from config file on pull? (500)

created set to 2009-08-26 12:49:24
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
content set to It's annoying to have to type in my username and password every time I pull from e.g. RT. Perhaps the syncs could store username/password in the config file? But then we'd probably want to make sure the umask on the config file is not world-readable. Don't implement this without thinking a bit more about the security aspect.
ticket set to e236613d-923e-11de-832a-9c1b448538c9

2009-08-26 12:49:24 spang@bestpractical.com 1372 7446405e-ebea-11dd-8386-e1c54aff8af6

try getting username/password from config file on pull? (500)

created set to 2009-08-26 12:49:24
summary set to try getting username/password from config file on pull?
component set to core
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
status set to new
milestone set to diana
reporter set to spang@bestpractical.com

2009-08-26 12:01:44 spang@bestpractical.com 1371 7446405e-ebea-11dd-8386-e1c54aff8af6

2009-08-26 12:00:51 spang@bestpractical.com 1370 7446405e-ebea-11dd-8386-e1c54aff8af6

Comment on: awesome clone failure mode (493)

created set to 2009-08-26 12:00:51
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
content set to This happens when the target replica already exists
ticket set to feefea69-90dc-11de-831b-c08db11b323c

2009-08-25 16:13:06 spang@bestpractical.com 1369 7446405e-ebea-11dd-8386-e1c54aff8af6

Comment on: server does not allow edits from IPV6 loopback address (497)

created set to 2009-08-25 16:13:06
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
content set to It compares against the string '127.0.0.1'. We should allow the IPv6 loopback device too, but even though this seems like a trivial change I'm not sure how to set things up properly locally to test it, so waiting until I or someone else has some time to look this up.
ticket set to 2c145186-9192-11de-8242-b500de27d915

2009-08-25 16:13:05 spang@bestpractical.com 1368 7446405e-ebea-11dd-8386-e1c54aff8af6

server does not allow edits from IPV6 loopback address (497)

created set to 2009-08-25 16:13:05
summary set to server does not allow edits from IPV6 loopback address
component set to core
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
status set to new
milestone set to diana
reporter set to spang@bestpractical.com

2009-08-25 15:54:00 spang@bestpractical.com 1367 7446405e-ebea-11dd-8386-e1c54aff8af6

Comment on: publish should check for rsync >= 2.6.7 (495)

created set to 2009-08-25 15:54:00
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
content set to --chmod was introduced in this version. Don't use this switch if rsync is older than that (but maybe print a warning that this person ought to upgrade).
ticket set to 816699d2-918f-11de-811d-a8b61e21f617

2009-08-25 15:54:00 spang@bestpractical.com 1366 7446405e-ebea-11dd-8386-e1c54aff8af6

publish should check for rsync >= 2.6.7 (495)

owner set to spang@bestpractical.com
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
status set to new
reporter set to spang@bestpractical.com
created set to 2009-08-25 15:54:00
component set to core
summary set to publish should check for rsync >= 2.6.7
milestone set to diana

2009-08-24 18:36:11 spang@bestpractical.com 1365 7446405e-ebea-11dd-8386-e1c54aff8af6

Comment on: awesome clone failure mode (493)

created set to 2009-08-24 18:36:11
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
content set to spang@loki:~/tmp> SD_REPO=hm sd clone --from http://hiveminder.com Prophet::TempUUIDTiny::string_to_uuid():
ticket set to feefea69-90dc-11de-831b-c08db11b323c

2009-08-24 18:36:11 spang@bestpractical.com 1364 7446405e-ebea-11dd-8386-e1c54aff8af6

awesome clone failure mode (493)

created set to 2009-08-24 18:36:11
summary set to awesome clone failure mode
component set to core
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
status set to new
milestone set to diana
reporter set to spang@bestpractical.com

2009-08-24 17:43:27 spang@bestpractical.com 1363 7446405e-ebea-11dd-8386-e1c54aff8af6

Comment on: line width for cli command output should be configurable (428)

created set to 2009-08-24 17:43:27
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
content set to Closing this for now anyway. If the summary-format-being-tied-to-both-web-UI-and-CLI bit is a problem for someone, it will come up later.
ticket set to 25aae909-89a2-11de-80a0-f26ac76196b1

2009-08-24 17:43:27 spang@bestpractical.com 1362 7446405e-ebea-11dd-8386-e1c54aff8af6

line width for cli command output should be configurable (428)

status changed from new to closed

2009-08-24 17:36:18 spang@bestpractical.com 1361 7446405e-ebea-11dd-8386-e1c54aff8af6

Comment on: line width for cli command output should be configurable (428)

created set to 2009-08-24 17:36:18
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
content set to Wrong again. It does pass through sprintf errors... it's just that if the output gets paged, the warnings get obscured. Made this better (print less, explode more).
ticket set to 25aae909-89a2-11de-80a0-f26ac76196b1

2009-08-24 10:23:36 spang@bestpractical.com 1360 7446405e-ebea-11dd-8386-e1c54aff8af6

Comment on: line width for cli command output should be configurable (428)

created set to 2009-08-24 10:23:36
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
content set to Well, it is, via summary-format. The problem is, (1) this is used both for the CLI and the web UI. Maybe we don't want to share. Also, it doesn't pass through sprintf errors, which it should.
ticket set to 25aae909-89a2-11de-80a0-f26ac76196b1

2009-08-24 09:03:21 spang@bestpractical.com 1359 7446405e-ebea-11dd-8386-e1c54aff8af6

shell parsing seems buggy (459)

status changed from new to closed

2009-08-24 09:03:21 spang@bestpractical.com 1358 7446405e-ebea-11dd-8386-e1c54aff8af6

Comment on: shell parsing seems buggy (459)

created set to 2009-08-24 09:03:21
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
content set to Closed by git commit 3a8c431fa495c13435aa212e09f4fe7edc114b0e
ticket set to 2797c308-8dc1-11de-8001-d766e0f30323

Earlier Later