Resolved in e2d9166473184

I tried last night with a render. I started Flamenco Manager using cmd.exe and with the - verbose command.
The manager didn't crash and worked perfectly all night long.

I've tried running Flamenco Manager on Windows 10 for close to 7 hours, and it keeps running just fine. It has one Worker connected to it, so it does get frequent polls for more tasks.

Can you start Flamenco Manager from a cmd.exe terminal? That way it stays open and you can read any error message. Start it with flamenco-manager.exe -verbose to get more verbose logging. If it turns out that that still doesn't give enough information we can use flamenco-manager.exe -debug to enable debug logging, but this will produce a rather copious amount of log messages.

Nice analysis, thanks.

Adding the script to my blender variable in flamenco-manager.yaml works for me.

no problem thanks!

Hi Kael - same here unfortunately. I'm definitely interested in looking into this, but it might take some time. I'll keep you posted!

Hey @Francesco Siddi (fsiddi) , I ended up becoming busy myself with another project as well, but am freed up now and am looking into this again.

Hello Kael, unfortunately I'm very busy with other projects at the moment. I'll come back to this conversation later next week.

The create new manager and revoke existing token endpoints are easy to fix.

This looks as easy as grabbing the session from flask and then taking the user_id from that session and validating based on that user id.

Issue was solving by tweaking indexes (over 1 year ago).

Fixed in 033bac4552b153894c936ab81307b42b4ec134e1.

@joel heethaar (joel_nl) I've added Brecht's script to Flamenco Worker, to the T53099-gpu-rendering branch, but I haven't created anything around that yet. Can you test that the script works by adding --enable-autoexec --python "/path/to/flamenco-worker/flamenco_worker/enable_all_gpus.py" to the blender variable in your flamenco-manager.yaml?

Something like this should work:

We are urgently need this feature

Done in f383764a274fe62f17c0d5e309cc5e97693c6178

Already resolved a while ago.

We'll probably have to re-think this once we take Blender Cloud out of Pillar. Since the macro now has too many things that are only relevant to the Cloud, such as Subscription and My Projects.

Tested after closing all subtasks and it looks good. Used the description of this task as a draft for docs about the permissions system in 5a429d29e1da9a3f00cabe94071a7b5c8ae392b6.
Thanks @Sybren A. Stüvel (sybren) !

Now we hide some parts of the interface is the right role is not available. See ce71ca7a99053723b3795c9a5941f93c54e48671.

Clicked through and browsed most of Flamenco with different role combinations (no role, subscriber, flamenco-admin, flamenco-user). Everything works as expected.

This is part of the documentation project, still work in progress.

PS: I implemented option 2 (see description above).

• Server: 2e55892272a224d5ecae3193faba8b337b2b5ba8
• Manager: e48261c252554db0fdb51a4961126e03b05e3d2b
• Blender Cloud add-on: a51f61d9b5dac066b0a54ea9c985b2dbc1446334