Open diegofrsilva opened 6 years ago
I am having the exact same issue. Using Node v9.11.1
+1
I get it too, but it doesn't seem to affect any functionality of the webapp. Does this prevent you from using the webapp in any way? If you open the browser devtools network tab, do you see any failed request (response status 4xx or 5xx) ?
I want to address this properly anyway, but I'm trying to understand the urgency of this.
Namespaces are not properly loaded for me, and I see the same error messages.
Ran into this issue today. It does prevent usage. At least for me, it's perpetually stuck loading the contents of the default namespace.
Indeed, even though the error message is there, it works. I'll keep the Issue as open because others reported they are blocked by this. @GabiAxel Feel free to close it if it isn't blocking others.
I'm blocked too
Same here, running node 8.15.0. The namespaces
and kinds
requests are sent but don't get a response. GUI is stuck at "Loading..."
+1
I resolved this issue.
Project name and host is should be same as your environment.
You can check it when run gcloud beta emulators datastore env-init
.
DATASTORE_DATASET
and DATASTORE_HOST
are correct.
@noppefoxwolf, can you say how exactly you have made it work?
For me, I tried the following:
localhost:5000
localhost:8081
by running gcloud beta emulators datastore start
$(gcloud beta emulators datastore env-init)
My environment variables are as follows:
export DATASTORE_DATASET=my-project-id
export DATASTORE_EMULATOR_HOST=localhost:8081
export DATASTORE_EMULATOR_HOST_PATH=localhost:8081/datastore
export DATASTORE_HOST=http://localhost:8081
export DATASTORE_PROJECT_ID=my-project-id
My question is: what exactly should be the values for DATASTORE_DATASET
and DATASTORE_HOST
in my scenario?
If you can guide me here, it is appreciated beyond words.
Hi, I'm facing the following problem when I try to execute the project.
Env:
Error: [Tue Jun 05 2018 12:58:50 GMT+0000 (UTC)] WARNING { Error: Some middleware threw an error that was not handled properly. This can happen when you do this:
To catch and handle these types of errors, add a route to the end of your middlewares to handle errors like this:
Please feel free to open an issue in Github asking for more info: https://github.com/franciscop/server
status: 500, namespace: '/plugin/final/', code: '/plugin/final/unhandled', id: 'plugin-final-unhandled' } [Tue Jun 05 2018 12:58:50 GMT+0000 (UTC)] ERROR Error: Can't set headers after they are sent. at validateHeader (_http_outgoing.js:491:11) at ServerResponse.setHeader (_http_outgoing.js:498:3) at ServerResponse.header (/home/node/.config/yarn/global/node_modules/express/lib/response.js:767:10) at ServerResponse.send (/home/node/.config/yarn/global/node_modules/express/lib/response.js:170:12) at stack.push.ctx (/home/node/.config/yarn/global/node_modules/server/reply/reply.js:152:13) at Reply.exec (/home/node/.config/yarn/global/node_modules/server/reply/reply.js:175:11) at processReturn (/home/node/.config/yarn/global/node_modules/server/src/join/index.js:11:22) at Object.middle (/home/node/.config/yarn/global/node_modules/server/src/join/index.js:43:17) at