Flamenco Worker - Update WRN msg when Blender isn't found by Worker to help end user on next-steps #104230

MichaelC · 2023-07-05T17:43:49+02:00

MichaelC commented

2023-07-05 17:43:49 +02:00

Problem

End users tend to get stuck on the "WRN" and try to either re-install Blender or configure Flamenco Manager blender paths.

Enhancement to message is to still warn on this situation and help point the end user to some configuration documentation explaining how Flamenco Manager can pass the Blender path whenever a Task in a render Job is dispatched to the Worker.

Probably worth trying to add some more info or FAQ documentation on why Blender couldn't be found in another PR.

Problem End users tend to get stuck on the "WRN" and try to either re-install Blender or configure Flamenco Manager blender paths. Enhancement to message is to still warn on this situation and help point the end user to some configuration documentation explaining how Flamenco Manager can pass the Blender path whenever a Task in a render Job is dispatched to the Worker. Probably worth trying to add some more info or FAQ documentation on why Blender couldn't be found in another PR.

MichaelC added 1 commit 2023-07-05 17:43:50 +02:00

point users to config help if worker cannot find blender exec 4cb9ee4523

Sybren A. Stüvel requested changes 2023-07-06 12:51:06 +02:00

Sybren A. Stüvel left a comment

For reference: this PR has the same goal as #104224, and the discussions on that PR are also valid here.

cmd/flamenco-worker/find_exes.go Outdated

						
				@ -36,2 +38,3 @@

					case errors.Is(err, fs.ErrNotExist), errors.Is(err, exec.ErrNotFound):

						log.Warn().Msg("Blender could not be found, Flamenco Manager will have to supply a full path")

						log.Warn().Msg("The Worker could not find Blender on this system. " + helpMsg)