Bug: regression on the current master

[gdassori]

[nuxt] [request error] [unhandled] [500] Cannot set properties of undefined (setting 'value')
  at ./chunks/app/server.mjs:772:18  
  at fn (./chunks/app/server.mjs:147:27)  
  at Object.callAsync (./node_modules/unctx/dist/index.mjs:49:19)  
  at callWithNuxt (./chunks/app/server.mjs:149:23)  
  at applyPlugin (./chunks/app/server.mjs:118:39)  
  at applyPlugins (./chunks/app/server.mjs:127:11)  
  at async createNuxtAppServer (./chunks/app/server.mjs:1046:7)  
  at async Object.renderToString (./node_modules/vue-bundle-renderer/dist/runtime.mjs:172:19)  
  at async ./chunks/handlers/renderer.mjs:384:21  
  at async ./chunks/handlers/renderer.mjs:26:22

[henrycunh]

oh oh, on it!

It happens when you refresh the /settings/model page, right @gdassori?

[gdassori]

Hi @henrycunh, it wasn't on the page you mentioned, but on the home, and it is still happening :-(.

The instance is geppetto[dot]mempool[dot]co (double t!), if it may be helpful for debugging.

[henrycunh]

That's weird! It's working here.

[gdassori]

Could be regarded to the localStorage status ?

[henrycunh]

You're using Chrome? Can you show me the stack trace on the server-side?

[gdassori]

Yes, Chrome is here. This is the log from vercel (500 server error):

[nuxt] [request error] [unhandled] [500] Cannot set properties of undefined (setting 'value')
  at ./chunks/app/server.mjs:772:18  
  at fn (./chunks/app/server.mjs:147:27)  
  at Object.callAsync (./node_modules/unctx/dist/index.mjs:49:19)  
  at callWithNuxt (./chunks/app/server.mjs:149:23)  
  at applyPlugin (./chunks/app/server.mjs:118:39)  
  at applyPlugins (./chunks/app/server.mjs:127:11)  
  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  
  at async createNuxtAppServer (./chunks/app/server.mjs:1046:7)  
  at async Object.renderToString (./node_modules/vue-bundle-renderer/dist/runtime.mjs:172:19)  
  at async ./chunks/handlers/renderer.mjs:384:21

[henrycunh]

Perfect! Just found the bug :]

[gdassori]

Fix confirmed here, thank you @henrycunh :+1: :+1: :+1: