I’m currently getting Failed to get build job info: error in response: status code 500 Internal Server Error
when attempting to run / update, and also when attempting to publish. There are sufficient cycles ops funds.
The error message isn’t very informative. Is it just me getting this, or is ICP Ninja down at the moment?
Sorry about that… We published a new version and missed to check that the build server is on the latest version (for the second time now. We need a better process…). The update is in progress
1 Like
No worries, thanks for the quick response @Severin
1 Like
The build server is redeployed and builds are fine again
2 Likes
Thanks @Severin. I was using ICP Ninja as a quick and convenient way to try something out. But then discovered the packages that you can depend on are limited and you can’t modify package.json, so I’ve switched to building this locally now.
While I have your ear, could I check if there’s a fundamental reason that agent js shouldn’t be able to query logs for a canister which has the logs set to public? I’ve confirmed that I’ve set the log visibility to public, and I’ve tried to fetch the logs and display them in the browser, but I get -
AgentError: Call failed:
Canister: aaaaa-aa
Method: fetch_canister_logs (query)
"Status": "rejected"
"Code": "CanisterReject"
"Message": "Caller 2vxsx-fae is not allowed to query ic00 method fetch_canister_logs"
I’m using ‘@dfinity/ic-management’. If this simply isn’t allowed for some reason it would be good to know so that I can drop the idea.
Apologies, false alarm. I was specifying the wrong principal accidentally (not the one for the canister that I’d set log visibility to public). Resolved 
1 Like
That is outdated info, same as with the folder structure. I’ll get that page updated…
I’d rather not tell you how many times I’ve done the same… 
1 Like