No longer able to remove file output input sockets from python. #102611

New Issue

michael campbell · 2022-11-18T20:47:38+01:00

michael campbell commented

2022-11-18 20:47:38 +01:00

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94

Blender Version
Broken: version: 3.5.0 Alpha, branch: master, commit date: 2022-11-17 22:27, hash: 2c096f17a6
Worked: (3.5 alpha from a couple of days ago (I'm not sure which one as I've deleted the zip)

Short description of error

I have an addon in use by around a thousand paying customers, and all of a sudden over the last day or so, it's been reported that the addon has ceased to work due to a sudden inability to remove file output node sockets. This is a necessity in order for the resulting multilayer EXR to adhere to the correct naming conventions.

I'm a financial supporter of blender, both as a percentage of addon sales and the development fun. Is there any chance this could be fixed quickly to save me a ton of complaints/refund requests? The addon is my only source of income.

Reproduction steps:

turn on use nodes in the compositor, then run this script:

import bpy
scene = bpy.context.scene
file_output_node =scene.node_tree.nodes.new("CompositorNodeOutputFile")
file_output_node.file_slots.remove(file_output_node.inputs[0])

Results in RuntimeError: Error: Unable to remove socket from built-in node.

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94 **Blender Version** Broken: version: 3.5.0 Alpha, branch: master, commit date: 2022-11-17 22:27, hash: `2c096f17a6` Worked: (3.5 alpha from a couple of days ago (I'm not sure which one as I've deleted the zip) **Short description of error** I have an addon in use by around a thousand paying customers, and all of a sudden over the last day or so, it's been reported that the addon has ceased to work due to a sudden inability to remove file output node sockets. This is a necessity in order for the resulting multilayer EXR to adhere to the correct naming conventions. I'm a financial supporter of blender, both as a percentage of addon sales and the development fun. Is there any chance this could be fixed quickly to save me a ton of complaints/refund requests? The addon is my only source of income. Reproduction steps: turn on use nodes in the compositor, then run this script: ``` import bpy scene = bpy.context.scene file_output_node =scene.node_tree.nodes.new("CompositorNodeOutputFile") file_output_node.file_slots.remove(file_output_node.inputs[0]) ``` Results in RuntimeError: Error: Unable to remove socket from built-in node.

michael campbell commented

2022-11-18 20:47:38 +01:00

Added subscriber: @3di

blender-admin commented

2022-11-18 21:01:40 +01:00

This issue was referenced by c4cfa1b23e

This issue was referenced by c4cfa1b23ee661a941e46c52e9fb8df1e43e74d4

blender-admin commented

2022-11-18 21:01:40 +01:00

This issue was referenced by c0f33814c1

This issue was referenced by c0f33814c13c38aa49b909ba2a8946798d14d078

Hans Goudey commented

2022-11-18 21:03:32 +01:00

Added subscriber: @HooglyBoogly

Hans Goudey commented

2022-11-18 21:03:32 +01:00

Changed status from 'Needs Triage' to: 'Confirmed'

Hans Goudey self-assigned this 2022-11-18 21:03:32 +01:00

Hans Goudey commented

2022-11-18 21:03:32 +01:00

Caused by 52bd198153.

I do wonder if there's a better API to make these changes that doesn't require changing the sockets of the node directly.

However, that doesn't matter at all now, because we shouldn't make such breaking changes for regular releases, especially with no warning or announcement, etc.

Caused by 52bd198153. I do wonder if there's a better API to make these changes that doesn't require changing the sockets of the node directly. However, that doesn't matter at all now, because we shouldn't make such breaking changes for regular releases, especially with no warning or announcement, etc.

Hans Goudey commented

2022-11-18 21:04:23 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Hans Goudey closed this issue

2022-11-18 21:04:23 +01:00

michael campbell commented

2022-11-18 21:05:47 +01:00

Thanks @HooglyBoogly , you're a legend! Phew!

michael campbell commented

2022-11-18 21:11:26 +01:00

I think Jacque must have just forgotten that the file output node requires the the sockets be editable in order for it to function. It's probably the only node other than a group node that needs that flexibility.

Jacques Lucke referenced this issue

2024-02-28 22:09:22 +01:00

WIP: Fix #103824: CompositorNodeOutputFile inputs.new() crash #118807

Philipp Oeser referenced this issue

2024-02-29 09:43:18 +01:00

WIP: Fix #103824: CompositorNodeOutputFile inputs.new() crash #118807

Sign in to join this conversation.