Is Canvas Data 2 EA broken for the time being?

Jump to solution
phanley
Community Contributor

It looks like the answer is "yes" judging from some other posts from the last few months, but since no one posted my exact issue I'm going to hope the answer is "you doing it wrong"

We've been waiting for CD2, and since the closed beta feels close I figured it was time to poke around the early access and get a feel for what's going on - I gave it the ol' npm i data-access-platform-cli , downloaded the config.json  from the EA blg post, got errors, discovered that apparently the cli doesn’t support node v14+ (or it didn't at some point), installed the version of node that @oxana had said worked on her machine (v10.19.0), removed and reinstalled data-access-platform-cli, relinked it, and still get some errors:

 

 

○ → dap -c path/to/config.json snapshot accounts
[2021-04-09T19:03:58.279Z info]: Requesting snapshot for accounts....
[2021-04-09T19:03:58.311Z error]: TypeError [ERR_HTTP_INVALID_HEADER_VALUE]: Invalid value "undefined" for header "Authorization"
at ClientRequest.setHeader (_http_outgoing.js:473:3)
at new ClientRequest (_http_client.js:203:14)
at Object.request (https.js:289:10)
(etc.)

 

 

 

Since the version I installed was pretty new (1.0.7-4, 4 days) i downgraded to 1.0.19 (from a couple months ago), but still no dice:

 

 

○ → dap snapshot users accounts courses
[2021-04-09T19:45:15.600Z info]: Requesting snapshot for users....
[2021-04-09T19:45:15.605Z info]: Requesting snapshot for accounts....
[2021-04-09T19:45:15.606Z info]: Requesting snapshot for courses....
Renewing...
Renewing...
Renewing...
[2021-04-09T19:45:16.368Z error]: API Request Failure: Request failed with status code 500

 

 


Maybe that's better, I dunno.

 Is there a version that should work?  The 500 error from the older version could be really the same error as the latest version, just a different error message, so maybe something has changed with the config.json file that is undocumented?

Labels (3)
0 Likes
1 Solution
phanley
Community Contributor
Author

I guess I didn't scroll down far enough?  It looks like the 500 error for anything has been standard since December, so I'm starting to think "it's not me, it's it."

View solution in original post

0 Likes