message: [Executor] Log error instead of failing when discarded transaction has non-empty write-set/events
  When this happens it should be a bug in the VM, but it's possible that
  discarding the transaction will not cause very bad things and the system
  can still proceed.
  Closes:
  Approved by: sblackshear
diff: @@ -799,17 +799,17 @@ where
  txn_info_hashes.push(real_txn_info_hash);
  txn_info_hash = Some(real_txn_info_hash);
  }
  - TransactionStatus::Discard(_) => {
  - ensure!(
  - vm_output.write_set().is_empty(),
  - "Discarded transaction has non-empty write set.",
  - );
  - ensure!(
  - vm_output.events().is_empty(),
  - "Discarded transaction has non-empty events.",
  + TransactionStatus::Discard(status) => {
  + if !vm_output.write_set().is_empty() || !vm_output.events().is_empty() {
  + crit!(
  + "Discarded transaction has non-empty write set or events. \
  + Transaction: {:?}. Status: {}.",
  + txn,
  + status,
  );
  }
  }
  + }
  txn_data.push(TransactionData::new(
  blobs,
  