Skip to content
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

Unable to import the O*Net technology skills framework into production #630

Closed
cwd-mparsons opened this issue Nov 19, 2019 · 11 comments
Closed

Comments

@cwd-mparsons
Copy link

I have tried many times to import the O*Net technology skills framework into production.
The import never finishes. Fritz had noted that the import appears to complete internally but no data is written.
I have tried importing for the DOL organization, and for credential engine - both fail.
The latest attempt shows a list of relation urls that I had not seen before. May or may not significant. The image shows there are 3.5mb of additional urls are available - perhaps shows something is happening!

image

@cwd-mparsons
Copy link
Author

Eventually an error message was displayed:
image

@Lomilar
Copy link
Member

Lomilar commented Nov 20, 2019

The technology skills framework imported successfully to Production, but the import request looks like it timed out. It was there when I checked last.

That huge list of updated URLs (it is framework, competencies, and relations) is indeed a sign that the import succeeded, as the server then sent out the list of things that changed.

image

These timeouts and whatnot continue to be a set of performance and scale issues. The next stage of performance improvements is in this issue here:
Eduworks/ec#68

We should continue to look at why the DoL account isn't able to import.

@cwd-mparsons
Copy link
Author

Status
19-11-18
I was able to publish the framework on staging
19-11-20
Production - failed.
I kept running into strange errors while trying to publish the O*Net technology skills, including multiple of: ERR_HTTP2_PROTOCOL_ERROR
I even tried to republish the staging version, which worked Monday – failed as above.
There was some suggestion that the protocol error could be related to a google update. I tried the publish using Firefox and got the same error.

@jeannekitchens
Copy link

@cwd-mparsons @woodkri Is this still open?

@woodkri
Copy link
Member

woodkri commented Jan 29, 2020

Yes, we still need to investigate why the DoL account is unable to import this framework.

@Lomilar
Copy link
Member

Lomilar commented Feb 21, 2020

@mparsons-ce Give this another shot. We did a reimport of all the O*NET frameworks and https://cass.credentialengine.org/api/ceasn/5b3e205efac3276dd7edfdd1345d8530 works in a fairly reasonable amount of time.

@mparsons-ce
Copy link

mparsons-ce commented Feb 21, 2020

@Lomilar
I tried to publish and got the following error:
image

Publisher is supposed to be a list and is being exported as an object:
image

BTW: this is progress, as the error occurs in the API indicating that we were able to export from CaSS and call the API!

@woodkri
Copy link
Member

woodkri commented Feb 24, 2020

I think publisher and creator used to be part of your context and were removed, affecting our translations. I've updated the translation so the "@id" part goes away. You may need to restart Tomcat to see the changes. @mparsons-ce

@siuc-nate
Copy link

Weird. I updated the site the other day, but not with any changes that should have affected the context, especially like that. I'll see if I can figure out what happened.

@siuc-nate
Copy link

siuc-nate commented Feb 24, 2020

Okay, this should be fixed now. Turns out it was due to a change that was made several weeks ago but wasn't actually part of the live site until the other day. It had to do with the way stuff borrowed from other schemas is handled when generating the context (the publisher and creator properties both reference ceterms organizations). Sorry about that!

@mparsons-ce
Copy link

Success!
I was able to publish the framework:
https://credentialengineregistry.org/resources/ce-9fab4187-d8e7-11e9-8250-782bcb5df6ac

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants