Miguel Carvajal
Miguel Carvajal
Any updates on this?
I am also having the same error, a `204` status code been returned from the proxied server is been converted into a `502` status code.
AFK right now. Will give it a shoot later on and post an example here.
I don't think the warning is completely harmless as mentioned above. If I try to restore the dump later on using `timescaledb-parallel-copy` I get the error described in https://github.com/timescale/timescaledb-parallel-copy/issues/38 which...
We also need this.
Any chance of this been merged?
I will look into it.
Hey, thanks for creating an issue. Can you elaborate more on this? Like what kind of behaviour are you expecting to see. And how that is not possible to be...
Thats a tricky problem. Maybe having instead of only one option we can add those other common ones like you mentioned?
@strass can you explain why your [solution above](https://github.com/apollographql/apollo-link/issues/855#issuecomment-521351718) fixes the issue. IMO they do exactly the same thing using the `forEach` and the `map`.