Hi,
After updating to the last version of LBT with the versioner, GH is failing to load LBT.
The following image shows the image I get. It is related to access denied to Dragonfly_grasshopper.
I installed again LBT with the one-click installer, and it works fine. Then I updated via versioner resulting in the same error.
Makes me wonder that recent updates in DF is causing this error. Can be?
Thanks,
-A.
Hi,
Just in case this one fell between the cracks …
It happened again today after installing LBT with the installer and then updating with the Versioner.
Thanks,
-A.
Thanks, @AbrahamYezioro ,
This is not a new issue and I doubt there is anything that we changed in Ladybug Tools recently that has triggered this for you. You can see that @charlie.brooker reported this same issue on the pollination forum over 3 years ago:
It only affected his work computer at the time but maybe Windows is changing it’s default security settings such that a lot more people are able to experience the issue now.
In the past, we weren’t really able to figure out what triggered it on his end. I still cannot recreate the issue on my own machine but @mikkel just told me that he was able to recreate it. I am pretty sure that, if I can recreate it, we’ll find some way to fix it or at least work around it.
Ah, I was just able to recreate it!
Did you also get the following strange warning when you tried to use the Versioner?
If so, I think that gives me a big hint about where things went wrong.
Ok, I have an initial, very manual workaround, which I am hoping to replace with something better but the workaround does enable you to get the latest development version of the plugin and I think it’s faster to perform than reinstalling the whole plugin.
The workaround is to go to the following folder:
C:\Program Files\ladybug_tools\grasshopper
Double-click on each of the 8 sub-folders and click “Continue”:
Then, go to this folder:
C:\Program Files\ladybug_tools\resources\standards
Double-click on honeybee_energy_standards and click “Continue”.
After that, you will have a fully functioning development version of the LBT plugin the next time that you open Rhino.
I am going to try my best to figure out how to integrate this manual process into the routine run by the LB Versioner. I’ll post back here if I manage to implement something.
I have an official fix ready to go here:
I have to admit that I don’t really know why this fixes it since it really feels like I am working around a problem that Python’s pip installer should have addressed natively. But I understand how my fix is working and verified that it gets the Versioner routine to succeed without the need to manually restore permissions to each file.
I am going to try and get this change into a release of the pollination single-click installers so that no one needs to do the manual workaround I listed above.
But, if you go through the process of using the LB Versioner now, you should only need to do the manual workaround once. After that, all subsequent runs of the LB Versioner should succeed.
We just pushed updated Pollination single-click installers with the fix. If you download and run those installers, you should no longer have any issues running the LB Versioner.
Let me know if you test it. Really glad that we finally got a solution for this after @charlie.brooker first reported it years ago.