Built-in Hub browser package updates downloads corrupted VARs

[atani]

This is different from downloading the wrong version issue, but could be related:

Wrong version dependencies are being downloaded fom the dependencies section of each release pressing download button

I do not want to create double posts so i will link the issue i posted here because i was pleased to inform here too. Dependencies DL is broken using the sites dependencies dl function...

hub.virtamate.com

In this issue the downloaded file of a update is corrupted.

The error above comes 15 minutes before this post, the downloaded file was around 35 KB in size when it should be much larger. This is by using the built-in Hub Browser updating existing VARs.
I've only noticed this for the past day or two.

Thanks

 

[AshAuryn]

This is different from downloading the wrong version issue, but could be related:

Wrong version dependencies are being downloaded fom the dependencies section of each release pressing download button

I do not want to create double posts so i will link the issue i posted here because i was pleased to inform here too. Dependencies DL is broken using the sites dependencies dl function...

hub.virtamate.com

In this issue the downloaded file of a update is corrupted.

View attachment 305378
The error above comes 15 minutes before this post, the downloaded file was around 35 KB in size when it should be much larger. This is by using the built-in Hub Browser updating existing VARs.
I've only noticed this for the past day or two.

Thanks

Looks like this file is not downloadable, as it and all its versions are hosted on Mega.

 

[atani]

The issue is that it showed in the updates, which wouldn't be possible as:

• it's externally hosted
• the file hosted in Mega is a zip file
• there's no v2

Upon closer inspection, it appears to be coming from the Discussion area where @bill_prime shares a v2 version.
The updates section in the built-in Hub shows a 364 KB update, that matches Bill's VAR size, but the download is of 37 KB, giving that error as the file is incomplete. There seems to be some polluting if sharing a VAR in the discussion area.

Very likely a freak case, it's not typical to share VARs like this, but worthwhile checking if that can be sanitized.
Thanks.

 

[AshAuryn]

The issue is that it showed in the updates, which wouldn't be possible as:

• it's externally hosted
• the file hosted in Mega is a zip file
• there's no v2

Upon closer inspection, it appears to be coming from the Discussion area where @bill_prime shares a v2 version.
The updates section in the built-in Hub shows a 364 KB update, that matches Bill's VAR size, but the download is of 37 KB, giving that error as the file is incomplete. There seems to be some polluting if sharing a VAR in the discussion area.

Very likely a freak case, it's not typical to share VARs like this, but worthwhile checking if that can be sanitized.
Thanks.

Thanks for that info. I will see if I can figure out what might have occurred.

 

[AshAuryn]

We've removed the file and let @bill_prime know it could be uploaded as a .zip safely. We've also disabled attaching .var files anywhere but the resource add/edit/update form.

 

[atani]

It's a edge case this one but could cause confusion if it happened in a very popular resource.
Thank you

 

[AshAuryn]

This issue should now be fixed for most resources.

The issue has to do with resources that are no longer viewable, and result in a 404 if you try to visit the resource page. This is most often because the resource has been deleted, or unpublished. We have updated the Hub to return a different download link in-game if a resource has been unpublished or removed. We did not alter the behavior that saves the 404 page as a var, because this would require an update to VaM itself, but the issue should be solved for most resources.

If you encounter the issue in the future with a particular resource, let us know and we will see if we can fix the resource itself so that it becomes available (or delete it properly if it is not supposed to be available).

 

[AshAuryn]

Normally our turn around time on something like this would be a bit quicker, but it took some time to reproduce the error consistently and nail down the cause. Thank you for your patience.