Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upOccasional failure to copy #1
Comments
This comment has been minimized.
This comment has been minimized.
Full copy of the error message with redacted API Key
|
This comment has been minimized.
This comment has been minimized.
Yes, will do. BTW, the purpose of this prototype is to elicit feedback on what the core capability should ultimately be. I'm all ears! We'd also be interested to know more about the workflow that motivates all this copying. |
This comment has been minimized.
This comment has been minimized.
We're moving annotations from a private to a public group (and we want both groups to exist, so this isn't about converting the group). |
This comment has been minimized.
This comment has been minimized.
OK, that makes sense. The SciCrunch project does a similar kind of data release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
adam3smith commentedOct 9, 2019
We've been using this with great success, but for pages with a relatively large number of annotations, there are often a number of failures, with no discernible pattern. The counter just stops and the web console shows "rejected" with "TypeError: "NetworkError when attempting to fetch resource." (I have included the full error in a comment). Right before that is a CORS warning
"Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://hypothes.is/api/annotations. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing)."
but it seems like that shouldn't matter given that other items do copy.
I'm guessing this might just be an API glitch? Would it be worthwhile just re-trying failed annotations? If not, could the tool display a more user-friendly error message?