Tyler van der Hoeven

I get ``` { "error": { "errors": [ { "message": "Unknown argument \"type\" on field \"operations\" of type \"Query\".", "extensions": { "code": "GRAPHQL_VALIDATION_FAILED", "exception": { "stacktrace": [ "GraphQLError: Unknown argument...

Oddly enough it works on testnet, just not on https://demo.astrograph.io/graphql/

ETA on when pubnet will be moved to ES? Having testnet mismatched from pubnet greatly reduces the usefulness of this service. :/

I have yes, I can't use that directly though as the output is too large to upload. ``` ✨ Built successfully, built project size is 1 MiB. ⚠️ Your built...

``` // wrangler.toml name = "name" type = "webpack" account_id = "account-id-abc123" workers_dev = true webpack_config = "webpack.config.js" [env.srcmap] webpack_config = "webpack.config.srcmap.js" ``` ``` // webpack.config.js const webpack = require('webpack')...

After extensive testing I can confirm this library broke at this commit https://github.com/Brechtpd/base64/commit/0e3627ccdb03ac8c7b7db52600d12d6ce4856e1c for L2 Arbitrum and I assume other L2s as well. You can see this working via this...

Reverting `mstore8` back to `mstore` resolves this issue.

There's also something here with running the mload through `shl(248, mload(...))`. Just swapping mstore8 for mstore produces invalid base64 strings. Adding back the shl wrapper gets everything working again.

I have an outstanding ticket with the Arbitrum team. We'll see what they say. https://bugs.immunefi.com/dashboard/submission/5898 Also and not necessarily related but what's the difference between your library and OpenZeppelin's? https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/utils/Base64.sol...

Getting this when trying to use `@supabase/ssr` on an Astro site deployed to Pages