Robert Lynch

This is especially relevant after the re-write 🙂 the number of things we support was greatly reduced when I moved to Gatsby so we'll probably open up a new issue...

Thanks for the report, it's most likely that I messed up copying the IDs over. I'll take a look at it sometime in the next few days

Your suggestion is actually roughly how it was implemented before, with the promotion assignment armor skins being handled totally separately. When I consolidated and normalized all the data I didn't...

> If you do not want to use an environment variable, use the [`os.Unsetenv`](https://pkg.go.dev/os#Unsetenv) function. I called that out in `Alternatives`, and is the approach I ended up going with...

I just ran into this myself. In my application I'm using Postgres, which doesn't support unsigned integers, so the created column by the migration is just a regular [signed] bigint....

I don't think this should be closed; Something in the `URLSessionInstrumentation` implementation seems to cause this since it exclusively happens when that library is initialized. I've tested in a blank...

Looks like the parser broke again, probably a new property type that's not handled. I haven't worked on this project in a while so I'm not sure when I'll revisit...

Full JS error: ``` Context property map -> property -> str property -> string Error Stack [External { parser: MapRes, message: "invalid utf-16: lone surrogate found" }, Parser(ManyTill)] Next 16...