Orion Martin

Related: #454

Yup, looks like we've been relying on `findall_operations_with_gate_type`, which doesn't bother searching inside of `CircuitOperation`s. Modifying that method is probably the right way to resolve this, although because of how...

One additional issue: `findall_operations_with_gate_type` returns a (moment index, op, gate) tuple. For a sub-operation of a `CircuitOperation`, moment index doesn't precisely locate the operation.

Bazel page is returning 404s, need to wait for it to come back and retry.

An inevitable side effect of building GPU support on machines that lack GPU support: we have no way to test GPU behavior in continuous integration. However, since the wheels generated...

This appears to be the result of changes in the Tensorflow toolchain location - hoping to have a fix out later today.

This fix has been delayed due to long-standing inconsistencies between the qsim and Tensorflow build processes, which we're now trying to reconcile. Existing builds of qsim (installed with `pip install...

In the absence of a quick solution for this, we have opted to disable the qsim Windows build to unblock other PRs. We will continue working with the TFQ team...

This is currently held back by https://github.com/actions/virtual-environments/issues/2187 - in short, we use Github Actions to build and release wheels for each platform, but Github Actions has no M1 runners. In...

Investigated with @aasfaw and @mpharrigan, and found that building locally on an M1 is blocked for all versions of qsim except `qsim_basic`. This is because ARM64 does not support the...