Sean Gillespie f83d32390c Don't close eventChannel when panicking (#1891) ... * Don't close eventChannel when panicking The state of the system is completely unknown when panicking and in general it's not safe to infer whether or not it is safe to close a channel when in this tate. * CR feedback * Spelling		2018-09-05 17:50:48 -07:00
..
apitype	Clarify refresh text	2018-08-29 17:09:14 -07:00
backend	Don't close eventChannel when panicking (#1891)	2018-09-05 17:50:48 -07:00
diag	Revert "Plumb `LogRequest.IsStatus` through the logging subsystem"	2018-08-31 15:56:53 -07:00
encoding	Add license headers	2018-05-22 15:02:47 -07:00
engine	Fail refreshes with init errors. (#1882)	2018-09-05 14:00:28 -07:00
graph	Add license headers	2018-05-22 15:02:47 -07:00
operations	Save resources obtained from ".get" in the snapshot (#1654)	2018-08-03 14:06:00 -07:00
resource	Clarify control flow in step generator (#1843)	2018-09-05 15:08:09 -07:00
testing	Update test frameworks to new packages	2018-09-05 08:16:14 -07:00
tokens	Remove dead code (#1833)	2018-08-28 14:43:41 -07:00
tools	Add a `WriteString` method to `tools/GenWriter`. (#1839)	2018-08-29 14:43:20 -07:00
util	Clarify control flow in step generator (#1843)	2018-09-05 15:08:09 -07:00
version	Add license headers	2018-05-22 15:02:47 -07:00
workspace	Move away from ${PROJECT} and ${DESCRIPTION} (#1873)	2018-09-05 08:00:57 -07:00