Nok Lam Chan

@ElenaKhaustova Can you point to the changes that you have made? I wonder if there is anything we can report upstream and create an example that strip away the kedro...

> cannot set WRITEABLE flag to True of this array Google: https://www.google.com/search?q=cannot+set+writeable+flag+to+true+of+this+array&oq=cannot+set+WRITEABLE+flag+to+True+of+this+array&gs_lcrp=EgZjaHJvbWUqDAgAECMYJxiABBiKBTIMCAAQIxgnGIAEGIoFMggIARAAGBYYHjINCAIQABiGAxiABBiKBTINCAMQABiGAxiABBiKBdIBBzI4MmowajeoAgCwAgA&sourceid=chrome&ie=UTF-8 Searching this bug there's tons of report everywhere, some are libraries compatibility issue. Is this a `scikit-learn` problem?...

Oh sorry I didn't notice that was the change. This remind me of something. If you check `MemoryDataset`. ``` if copy_mode == "deepcopy": copied_data = copy.deepcopy(data) elif copy_mode == "copy":...

Capture some relevant discussion in Slack. PR are welcome since I think this should be a straightforward fix without introducing more complicated tree structure. On a side note, kedro-viz probably...

@amitpoorab feel free to make a draft PR

We need to clarify this case: - `a` - `a.b` - `a.c` If one choosing namespace = a, should a.b, and a.c be filtered? Changing from `.startswith` to exact string...

@datajoely is correct that it's more like AND, there are more use cases that are only possible with Pipeline API but not CLI, [this is one of the example](https://noklam.github.io/blog/posts/kedro-pipeline-slicing-pipeline/2024-03-06-Kedro-Pipeline-Slicing-Pipeline.html#advance-pipeline-slicing). On...

@lordsoffallen I think I understand where is this coming from. I am not sure if this is clearly better. ``` node(myfunc, input='data1', output='out1', name='myfunc', namespace='a') node(myfunc, input='data2', output='out2', name='other_function', namespace='b')...

@lordsoffallen would you mind pointing me to some k8s resource that related to this? I am not very familiar with it. I do think conceptually they are different things, the...

One question here, we tend to do the breaking change later in `develop` to avoid the code diverge too much. At the same time should we add the `deprecated` warnings...