Resetting and re-executing resolved it but I still wonder if a real issue in the data was triggered. Here is the code:
import knime.scripting.io as knio
import pandas as pd
import html
# Load the input table
df = knio.input_tables[0].to_pandas()
# Apply HTML escaping to the "ColumnValues" column, handling NaN values
df["ColumnValues"] = df["ColumnValues"].apply(lambda x: html.escape(str(x)) if pd.notnull(x) else x)
# Output the modified table
knio.output_tables[0] = knio.Table.from_pandas(df)
@mwiegand I have seen this sometimes after a green Python node ‘sits’ there for some time with its result and then it shows this error, without this being an actual error (maybe). It looks as if the connection to the stored results gets ‘lost’ or something.
@mlauber71 yes, I agree. This falls into the bucket of hard to trace problems we keep a record of. Though, it still causes concerns as no one can actually tell if there is a problem or not.
It is almost as if the node is in a quantum state of superposition
I also just experience another odd behavior where that very same node got triggered to execute but was kind of hanging not starting to crunch the data. No error … just “superposition” oof awkwardness.
PS: I start to believe there is a more fundamental issue as I encountered something similar before but with the Component Output. Just right now I got this “experience”.
