Skip to content

#!connect stdio doesn't expose all the kernels when connecting to another composite kernel #2546

@colombod

Description

@colombod

when in vscode I do

#!connect stdio --name new-interactive [path to another dotnet interactive]

I don't get the opportunity to connect proxies to the child kernels of the composite kernel I just connected to

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions