Ian Carroll

> Do you have any errors when building jupyterlab? No errors. I can confirm with an added console log in packages/markedparser-extension/src/index.ts#initializeMarked that three plugins are loaded. If there is a...

@bent10 Thank you for the marked-alert extension. I am interested in the feasibility of integrating it into JupyterLab. I'm not a javascript developer, but this seemed like it should have...

> does GitLab support it? Yes - Documented at https://docs.gitlab.com/user/markdown/#alerts, with a possibly useful discussion at https://gitlab.com/gitlab-org/gitlab/-/issues/24482. > is there a consistent implementation across platforms? (It sounds like not?) GitLab...

If you want to be fancy, you could return the same type given to you in the `local_path` argument.

Despite getting immediately stuck on #18096, I want to learn how to contribute to jupyterlab. I see @MMesch added this to a project; let me know if I could help....

Thanks for the update. I want to note this is relevant to #565.

I [can get custom cache arguments](https://github.com/itcarroll/repo2docker-action/blob/cc5bad9abae7c3ff4ee6cdcfdbcecc9a53d40d0f/create_docker_image.sh#L127-L128) to the build using `--DockerEngine.extra_buildx_build_args`, but run into the following error from the default docker driver. This is why actions/docker-setup-buildx is called before actions/build-and-push-docker-images...

I'm failing to get the containerd image store enabled. I've included the [documented configuration file](https://docs.docker.com/engine/storage/containerd/#enable-containerd-image-store-on-docker-engine) in the `repo2docker-action` Dockerfile. But this is docker-in-docker and I suspect that configuration is meaningless.

I'm very happy to see this project-specific kernel suggestion! I created a similar feature request (jupyterlab/jupyterlab#16359) hoping to leverage JupyterLab [workspaces](https://jupyterlab.readthedocs.io/en/latest/user/workspaces.html). Some advantages to linking a kernel spec to a...

I see a lot of potential for taking this moment to actually broaden and strengthen the community, which any user disruption would work against. Thoughts in that line from this...