twenty icon indicating copy to clipboard operation
twenty copied to clipboard

Cannot create new opportunities after recent update (docker 0.2.3)

Open iamDecode opened this issue 2 years ago • 0 comments

Bug Description

After updating to the latest docker images (server, postgres, front, all 0.2.3), I don't seem to be able to create any new opportunities.

Example: Just create a new opportunity, select a company and wait. The frontend gives a generic:

Screenshot 2024-01-23 at 22 43 12

in the server logs I get a more specific:

  Error: Cannot return null for non-nullable field Mutation.updateOpportunity.
      at completeValue (/app/node_modules/@graphql-tools/executor/cjs/execution/execute.js:421:19)
      at /app/node_modules/@graphql-tools/executor/cjs/execution/execute.js:334:49
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async /app/node_modules/@envelop/core/cjs/orchestrator.js:383:27
      at async YogaServer.getResultForParams (/app/node_modules/graphql-yoga/cjs/server.js:304:26)
      at async YogaServer.handle (/app/node_modules/graphql-yoga/cjs/server.js:77:29)
query time: 110.48989100009203 ms on query opportunity

Expected behavior

The opportunity is created.

Related

Perhaps its useful context that when I click an opportunity, the page I end up at seems half-broken too. I see the normal object details, but the icon/picture and title are missing. Other fields and relations are showing. However, clicking the tasks/notes/files tabs gives me errors, and I am not able to create any of those in those tabs either.

Example: Screenshot 2024-01-23 at 22 49 25

Server response for those:

  Error: Invalid UUID
      at GraphQLScalarType.checkUUID (/app/packages/twenty-server/dist/src/workspace/workspace-schema-builder/graphql-types/scalars/uuid.scalar.js:11:15)
      at coerceInputValueImpl (/app/node_modules/graphql/utilities/coerceInputValue.js:151:26)
      at /app/node_modules/graphql/utilities/coerceInputValue.js:75:16
      at Function.from (<anonymous>)
      at coerceInputValueImpl (/app/node_modules/graphql/utilities/coerceInputValue.js:73:20)
      at coerceInputValueImpl (/app/node_modules/graphql/utilities/coerceInputValue.js:117:34)
      at coerceInputValueImpl (/app/node_modules/graphql/utilities/coerceInputValue.js:117:34)
      at coerceInputValue (/app/node_modules/graphql/utilities/coerceInputValue.js:32:10)
      at coerceVariableValues (/app/node_modules/@graphql-tools/executor/cjs/execution/values.js:68:65)
      at getVariableValues (/app/node_modules/@graphql-tools/executor/cjs/execution/values.js:19:25)

Note

I just got started with the project, and am not sure this is a bug or my mistake in updating incorrectly. Are there any other steps required for upgrading to a newer docker image that I may have missed? Let me know I should move the discussion elsewhere (discord?) Instead. I tried running yarn database:migrate on the server to be sure, but there was nothing to migrate.

iamDecode avatar Jan 23 '24 21:01 iamDecode