Kalan

Good callout, thanks @jheckey - this looks like a leftover in the migration from pyQuil v2 to v3.

Hey @BOBO1997 , please submit issues like this (which may or may not be issues with `pyQuil` itself) to the support team at [email protected]. I've forwarded a link to this...

Saw this on `prost-build` 0.6.0. On upgrade to 0.9.0, it's gone. Without investigating, if I had to guess, it was probably taken care of by the significant refactor in 0.8.0.

Similar situation - the build artifact `react-hooks.cjs.js` includes the line: ``` var _apolloClient = require("apollo-client"); ``` Correcting that to read ``` var _apolloClient = require("@apollo/client"); ``` as a patch fix...

Came up with a hacky workaround after digging into `apollo-link-rest` and this package. Rather than using `onError`, I rewrote my own (below). The intent: intercept a `NetworkError` and conditionally transform...

Hey @dotansimha , it's ready (for review, not merge), just been hoping for input on that question 🙂

Yes, I need answers to the questions I posed here and in the original PR. These are not questions about my plugin, they're about the interaction of the plugin with...

This is important to consider for `v4`: QVM and QPU should return results that are consistent in shape

> In pyquil v3, the constant pi was a float. Specifically, the program constructed like so, > > ```python > import numpy as np > from pyquil.quil import Program >...

Two parts here: 1. We need to make this a first-class concern in `v4` 2. We need to document its behavior front-and-center for users to take advantage of