jbrunton / chat-demo-legacy Goto Github PK

• Rename profile name (#125).
• Update prior messages.
• Make the notification transient.

There's currently a direct dependency on adapter. This can be refactored using reader monad.

Seeing failures on cleanup-stacks, leaving some remaining resources.

• Reusable fixtures for repos and request/response processing.
• Maybe some shared types or library code for request processing, to (a) provide a common structure (parse request -> process request -> generate response) and (b) DRY up code if possible.
• Need some middleware for handling exceptions – which might include a switch to fp-ts RTE monad.

Maybe use prepublishOnly script from npm plugin, or exec plugin to build.

• Docker image tags don't get removed
• The Pulumi stack is never deleted (fixed with #110)

• On visiting a new room, user is given the option to "join"
• User can only post to "joined" rooms
• There is a list of joined rooms in a sidebar
• A room can be made "private", in which case: (a) joining must be approved, and (b) discussion cannot be viewed until joined
• A room can be made "public:read", in which case: (a) joining must be approved, but (b) discussions can be viewed without joining
• A room can be made "public:write", in which case anyone can immediately join
• Renaming a room updates the menu

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• fix(deps): update all non-major dependencies (@pulumi/aws, @pulumi/digitalocean, @pulumi/pulumi, @pulumi/random, @types/express, @types/jest, @types/node, @types/react, @types/react-dom, @types/semantic-release, @typescript-eslint/eslint-plugin, @typescript-eslint/parser, antd, cypress, eslint, eslint-config-prettier, husky, jest, lint-staged, next-auth, nodemailer, prettier, sequelize, ts-jest, tsconfig-paths, typescript)
• chore(deps): update dependency @types/semantic-release to v20
• chore(deps): update dependency semantic-release to v20
• chore(deps): update pulumi/actions action to v4
• fix(deps): update dependency @ant-design/icons to v5
• fix(deps): update dependency @pulumi/awsx to v1
• fix(deps): update dependency antd to v5
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update nextjs monorepo to v13 (major) (eslint-config-next, next)
• chore(deps): update node.js to v19

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• chore(deps): update dependency @types/node to v18

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Maybe use pulumi automation framework to tidy up empty stacks and alert on unused ones.

Sign in by email sometimes entails a delay.

🚨 The automated release from the semantic-release branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the semantic-release branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch semantic-release on the remote Git repository with URL https://x-access-token:[secure]@github.com/jbrunton/chat-demo.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

Good luck with your project ✨

Your semantic-release bot 📦🚀

• Ship logs to Logz.io
  • #177
  • #183
  • #185
• Correlation IDs
• Consider a JSON logging format for prod
• Metrics with Grafana/Prometheus
• Log http responses

See also https://medium.com/@JaouherK/creating-a-human-and-machine-freindly-logging-format-bb6d4bb01dca

Local logs:

error - (api)/src/app/dependencies/index.ts (73:10) @ withReqDeps
error - Error: dispatcher is undefined
    at withReqDeps (webpack-internal:///(api)/./src/app/dependencies/index.ts:57:15)
    at eval (webpack-internal:///(api)/./src/app/utils/api.ts:35:77)

This is a race condition, because the dispatcher is only created when a user open a websocket.

• Each new room has ID, owner and optional name (#120)
• Each room has message history (#123)
• Add a rename room command (only for owner) (#121)