I am utterly sorry if this was the wrong place, I didnt see it as a feature request.
My bad! Thank you for doing what you do!

That's indeed a limitation. We don't use this tracker to handle such feature or improvement requests though:
https://wiki.blender.org/wiki/Contact#Requesting_Features

Agree it could skip writing if the Composite node is removed (or has nothing linked), and that making it do that would be a To Do.

Agree this is a little weak.
It is not a bug though, it is still working as intended.
Not having a Compositing output Node used to complain and refuse to render, but that rule was softened in the fix for T35269.

Working around it would be easier if the dilate/erode node had an input for step value.

I guess this is known limitation of the compositor (but I am not sure).
Workaround is (as you said) to first do the erosion first, then the scaling.

Rebased on the latest master.

Tried undoing some changes done in snode_set_context() but no success so far. @Lukas Stockner (lukasstockner97) this falls on your desk am afraid. ;)

Bisecting points to rB4cf7fc3b3a4d032f0c0db632a46d40806e906cf1 as breaking commit. Not sure what went wrong there, that is rather large commit :/

Confirmed, would guess something went wrong in the update notifiers…

Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

@Sergey Sharybin (sergey), I guess that one is for you? ;)

It does work when you are using the Defocus Node, using the Z-Buffer of the current scene. Could be that this is the only node that does actually trigger a render update, but then the Auto Render button would be quite misleading indeed.

It’s not saved because there is no data at all (as can be checked with a viewer node), for both volume passes, when Save Buffer is enabled. @Brecht Van Lommel (brecht), guess that one is for you?

Thank you! As usual I can help with testing.
If new color management will not get into 2.8, this will surely make it more flexible.

Thanks for the report, but this is a known limitation. One day we would need to implement more proper color management and such for file output (including manual saving from the editor, render output, nodes...). For until then considering it a TODO.

Sounds more like a TODO and/or known limitation, @Sergey Sharybin (sergey)? Also, do not see anything specific to 2.8, afaik 2.7 does not have that option either.

This is interesting, for sure. I'm not sure that in a typical compositing workflow if it would be extremely useful, but from the examples posted, it certainly looks like you can do some very artsy, creative stuff with it.

Thanks guys :)

This is indeed a feature request, that is planned to be solved in the future with overrides in 2.8. The other thing is that we should add support for a world position pass at some point.

Well, this is like trying to simulate data pass with a light setup, which is already kind of weird. So probably this is something to look at as well.

@Brecht Van Lommel (brecht) @Sergey Sharybin (sergey) while much more like a feature request than a bug, think that totally make sense… Maybe change the task to TODO type?

Hi @Brecht Van Lommel (brecht), I know you have a lot to do, but could this feature someday included in Blender? (Only asking)

Hi @Brecht Van Lommel (brecht), I know you have a lot to do, but could this feature someday included in Blender? (Only asking)

Updated the patch

Updated patch with comments from @Brecht Van Lommel (brecht)'s review

Looks generally fine. For release notes / documentation I guess this can be summarised as:

Yeah, there is some blurring at the default values.
Assume that the image is recalculated (always) which leads to blurring.

The fact that is has zero alpha outside the object is correct, it's intended to add glow without obscuring anything behind.

The problem lies elsewhere.

The compositor actually works fine, but the image editor is not displaying it correctly, see T52680.

It might have something to do with it. This was pretty much the closest workaround solution I came up with, even then there's still some compromise. Is it a compositor/viewport problem or is this just normal for some effects in Blender? Sorry, I'm still fairly new to Blender.