Seth Nickell

I believe this is the first / underlying PR that broke nuxt: [fix: hide unhandled error messages in prod](https://github.com/nitrojs/nitro/pull/2591). Perhaps @pi0 or @danielroe can comment on whether this is intended...

I _suspect_, although have not tested, that this is fixed in nuxt HEAD, which uses its own copy of normalizeErrors ([github](https://github.com/nuxt/nuxt/blob/ed22319cd0e3a11e5bb6c9491fcf067ce8f984c3/packages/nuxt/src/core/runtime/nitro/handlers/error.ts#L114). However, it seems the 3.15.x branch uses nitro's normalizeErrors,...

When I started running this, I get a bunch of non-breaking warnings: ``` code-dot-org-3.12➜ code-dot-org git:(adds-docker-compose-basics) docker compose run dashboard-services WARN[0000] The "SELENIUM_EDGE_VERSION" variable is not set. Defaulting to a...

## UPDATE: these are totally issues with my local environment, I've been playing with replacing aws-google, and I managed to break my local AWS credentials in terrible ways, I'd assume...

The branch upgraded us to selenium-webdriver 4.23.0 (from 4.10.0). I can confirm that Firefox UI tests fail running locally too. The sauce failures were only on Firefox, and appear to...

Using the Applitools Eyes UI, I've merged the baselines for `staging` into this branch. Now when I run [test eyes], it should actually fail if the baslines don't match.

# Fix full page screenshots in applitools eyes The (undocumented, from reading source) first boolean argument to `@eyes.check_window` is "fully", which enables/disables full page screenshots. By passing false here (not...

https://eyes.applitools.com/app/test-results/00000251677612358866/?accountId=mG4DoRfv0ntEgI3XIYBulrKxlZqrHtGwbP3V103ojvLFU110

Eyes test passed ([applitools eyes results](https://eyes.applitools.com/app/test-results/00000251677612358866/?accountId=mG4DoRfv0ntEgI3XIYBulrKxlZqrHtGwbP3V103ojvLFU110)) with staging's baselines imported. There are 5 tests still "Running" long after the test is completed, but I looked at a real test run...

Looks like you have to bump the `ruby-build` version each time you upgrade ruby so it knows about your current ruby version: ``` * execute[install ruby with ruby build] action...