Martin von Zweigbergk e0112a4be0 transaction: report failure to close transaction only in debug builds ... When a transaction gets dropped without being committed or explicitly discarded, we currently raise an assertion error. I added that check because I kept forgetting to commit transactions. However, it's quite normal to want to drop transactions in error cases. The current assertion means that we panic and don't report the actual error to the user in such cases. We should probably audit the code paths where we commit transactions and decide for each if we simply want to to discard the transaction or not. In some cases, we may want to commit the transaction without integrating it in the operation log (i.e. without creating a file entry in .jj/views/op_heads/). However, we can do that later. For now, let's just make sure we don't panic when dropping the transaction in release builds.		2021-02-07 00:11:42 -08:00
..
protos	view: add tracking of "public" heads (copying Mercurial's phase concept)	2021-01-16 11:48:35 -08:00
src	transaction: report failure to close transaction only in debug builds	2021-02-07 00:11:42 -08:00
tests	transaction: when checking out open commit with conflicts, create child commit	2021-01-22 11:41:52 -08:00
build.rs	protobuf: generate code at build-time	2020-12-24 01:05:17 -08:00
Cargo.toml	cargo: release 0.1.1	2021-01-03 23:06:46 -08:00