You can run Blender with --debug-cycles to see what it is doing, and also check that there is no Python error in executing that script.

Hi, having the same problem...

I currently have the script that @Brecht Van Lommel (brecht) wrote. Then using the command line on windows im running:

Hi, thanks for your patch.

Hi, thanks for your patch.

I'll close this as 'Archived' then; if you know of a way for us to reproduce the issue we can always reopen.

It is not 100% fixed, but I can confirm that I have certain .blend files with audio tracks in them that submit properly now in 2.81. I am not sure why some others don't submit to Flamenco, but there is the easy workaround of deleting the audio track before submitting the render or turning on "Relative paths only" in the Cloud plugin settings.

so u are saying it all works fine with 2.81? correct? that would means that we can close this as fixed/.

Unfortunately I won't have time to do this, but on a positive note I am unable to replicate this issue in Blender 2.81 with latest Blender Cloud plugin.

The package is golang.org/x/crypto (see the entry in go.mod), so go get -u golang.org/x/crypto + make would have been sufficient.

I suspect it has to do with the behaviour of Path.resolve() (doc). AFAIK on Windows it also "resolves" mapped drive letters to their \\SERVER\share\path\to\file notation, which is a pain in the rear end.

I have discovered that the error during the job submission can be prevented if "Relative paths only" is turned on in the Blender Cloud settings. I am not sure if that will introduce other issues, or if this is on by default, but it appears that it addresses the issue.

Error is still occurring for both 2.79 and 2.80, but only when a WAV file is in the video sequencer and I try to submit to Flamenco. The .blend files don't submit and get an error as below, with the display in the Flamenco Render tab reading "Found asset Narration-Audio.wav" when it stops packing. All files submit properly once the audio track has been removed, which is an acceptable workaround for me.

@Joel Howe (jhowe) can you try with this BAT wheel file? Just remove any exist blender_asset_tracer*.whl file from the wheels directory of the Blender Cloud add-on, then put this one in place and restart Blender.

D:/ is a local physical data drive on my main Win 10 workstation.
R:/ is the Flamenco project.
R:/ is a network mapped folder location to D:/Flamenco, so in the case of submitting the job, R:/ points to the same hard drive. R:/ was created using Windows "Map network drive", which I don't believe allows you to specify a protocol.
All Flamenco workers have an R:/ mapped back to my workstation, which is also running Flamenco manager.
Inside R:/ are three folders:

In T65726#699782, @Sybren A. Stüvel (sybren) wrote:

It would also help to know the layout of your files. What directory is set as the project directory? You're using drive R:, is that a network drive (if so, which protocol?) or a local disk?

I have been able to successfully submit to Flamenco a version of the file that has the object with an Ocean modifier, but only when the Cache path for that modifier was empty.

Adding a sound file to the sequencer in an empty .blend file was enough to reproduce the error for me, but I am attaching this actual file. This file has the proprietary elements removed, including the WAV file in the sequencer. To get this to submit to Flamenco without error, I have to delete the WAV audio and both the Alembic fluid surface and the Ocean modifier fluid surface.

Please give us files we can use to reproduce the issue. The blend file you uploaded packs just fine, albeit with warnings about missing files.