-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some PCs are having problems updating addon #90
Comments
Sorry for the late reply here. It's hard to debug path based issues, as it depends a lot on the structure of the source addon and the repo itself. Can you gather any insights over why it was happening with some pc's? When those updates were attempted, do you know what version of your own addon they were updating to and from? Was there any restructure (folder pivot) at some time with the plugin? I'll admit I haven't run into any pathing issues with plugins I manage using this framework, but that doesn't mean there isn't some edge case out there.
There shouldn't be realistically, but I will say I notice some double pathing in the folder structure (e.g. seeing |
Hi @TheDuckCow, I've just recently upgraded my build scripts and I've seen this bug for BlenderKit add-on (there are few prints added for debug purposes):
So I have investigated the zip files and found that I've somehow managed to create it without explicit directory entries:
This then leads to situation when update fails, because it tries to write the file into a directory which does not exist. Maybe updater could just check if the parent directory exists before opening the file for write instead of relying on existence of directory entry and the pathsep?
|
We have updated to github action https://github.com/actions/upload-artifact v3 -> v4. That could be the reason. Not sure, but maybe it could help somebody, until this issue is fixed. For now I am gonna stick to manual zip creation as the v4 does not offer possibility to insert explicit directory entries. |
A question for you @agajdosi - if you download that zip being downloaded by the updater manually, does it work as-is to install into blender manually? Blender addons pretty strictly require that, otherwise you end up creating a mess in the addons folder (presuming these addon builds are also made available for download elsewhere). I find it odd that upload-artifact would make a difference, unless is that action itself doing the work on constructing a zip file? |
Oh and I should clarify, is the snippet you provided a workaround that makes it functional as-is for you? If so, I can analyze it a bit further and see if I'm happy enough to take that as a contribution (you could also create a PR and tag me as a reviewer, the important thing is to verify it is at least working for you, I can then cross verify if working in other addon repo setups) |
Hi @TheDuckCow, I would be totally happy to make the PR.
I am relying on the artifact-upload action to create the .zip file (as I am not aware of a way how this action could upload zip created by me and not encapsulate it into another zip). So the problem starts there. But...
... I am able to install that .zip into Blender manually just fine. Actually I have sent these zips to many users and they all reported it fixed their issue. I only found the problem recently when I have released the zip and people started auto-updating. For now the fix was to release the zip created manually. But I believe auto-updater should handle this form of zip. Because the directory entry in the zip is redundant, information about the directory is present in the files which specify it: |
Ok great, I'd be happy to swiftly review any PR you put together to make sure there's no unintended regressions. I agree that it shouldn't be a requirement to create a manual build, so this is a fix worth making indeed. |
Hi,
We are getting an error which we can't reproduce as it only occurs in some pcs. When updating after detecting a new version of our asson some pcs throw the following error:
FileNotFoundError: [Errno 2] No such file or directory: 'C:\\Users\\FerranMMC\\AppData\\Roaming\\Blender Foundation\\Blender\\4.0\\scripts\\addons\\blender_venue_editor\\blender_venue_editor_updater\\source\\addon_updater_dir/blender_venue_editor.addon_updater_dir_updater/blender_venue_editor.addon_updater_dir_updater_status.json'
Is there any condition inside the updater which changes where the status.jason is stored???
The text was updated successfully, but these errors were encountered: