-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
unable to see cloud logs after upgrading dashboard to ?.?.? #708
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The latest version of the dashboard is 1.0.25 not sure where you got the version 2.0 of it! |
Hello @flovilmart, i'am not sure how to check the version here is a little extract of my package.json in parse-dashboard
Regards, |
I'm not sure how you got that version, but this is not the latest, as we're at 1.0.25 |
Thanks a lot @flovilmart i have downloaded the right version and know everything is ok, i don't know what happens with my previous Sorry for the wrong issue and thanks for your help, Regards, |
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Dashboard!
You're running version >=1.0.23 of Parse Dashboard.
You're running version >=2.3.2 of Parse Server.
You've searched through existing issues. Chances are that your issue has been reported or resolved before.
Environment Setup
Centos 7
dashboard: 2.0.0
parse-server: 2.4.0
node: 7.10.0
This is my parse dashboard configuration
This is my cloud code test function:
When i call it with a curl i have:
the result is correct and on the parse server i have the trace:
I have seen this topic: #281 and i have try to set the verbose export variable on my parse-server and dashboard
i think i have miss some configuration but i can't find which one,
Thanks a lot,
Canna
Steps to reproduce
https://i.stack.imgur.com/Br1cs.png
As you can see i dont have the log item to display cloud code log
Logs/Trace
Note: If you get a browser JS error please run
npm run dev
. This will provide source maps and a much more useful stack trace.The text was updated successfully, but these errors were encountered: