azure-batch-maya

azure-batch-maya copied to clipboard

Attempted to install v17 on 3 different computers, however each computer becomes stuck in a "Need to install azure-batch-extensions==1.0.1" loop. Deleting the whole My Documents\maya folder does not remedy the issue.

Are there any hidden (Appdata~) folders that need to be cleared in these cases?

Is the mayapy install progress logged anywhere for reference?

The only way I could solve this was by manually running mayapy with the commands but altered to be:

mayapy C:\Users\trevor\Documents\maya\2017\scripts\azure-batch-libs\pip install azure-batch-extensions==1.0.1 --target C:\Users\trevor\Documents\maya\2017\scripts\azure-batch-libs\temp-target --ignore-installed

I then copied the files over to the main directory (although I could probably just have installed them directly into the parent azure-batch-libs from the start). Something seems to be a little strange with the way the following is working, at least on my 3 systems that I tested it: https://github.com/Azure/azure-batch-maya/blame/master/azure_batch_maya/plug-in/AzureBatch.py#L372

It did not work in the end, it installed "successfully" (no more dependency loop) but now it just throws an error upon loading the shelf

ImportError: file C:\Users\trevor\Documents\maya\2017\scripts\azure-batch-libs\entrypoints.py line 19: No module named backports

backports is present in the parent lib directory though

I am also having the same problem, please someone help me fix this problem.

Hi Trevor, I have forwarded your query off to a colleague who will take a look in the morning.

Thanks, Andrew

Thanks Andrew!

@davidkydd I saw an email that you had commented but couldn't reproduce the issue.

Here's what happens on all 3 PCs that I try it on.

https://youtu.be/PiaB08iK79k

Thanks Trevor yes after posting that comment I was able to repro this issue so deleted the comment :-)

No update yet but are continuing to investigate - your comment on yammer that even previous builds of the plugin are now exhibiting the same behaviour is a good tip off that something has changed "under our feet", and the fault is with one of the plugin dependencies or our usage of them.

Also just a minor update on investigation progress thus far - it appears that the azure-batch-extensions dependency now requires msrestazure==0.4.14 or later, and the plugin is configured to fetch only msrestazure==0.4.11.

Changing the msrestazure version in AzureBatch.py to 0.4.14 breaks the "Need to install azure-batch-extensions==1.0.1" loop, and reveals the backports import error on shelf loading as described by psyrus above.

This is fixed in c19a09b and in release v0.18.0 - cause was that azure-batch-extensions==1.0.1 changed at some point to require msrestazure==0.4.14 instead of 0.4.11. This required the install of the new dependency backports.configparser