GitHub PushEvent at 2014-03-14 18:22:40
Repository: SALVE
Actor: sirosen
Payload: {"shas":[["cd31ddcf37e5d7d906ae14b9bc699b352046a285","860a2943edf6314a8c980d17761b014c9b568196@uchicago.edu","Added settings for log levels and util for run logging.\n\nReplaces all prints not directed at files with uses of the new log utility.\nFixes for scratch containers to include logging settings, does not set WARN\nor INFO in order to keep tight control of messages.\nAddition of INFO logging for phase transitions. Some tweaks were needed to\ncorrectly set log levels during unit tests. Induces some DRY violations in\nthe test suite.","Stephen Rosen",true],["563c613c2137c8c419d6c36d973f3cf6797b840f","860a2943edf6314a8c980d17761b014c9b568196@uchicago.edu","Added exception handling for ini parsing failures.\n\nSALVE now accurately reports the results of a parsing failure.\nThere is no logging before log_level is set.\n\nAlso, suppressed INFO output during tests.\nThere was an instance of logging taking place during config loading\nas a result of state transitioning. Since the distinction between\n\"STARTUP\" and \"CONFIG_LOADING\" is not particularly large right now,\nthe simple solution is to remove the CONFIG_LOADING state.","Stephen Rosen",true],["63e4888682b64bae02e6d68529f65ff90ae2157b","860a2943edf6314a8c980d17761b014c9b568196@uchicago.edu","Added a verbosity setting and defaults for globals.\n\nAlthough sensible defaults are specified through the default_settings.ini file,\nthese are exposed directly to the user for modification. It is safer, therefore,\nfor there to be a set of \"true\" defaults underlying these, which are set when\nvalues are not specified.\nAdded min_verbosity constraint to INFO logging. Verbosity levels are adjustable\nand modify which messages are seen.","Stephen Rosen",true],["7b5f013559a41c37ae3b19434a2c7ebc79aa1c9e","860a2943edf6314a8c980d17761b014c9b568196@uchicago.edu","Merge branch 'feature/log-control' into dev","Stephen Rosen",true],["b741a595b13628fc50f6110936b06e461d410c7e","860a2943edf6314a8c980d17761b014c9b568196@uchicago.edu","Added definitions for a FilesystemExpectation.\n\nThe basic purpose of a FilesystemExpectation is to track the state that\nthe filesystem will be in at the time that each action is executed.","Stephen Rosen",true],["c0bc0bbf1b3cdc286fa5c10f4d12ed3310563419","860a2943edf6314a8c980d17761b014c9b568196@uchicago.edu","Fix for missing import in src.expect.filesys","Stephen Rosen",true],["87cac3eff358888c4548689c0c8d79049989c6a6","860a2943edf6314a8c980d17761b014c9b568196@uchicago.edu","Added func to create expectations from existing filesys\n\nNecessary as a basis for a filesystem expectation. Expectations are a union between\nthe existing state of the filesystem and the application of actions.","Stephen Rosen",true],["9f5c9ddfec2fa9aae5c62c7a3f005e8c29ce34a4","860a2943edf6314a8c980d17761b014c9b568196@uchicago.edu","Improved permissions checking when converting files to expectations.","Stephen Rosen",true]],"size":8,"ref":"refs/heads/working/feature/verify-pre-deploy","head":"9f5c9ddfec2fa9aae5c62c7a3f005e8c29ce34a4"}