Another user reported this issue (on Discord) when trying to upload only 1 recording to Commons (he simply couldn't).

@Poslovitch said on Discord (translated from French) :
"With Lyokoï, we discovered a "new" "error message" during the uploading on LiLi. Apparently, it can happen that Commons says "I did not receive the file", while it actually did receive it. So, if you try to upload the file again, well, that won't work because Commons will refuse it, saying that the file is identical to a previously sent file.
So I will have to edit the RW interface to better handle this kind of errors.
In the meantine, the way to see why Commons refuses a file is to open the browser's console, which contains the errors."

Related task : [[T275957]]

Bonjour @WikiLucas00 ,

la console

In T281636#7097546, @WikiLucas00 wrote:

Related task : [[T275957]]

For me, it's not comparable: a few recordings that can be restarted or all the recordings that cannot be uploaded all.

But nobody except you and Michael have access to that db, is it fixed for good or will you have to regularly do that command for everybody else?

In T281636#7097541, @WikiLucas00 wrote:

@Poslovitch said on Discord (translated from French) :
"With Lyokoï, we discovered a "new" "error message" during the uploading on LiLi. Apparently, it can happen that Commons says "I did not receive the file", while it actually did receive it. So, if you try to upload the file again, well, that won't work because Commons will refuse it, saying that the file is identical to a previously sent file.
So I will have to edit the RW interface to better handle this kind of errors.
In the meantine, the way to see why Commons refuses a file is to open the browser's console, which contains the errors."

@WikiLucas00: please open a dedicated task, it seems to be different.

In T281636#7133556, @Poslovitch wrote:

But nobody except you and Michael have access to that db, is it fixed for good or will you have to regularly do that command for everybody else?

It is fixed permanently for Eihel. If other users have a similar issue, it should be asked to Michael to execute the SQL command. On the longer term, it could be created a frontend to allow admins to do this operation, but this issue is probably exceptional.

In T281636#7133573, @Seb35 wrote:

It is fixed permanently for Eihel. If other users have a similar issue, it should be asked to Michael to execute the SQL command. On the longer term, it could be created a frontend to allow admins to do this operation, but this issue is probably exceptional.

@Seb35 @VIGNERON @mickeybarber we might have a similar issue with User:Kunokuno, cf this post.

@Seb35 @VIGNERON @mickeybarber we might have a similar issue with User:Kunokuno, cf this post.

Done for Kuknokuno: I deleted the OAuth token + disconnected the user:

DELETE FROM oauthauth_user WHERE oaau_username = 'Kunokuno';
UPDATE user SET user_token = '' WHERE user_name = 'Kunokuno';

(as described on https://lingualibre.org/wiki/Help:Documentation_opérationelle_Mediawiki#OAuth)