PARSE DASHBOARD unable to see cloud logs after upgrading dashboard - parse-platform

After updating my parse-dashboard i lost the "logs column" as you can see:
I just upgraded my parse-dashboard and my parse server:
dashboard: ?.?.? (package.json https://pastebin.com/KRFaxJha)
parse-server: 2.4.0
node: 7.10.0
This is my parse-dashboard configuration file:
{
"apps": [
{
"appId": "APP_ID",
"masterKey": "MASTER_KEY",
"restKey": "REST_KEY",
"serverURL": "http://WWW_WEBSITE:8081/parse",
"appName":"APP_NAME"
}
],
"users": [
{
"user": "ADMIN",
"pass": "ADMINXXXXXXX"
}
]
}
This is my cloud code test function:
Parse.Cloud.define("hello", function(request, response) {
response.success("Hello world!");
});
When i call it with a curl i have:
curl -X POST -H "X-Parse-Application-Id: APP_ID" -H "X-Parse-REST-API-Key: REST_KEY" -H "Content-Type: application/json" -d '{ }' http://WWW_WEBSITE:8081/parse/functions/hello
{"result":"Hello world!"}
the result is correct and on the parse server i have the trace:
verbose: REQUEST for [POST] /parse/functions/hello: {} method=POST, url=/parse/functions/hello, user-agent=curl/7.29.0, host=WWW_WEBSITE:8081, accept=*/*, x-parse-application-id=APPID, x-parse-rest-api-key=REST_KEY, content-type=application/json, content-length=3,
info: Ran cloud function hello for user undefined with:
Input: {}
Result: "Hello world!" functionName=hello, , user=undefined
verbose: RESPONSE from [POST] /parse/functions/hello: {
"response": {
"result": "Hello world!"
}
} result=Hello world!
I have seen this topic:
https://github.com/parse-community/parse-dashboard/issues/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

Bad dashboard version i don't know why:
npm install -g parse-dashboard fix it and installed the good dashboard version

Related

Is there a way to debug transactions in RSK network, which could be the best way?

We are running an RSK node, some smart contract transactions show internal errors, but the message related to the failed require condition doesn't appear in those error messages...
We only see "internal error" and are unable to see which specific error occurred.
If your contract emits messages in the reversions, then you can find them out by using debug_traceTransaction.
NOTE: The debug RPC module is enabled by default in RSK config, but this is disabled on public nodes.
Furthermore, the RSK public nodes do not expose this feature, and you must run your own node in order to do so.
The following assumes that you have a local node running with RPC exposed on port 4444.
First, you need to enable debug module in your config file:
modules = [
...
{
"name": "debug",
"version": "1.0",
"enabled": "true",
},
...
]
Then, you can execute the RPC method passing the
transaction ID as a parameter, like in this example:
curl \
-X POST \
-H "Content-Type:application/json" \
--data '{"jsonrpc":"2.0","method":"debug_traceTransaction","params":["0xa9ae08f01437e32973649cc13f6db44e3ef370cbcd38a6ed69806bd6ea385e49"],"id":1}' \
http://localhost:4444
You will get the following response
(truncated for brevity):
{
...
"result": "08c379a00000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000001e536166654d6174683a207375627472616374696f6e206f766572666c6f770000",
"error": "",
"reverted": true,
...
}
Finally, convert result from hexadecimal to ASCII,
to obtain a readable message:
Ãy SafeMath: subtraction overflow

build-spec Error parsing spec file: expected value at line 1 column 1

I am following the Substrate Developer Hub tutorial in here: https://substrate.dev/docs/en/tutorials/start-a-private-network/customspec
I have successfully executed the command:
./target/release/node-template build-spec --disable-default-bootnode --chain local > customSpec.json
But when I try to parse this last file using this command:
./target/release/node-template build-spec --chain=customSpec.json --raw --disable-default-bootnode > customSpecRaw.json
I got the following error:
Error: Input("Error parsing spec file: expected value at line 1 column 1")
The contents of the customSpec.json are:
{
"name": "Local Testnet",
"id": "local_testnet",
"chainType": "Local",
"bootNodes": [],
"telemetryEndpoints": null,
"protocolId": null,
"properties": null,
"consensusEngine": null,
"lightSyncState": null,
"genesis": {
"runtime": {
"frameSystem":
...
...
"palletSudo": {
"key": "5GrwvaEF5zXb26Fz9rcQpDWS57CtERHpNehXCPcNoHGKutQY"
}
}
}
}
I am attempting the Hello World Hackathon by Polkadot.
Thank you in advance.
I was having this problem on when I was building the chain spec using Windows Powershell. But I used the regular Windows Console and it worked fine.

Spaceship::UnexpectedResponse: [!] Missing required information to submit for external testing - Missing requied data

I'm facing this issue, while running fastlane pilot command in terminal. How should i use this " beta_app_review_info" as a parameter? what value need's to be added?
Here's the command i've tried to run but getting failed with "beta_app_review_info' value must be a Hash! Found String instead."
fastlane pilot upload --username="XXX#gmail.com" --verbose --changelog "$(cat changelog1.txt)" --distribute_external true --groups="Users" --ipa="build/Release-iphoneos/some.ipa" --beta_app_review_info “contact_email: "XXXXX#gmail.com",contact_first_name: "test",contact_last_name: "user",contact_phone: "XXXXXX",demo_account_name: "testuser#gmail.com",demo_account_password: "XXXX"
looks like beta_app_review_info is not included as parameter in Fastlane pilot. Can someone help me to sort out this issue?
Had the same issue. Probably, AppStore start to require extra meta data. Adding beta_app_review_info did fix the problem.
Sample:
upload_to_testflight(
beta_app_review_info: {
contact_email: "email#email.com",
contact_first_name: "Connect",
contact_last_name: "API",
contact_phone: "5558675309",
demo_account_name: "demo#email.com",
demo_account_password: "connectapi",
notes: "this is review note for the reviewer <3 thank you for reviewing"
},
localized_app_info: {
"default": {
feedback_email: "default#email.com",
marketing_url: "https://example.com/marketing-defafult",
privacy_policy_url: "https://example.com/privacy-defafult",
description: "Default description",
},
"en-GB": {
feedback_email: "en-gb#email.com",
marketing_url: "https://example.com/marketing-en-gb",
privacy_policy_url: "https://example.com/privacy-en-gb",
description: "en-gb description",
}
},
localized_build_info: {
"default": {
whats_new: "Default changelog",
},
"en-GB": {
whats_new: "en-gb changelog",
}
}
)
Reference: https://docs.fastlane.tools/actions/upload_to_testflight/

How to get OKTA implicit response without callback (Desktop app)

Can i get okta authentication worked in Desktop applications ? Where i just want to hit okta api to get access token and other details in response ?
As per my understanding it looks for some redirect_uri which i do not have in case of desktop application. Any recommendation ?
I tried it with my web application that works fine.
with following parameters
const openIdConnectUrl = 'https://xxxx.okta.com/oauth2/default';
const clientId = 'xxxxxxxxxxxxxxxxxxx';
const redirectUri = 'http://xxxx.com/yyy/zzz';
Reqeust
curl -v -X POST \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-d '{
"username": "xxxx#example.com",
"password": "xxxxxx",
"relayState": "/myapp/some/deep/link/i/want/to/return/to",
"options": {
"multiOptionalFactorEnroll": false,
"warnBeforePasswordExpired": false
}
}' "https://${yourOktaDomain}/api/v1/authn"
provides response like
{"expiresAt":"2019-11-13T06:27:03.000Z","status":"SUCCESS","sessionToken":"20111PJIKs504fXVoLs-9zf4t8YoVzMCEvlUbcnjDnPhqSk7C-YPzCL","_embedded":{"user":{"id":"xxxxxxxxxxxxxxx","passwordChanged":"2019-11-13T03:20:33.000Z","profile":{"login":"xxxxxx#gmail.com","firstName":"xxxx","lastName":"xxxx","locale":"en","timeZone":"America/Los_Angeles"}}},"_links":{"cancel":{"href":"https://dev-924234.okta.com/api/v1/authn/cancel","hints":{"allow":["POST"]}}}}
Refer the below documentation if needed.
https://developer.okta.com/docs/reference/api/authn
Although it did not serve my purpose completely. But it can help you.

Ansible Tower API not accepting token

I am performing the following POST in a Tower server:
http://<my-tower-url>/api/v2/job_templates/10/launch/
Headers:
Content-Type:application/json
Authorization:sometokenhere
And getting back the error:
{"detail":"Authentication credentials were not provided."}
Have also tried the following:
Headers:
Content-Type:application/json
Authorization:Token sometokenhere
as suggested here.
Same happens when passing raw username/password in the POST body as follows (and skipping the Authorization header):
{
"username": "myusername",
"password": "mypass",
"inventory": "inventoryname",
"verbosity": 0,
"extra_vars": {
"var1": "somevar1",
"var2": "somevar2",
"var3": "somevar3",
"var4": "somevar4",
"var5": "somevar5"
}
}
Any idea why this is not working?
Authorization: Bearer <oauth2-token-value>
See here, Section "3. OAuth 2 Token Authentication", part "Curl Example".
I ended up using basic auth as follows:
1.create the user which you want to run your ci jobs with
2.perform the following post at the respective CI job:
curl -o /dev/null -s -w \"%{http_code}\n\" -X POST http://<my-tower-url>/api/v2/job_templates/10/launch/ \
-H \"authorization: Basic $MY_AUTH_TOKEN\" \
-H \"content-type: application/json\" \
-d \"#awx_data.json
Where
awx_data.json is a file holding the actual POST body
MY_AUTH_TOKEN is the tyical base64 encoded username+password of the above user
You can also assign the above result and check it against 201 which is what AWX returns upon successful job creation.
Polling the AWX server to check if the job was successfully finished is another story of course.

Resources