Uploading a new extension causes 500 error #125

New Issue

Isamu Mogi · 2024-05-11T19:30:16+02:00

Isamu Mogi commented

2024-05-11 19:30:16 +02:00

I'm getting an internal server error (500) when trying to upload a new extension. The extension upload I did in March was successful.

Please refer to the attached video for network communication logs, etc.

Windows 11 Pro 22H2 22621.3527
Microsoft Edge 124.0.2478.97 (公式ビルド) (64 ビット)

I'm getting an internal server error (500) when trying to upload [a new extension](/attachments/685acca8-3d09-464b-8dfc-266889924b56). The extension upload [I did in March](https://extensions.blender.org/approval-queue/vrm-extension/) was successful. Please refer to the attached video for network communication logs, etc. <video src="/attachments/1db70914-b457-4b8f-872f-c76dc5be59df" title="new-extension.mp4" controls width="600"> Windows 11 Pro 22H2 22621.3527 Microsoft Edge 124.0.2478.97 (公式ビルド) (64 ビット)

new-extension.mp4

1.2 MiB

vrm_20240511133734_b0aedc74ae4b23e69756106ded4e60195265c57a.zip

1019 KiB

Isamu Mogi commented

2024-05-11 21:06:53 +02:00

This error seems to occur when there are duplicate extension names.

I have uploaded an extension with the id vrm_extension, but I want to change it to vrm. I tried to upload an extension with the same name but only the id changed.

This error seems to occur when there are duplicate extension names. I have uploaded an extension with the id `vrm_extension`, but I want to change it to `vrm`. I tried to upload an extension with the same name but only the id changed.

Oleg-Komarov self-assigned this 2024-05-13 10:26:58 +02:00

Oleg-Komarov commented

2024-05-13 10:31:35 +02:00

Yes, we have two integrity checks in the models that unfortunately were not covered by pre-validation: name uniqueness and file content uniqueness (for zips and for images).
I will fix the form to make sure that we display a proper error message.

Yes, we have two integrity checks in the models that unfortunately were not covered by pre-validation: name uniqueness and file content uniqueness (for zips and for images). I will fix the form to make sure that we display a proper error message.

👍 1

Oleg-Komarov referenced this issue from a commit

2024-05-13 11:31:32 +02:00

Validation: check extension name uniqueness (#125)

Oleg-Komarov commented

2024-05-13 13:05:45 +02:00

File uniqueness was already addressed in 47a0baf8b2, but hasn't been deployed yet.

File uniqueness was already addressed in 47a0baf8b26df6907093fc2bfcfa8cd6b09f1495, but hasn't been deployed yet.

Oleg-Komarov commented

2024-05-13 13:12:16 +02:00

Thank you for the report!
All fixes have been deployed in production.

Thank you for the report! All fixes have been deployed in production.