for SD

History

Earlier Later

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

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

Comment on: sqlite caching interacts badly w/outside editing, e.g. git hooks (487)

created set to 2009-08-24 08:36:27
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
content set to If for example you have a main session in the SD shellnand then you close a ticket via a hook, your cache will be out of date and won't ever be updated.
ticket set to 1b47e7cb-9089-11de-8108-e7487dff914c

2009-08-24 08:35:41 spang@bestpractical.com 1356 7446405e-ebea-11dd-8386-e1c54aff8af6

sqlite caching interacts badly w/outside editing, e.g. git hooks (487)

created set to 2009-08-24 08:35:41
summary set to sqlite caching interacts badly w/outside editing, e.g. git hooks
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 08:25:38 spang@bestpractical.com 1355 7446405e-ebea-11dd-8386-e1c54aff8af6

add --non-interactive to SD usage messages for init/clone (451)

status changed from closed to closed

2009-08-22 13:53:38 spang@bestpractical.com 1354 7446405e-ebea-11dd-8386-e1c54aff8af6

add --non-interactive to SD usage messages for init/clone (451)

status changed from new to closed

2009-08-22 13:53:36 spang@bestpractical.com 1353 7446405e-ebea-11dd-8386-e1c54aff8af6

Comment on: add --non-interactive to SD usage messages for init/clone (451)

created set to 2009-08-22 13:53:36
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
content set to Closed by git commit f3c6ac313c3f948bfb5043250ed0ea981cbee945
ticket set to 49bcc92f-8dab-11de-820f-a0a7844892fa

2009-08-21 23:26:01 spang@bestpractical.com 1352 7446405e-ebea-11dd-8386-e1c54aff8af6

sd server readonly mode appears to have vanished (308)

milestone changed from cavil to diana

2009-08-21 23:25:41 spang@bestpractical.com 1351 7446405e-ebea-11dd-8386-e1c54aff8af6

Comment on: sd server readonly mode appears to have vanished (308)

created set to 2009-08-21 23:25:41
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
content set to Committed a workaround for now--reject changes from non-localhost and kill the doc pointing out --writable. There is now only one server mode, which is world-readable, only-localhost-writeable. Make this better in the future?
ticket set to 3125ABC2-EE5E-11DD-9BD1-E335D30C5955

2009-08-21 18:33:33 spang@bestpractical.com 1350 7446405e-ebea-11dd-8386-e1c54aff8af6

make syncwith.us git repo public (484)

created set to 2009-08-21 18:33:33
summary set to make syncwith.us git repo public
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-21 18:32:45 spang@bestpractical.com 1349 7446405e-ebea-11dd-8386-e1c54aff8af6

make a screencast showcasing SD in action (483)

created set to 2009-08-21 18:32:45
summary set to make a screencast showcasing SD in action
component set to docs
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

Earlier Later