Mike McCready

- PR #1513 has solved the aws warning. Thanks to @timheilman / @AtofStryker !

- PR #1521 resolved the `express-graphql` issue. Thanks to @timheilman 👍🏻 🚀 !

- This PR should be closed. It requires a manual reconfiguration and update. See https://github.com/cypress-io/cypress-realworld-app/issues/1547

- This could be related to https://github.com/cypress-io/circleci-orb/issues/426 (assigned to @mschile). There doesn't seem to be any mechanism to wait for the database to become available.

## Suggestion If it is not planned to enhance Orb to include a `wait-on` function (again), then use `start-server-and-test` which is already included in devDependencies and unused at this time.

https://circleci.com/developer/orbs/orb/cypress-io/cypress now lists [wait-on](https://www.npmjs.com/package/wait-on)  I don't plan to submit a PR for this. I have found that trying to use Circle CI from a fork is impractical. Either I...

No current failures. I will re-open if necessary.

This issue occurred again today in CircleCI, in the current RWA setup. See https://app.circleci.com/pipelines/github/cypress-io/cypress-realworld-app/5566/workflows/20addbdb-3781-48f2-8fad-0b7c1b6aefa9/jobs/35423 So, unfortunately, I need to re-open 🙁

- This issue is no longer occurring. Possibly this is due to the removal of Windows testing in CircleCI through https://github.com/cypress-io/cypress-realworld-app/pull/1447

The issue is also reproducible with `yarn add` ```shell npm install [email protected] -g mkdir yarn-test cd yarn-test yarn init -y yarn add yarn ``` displays: ```text yarn add v1.22.1 info...