Upload issue v0.4.1/3

[baiddd]

Hi,
After many many tests, the website often returns me such errors while "upload as a new deposit":

I tried to log out and log in, refresh tag to make sure I had the latest version, it continues since this afternoon
This always happened after the error during the logging session :

the authorization paged blocked at imjoy login healper

I should then re-login and the error message popped up as I mentioned before for "upload as a new deposit"
Sorry for the distribution, could you again take a closer look?

[oeway]

I just changed the version to 0.4.2, could you try to refresh until you get that and try it again. It should have been fixed.

…

On Mon 9 Aug 2021 at 18:23, Jiachuan Bai ***@***.***> wrote: Hi, After many many tests, the website often returns me such errors while "upload as a new deposit": [image: image] <https://user-images.githubusercontent.com/56833522/128737889-05c058bb-62ed-41c8-a442-767bd913dc39.png> [image: image] <https://user-images.githubusercontent.com/56833522/128738274-02dedb49-be62-4667-b15a-10f2d698a090.png> I tried to log out and log in, refresh tag to make sure I had the latest version, it continues since this afternoon This always happened after the error during the logging session : [image: image] <https://user-images.githubusercontent.com/56833522/128738645-22a83b76-fb6b-478b-b46c-ca426d3def73.png> the authorization paged blocked at imjoy login healper <https://imjoy.io/login-helper#token_type=Bearer&state=5hmmrtowle&user=%7B%27id%27%3A+u%2779598%27%7D&access_token=PCgemoPXKu3ILdVWWvRGfKrl5q41E1&scope=deposit%3Awrite+deposit%3Aactions&expires_in=3600> I should then re-login and the error message popped up as I mentioned before for "upload as a new deposit" Sorry for the distribution, could you again take a closer look? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#51>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADU3S4P7CAPUJYSME523FDT376GNANCNFSM5B2LN2RA> .

[baiddd]

Hi again,

I didn't stop trying since yesterday :(, the similar errors are always shown in different update states, Is that because you make new commits? to make sure it is now version 0.4.3

xhr.js:177 PUT https://sandbox.zenodo.org/api/files/8228b025-d5ac-4aa6-9501-57d082129f28/sample-6/data.smlm?access_token=7Kyunk6VLWUlpoG6CGjFqLRlS9JXlX 404 (NOT FOUND)
(anonymous) @ xhr.js:177
(anonymous) @ xhr.js:13
(anonymous) @ dispatchRequest.js:52
Promise.then (async)
(anonymous) @ Axios.js:61
(anonymous) @ Axios.js:87
(anonymous) @ bind.js:9
(anonymous) @ utils.js:877
l @ runtime.js:45
(anonymous) @ runtime.js:274
(anonymous) @ runtime.js:97
n @ asyncToGenerator.js:3
s @ asyncToGenerator.js:25
(anonymous) @ asyncToGenerator.js:32
(anonymous) @ asyncToGenerator.js:21
t @ utils.js:490
(anonymous) @ Upload.vue:817
l @ runtime.js:45
(anonymous) @ runtime.js:274
(anonymous) @ runtime.js:97
l @ runtime.js:45
A @ runtime.js:337
(anonymous) @ runtime.js:248
(anonymous) @ runtime.js:97
l @ runtime.js:45
A @ runtime.js:337
(anonymous) @ runtime.js:248
(anonymous) @ runtime.js:97
n @ asyncToGenerator.js:3
s @ asyncToGenerator.js:25
utils.js:879 Error: Request failed with status code 404
    at createError.js:16
    at settle.js:17
    at XMLHttpRequest.f.onreadystatechange (xhr.js:62)
(anonymous) @ utils.js:879
l @ runtime.js:45
(anonymous) @ runtime.js:274
(anonymous) @ runtime.js:97
n @ asyncToGenerator.js:3
c @ asyncToGenerator.js:29
Promise.then (async)
n @ asyncToGenerator.js:13
s @ asyncToGenerator.js:25
(anonymous) @ asyncToGenerator.js:32
(anonymous) @ asyncToGenerator.js:21
t @ utils.js:490
(anonymous) @ Upload.vue:817
l @ runtime.js:45
(anonymous) @ runtime.js:274
(anonymous) @ runtime.js:97
l @ runtime.js:45
A @ runtime.js:337
(anonymous) @ runtime.js:248
(anonymous) @ runtime.js:97
l @ runtime.js:45
A @ runtime.js:337
(anonymous) @ runtime.js:248
(anonymous) @ runtime.js:97
n @ asyncToGenerator.js:3
s @ asyncToGenerator.js:25
Upload.vue:836 Error: Request failed with status code 404
    at createError.js:16
    at settle.js:17
    at XMLHttpRequest.f.onreadystatechange (xhr.js:62)
(anonymous) @ Upload.vue:836
l @ runtime.js:45
(anonymous) @ runtime.js:274
(anonymous) @ runtime.js:97
n @ asyncToGenerator.js:3
c @ asyncToGenerator.js:29
Promise.then (async)
n @ asyncToGenerator.js:13
s @ asyncToGenerator.js:25
A bad HTTP response code (404) was received when fetching the script.

[oeway]

https://sandbox.zenodo.org/api/files/8228b025-d5ac-4aa6-9501-57d082129f28/sample-6/data.smlm

It seems the 404 error comes from the zenodo server, could you elaborate when does this happen? I tried it but never get this error. This is a different error compared to the 403 error you reported earlier.

Could you try the same with the production server?

[baiddd]

For the SANDBOX version
When I logged in: the first try stocked at this page again, so this message popped up:

The second one went smoothly.
Then I entered 7 samples in which we have 1/2 channels: smlm/smlm with widefield
I clicked on the upload button, the error appears

Sometimes it appears when the uploading is almost finished, as I mentioned

I try the production mode now.

[baiddd]

For production version,
when I click on Upload as new deposit a new error

Error: Failed to create deposition, error: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>403 Forbidden</title>
<h1>Forbidden</h1>
<p>To create a deposit please verify your email. You can resend the verification email from your profile settings.</p>

Something wrong with my account, I will try later when I fixed the pb
@oeway

[oeway]

Sometimes it appears when the uploading is almost finished, as I mentioned

I believe that there are two types of issue here. Basically, the 401 error should not appear any more, did you take new screenshots or it's the same one as your first post? The 404 error is new, but it looks like the zenodo server has some issue, it might not appear in production server.

[oeway]

To create a deposit please verify your email. You can resend the verification email from your profile settings

You need to verify your email. Where did you see this message? Could you take a screenshot, and add that to the login instruction?

[baiddd]

Sometimes it appears when the uploading is almost finished, as I mentioned

I believe that there are two types of issue here. Basically, the 401 error should not appear any more, did you take new screenshots or it's the same one as your first post? The 404 error is new, but it looks like the zenodo server has some issue, it might not appear in production server.

It was a different screenshot, I tried again still the same error 401 now even with production version

[baiddd]

To create a deposit please verify your email. You can resend the verification email from your profile settings

You need to verify your email. Where did you see this message? Could you take a screenshot, and add that to the login instruction?

when I see again the error I will take the screenshot, strangely my email was correctly related to my Znodo account before

[oeway]

To create a deposit please verify your email. You can resend the verification email from your profile settings

You need to verify your email. Where did you see this message? Could you take a screenshot, and add that to the login instruction?

when I see again the error I will take the screenshot, strangely my email was correctly related to my Znodo account before

Note that the production server is independent from the sandbox server, e.g. they don't share user accounts.