Cherry picks from release/1.2

[arnfinn]

Description

Cherry-picked all the commits that were on the release/1.2 branch but not on the master branch.

Motivation and Context

Make sure master is up to date. master is now identical to release/1.2.

Types of changes

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Questions

• [ ] I have cherry-picked all the commits, including "Bump version to..." and "Records tag for...". I am not sure the latter commits are necessary to cherry-pick, but this one made me unsure: 809e4a9a6013edb In this commit, tools/versioner.py was also changed, which I guess we want to include on master.
• [ ] Maybe rebase these commits into master?

Status

• [x] Ready to go
• [ ] Cherry-pick to latest release branch

[MinazoBot]

	1 Warning
:warning:	There are code changes, but no corresponding tests. Please include tests if this PR introduces any modifications in behavior.

Generated by :no_entry_sign: Danger

[codecov[bot]]

Codecov Report

Merging #166 into master will not change coverage. The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #166   +/-   ##
=======================================
  Coverage   70.01%   70.01%           
=======================================
  Files          92       92           
  Lines        5592     5592           
=======================================
  Hits         3915     3915           
  Misses       1677     1677

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 1c2e836...dd493cf. Read the comment docs.

[arnfinn]

@robertodr Is this OK?

[robertodr]

Yes, this should be merged back to `master, but I haven't had time to think about it carefully yet.