James Horsley

I've run into this as well. Digging in a bit, it's crashing here: https://github.com/nextcloud/desktop/blob/6e41875fe1eb486813fb715c83aeaf59f5367d5d/src/libsync/vfs/cfapi/cfapiwrapper.cpp#L630 Here's a bit more debug info:   I tried building nextcloudsync.dll with optimizations disabled /Od...

Oh? I didn't know about that. After having a quick look it seems as though mod capes are frowned upon but not banned. https://twitter.com/Dinnerbone/status/425037592200224768

hmm, the only other thing is that the whole eula thing was all about servers specifically and a mod like this has nothing to do with servers.

I think this is just a problem with the field names, because the fix relies on super hacky reflection stuff it is very hard to get it working. It doesn't...

Yes, I do mean that the files within the release_packages_path for that version are overwritten. In that simple example package.py I put above, the package.py and build.rxt files are overwritten....

Of course, it's just a nice to have really and I think it makes sense. Some packages you can't rez-cp, if they're set as not relocatable for instance!

I do indeed have `~/packages` first in my `packages_path` and it was using the local package definition (said as much in the context printout) although I've tried this again now...

So this would seem to be a much more difficult to catch bug than I originally thought, this package I have the problem with appears to have had the local...

So the plot thickens, these wrongly cached packages were not even cached by my user. A bit of background, we run a render farm where rez env is being run...

Yes, that does seem to be ok with that version. Although after resizing for a little bit memory usage (RAM+VRAM) steadily increases and it becomes more and more laggy/unresponsive until...