►
From YouTube: JupyterLab Team Meeting - 14 June 2023
Description
A meeting to share and discuss features, ideas, issues, and pull requests in JupyterLab and other Jupyter frontends. This meeting is open to anyone and everyone.
Join future calls via the Jupyter community calendar: https://docs.jupyter.org/en/latest/community/content-community.html#jupyter-community-meetings
Notes for upcoming meetings can be found on the agenda: https://hackmd.io/Y7fBMQPSQ1C08SDGI-fwtg
Past notes can be found on the JupyterLab team compass: https://github.com/jupyterlab/team-compass/issues/170
A
Hey
hello
and
welcome
to
the
June
14
Jupiter
lab
weekly
meeting.
Let's
see
today
we
have
16
people
on
the
call
and
you
have
to
be
there.
We
all
just
introduced
ourselves-
well,
not
all
16
of
us
but
planning.
So
that's
incentive
for
me
to
come
if
you're
seeing
this
at
some
point
in
the
future
and
let's
see
if
you
would
like
to
talk
about
something,
please
add
your
name
to
the
agenda
and
we
will
get
started
right
away
so
Jason
W.
You
are
up
first.
B
Hey
good
day,
everyone
there
is
an
open
issue:
Jupiter
lab
issue,
14585,
it's
in
the
notes
and
I'll
drop
a
link
into
the
chat
as
well
came
from
a
colleague
of
mine
who
noticed
that
we
have
two
different
icons
in
Jupiter
lab
one
for
terminal
and
one
for
a
code
console.
But
the
code
console
icon
looks
very
much
like
the
terminal
icon
used
in
Mac
OS
and
some
popular
Linux
desktop
environments.
B
So
it's
a
bit
confusing
and
so
as
a
proposal
to
reply
to
change
the
icons
and
as
you
might
expect,
this
is
something
that
has
gone
back
and
forth
a
few
times.
People
have
opinions,
I'd
encourage
folks
who
are
interested
in
visual
designs,
because
this
is
probably
going
to
be
a
quite
noticeable
change.
Please
take
a
look
at
some
of
the
concepts
that
have
been
put
in
there
and
weigh
in
on
it.
We
should
probably
come
to
a
consensus
on
this
fairly
soon.
B
All
right,
if
not
I,
welcome
your
comments.
Is
there
a
strong
case
for
change.
Asks
Mike
I
personally
feel
like
the
the
terminal
icon
of
greater
than
underscore
is,
is
pretty
common,
and
so
it
might
help
new
users
to
be
more
comfortable.
The
idea
of
a
code
console
is,
as
far
as
I
can
tell
particular
to
Jupiter
lab
and
so
I,
like
the
idea
of
using
a
different
color
scheme
to
differentiate
the
two.
B
Even
if
we
use
a
very
similar
icon
using
a
different
color
might
be
good,
but
the
the
idea
of
like
putting
square
brackets
with
a
colon
afterwards,
it
might
be
specific,
yeah
and
Tony
points
out.
Color
only
is
insufficient
for
accessibility.
That
is
a
valid
concern,
as
well
also
for
things
like
printed
documentation
material.
If
you
use
a
black
and
white
printer,
you
don't
want
to
use
color
as
the
only
differentiator.
A
I
would
argue
that
the
code
consoles
not
unique.
It's
a
Jupiter,
it's
just
a
rapple,
it's
a
good
rebel,
it
has
visual
stuff
in
it,
but
it's
just
a
rebel,
and
so
maybe
there
is
prior
art
and
something
that's
analogous,
but
not
exactly
a
code
console.
If
we
look
to
see
what
kind
of
representations
of
rebels
we've
got,
yeah
I
mean
there.
B
Is
yeah?
There
is
a
comment
I'm
sorry.
There
is
a
comment
from
a
colleague
of
mine,
the
same
one
who
suggested
I
open
this.
That
points
out
that
Jupiter
cute
console
uses
an
icon
that
looks
more
like
the
prompt,
and
so
perhaps
we
could
use
a
simplified
version
of
the
cute
console
icon
for
it.
C
A
I,
don't
know
I
mean
we've
got
a
comment
in
the
chat
about
just
calling
it
a
ruffle
I'm
down
with
that,
but
I
would
be
because
I
said
the
word.
So
don't
take
it
too
seriously.
A
Yeah,
there's
a
question:
is
there
a
consistent
icon
system
that
could
reflect
stuff
made
of
cells?
I
mean
you
know,
you
see
like
a
little
table
icon
used
to
represent
spreadsheets
and
stuff,
but
no
I'm,
not.
B
Sure
yeah,
when
I
was
working
on
the
cell
toolbar
last
year.
This
was
a
common
concern
that
having
an
icon
that
represents
a
cell
is
surprisingly
difficult,
because
what
does
a
cell
look
like
other
than
a
really
skinny,
horizontal,
rectangle
and
so
cells?
Plural
could
look
like
a
series
of
horizontal
rectangles,
but
that's
arguably
too
simple
and
doesn't
really
convey
the
notion
of
cells,
so
it's
It's
Tricky,
but
a
code
console
is
not
necessarily
something
that
is
purely
related
to
cells.
It's
it's
yeah.
It's
a
rebel
element.
B
Well,
please:
let's
keep
the
conversation
going
in
14
585,
so
if
we,
if
we
can
come
to
a
consensus
on
something
that
we
believe
is
better,
then
we'll
try
to
move
forward
on
it.
Thanks
for
your
time,
cool.
B
There's
a
question
also
in
the
chat
from
Mr
grout
about
moving
tobias's
item
up
in
the
agenda.
So
if
make
sure
that
that's
oh.
B
Yeah,
so
that's
okay,
I'll
I'll,
cut
and
paste
it
beautiful.
Thank.
D
D
Awesome
yeah
I
appreciate
it
all
right,
yeah.
Thank
you,
so
I,
basically
just
wanted
to
use
also
this
meaning
to
reach
out
to
Mike
I
already
texted
you,
but
I
just
want
to
make
sure
that
we
are
currently
working
on
LS
python,
LSP
support
and
we
would
like
to
Upstream
all
that
work.
So
far,
I
haven't
seen
any
attempt
to
support
notebook
document
messages,
LSP
messages
in
any
package,
and
we
find
that
the
python
SP
server
package
is
I.
D
Think
a
very
good
starting
point
to
get
this
going
so
I've
already
opened
a
pull
request,
I'm
currently
working
on
it,
and
but
since
I
haven't
I
haven't
heard
from
you
or
I
forgot,
the
the
other
maintainer
of
the
package.
D
I
just
wanted
to
reach
out
again
asking
whether
we
can
have
like
a
quick
call
well
like
15
or
10
to
15
minutes
would
be
I
think
more
than
enough
to
get
things
going
either
way,
I'm
already
working
in
parallel
and
happy
just
to
also
contribute
more
to
the
package
and
probably
even
become
a
maintainer.
If,
if
that
is
if
that
is
possible,
yeah.
Thank
you.
E
Yeah
sure
sorry
I
haven't
had
time
to
look
into
your
pull
request.
Elia
I
I
will
be
working
on
LSP
staff.
This
coming
weeks.
I
will
mostly
voting
dlsp
extension
to
Jupiter
lab
4.,
but
I
will
make
sure
to
to
find
some
time
to
look
at
the
pull
request,
and
we
can
also
sync
outside
of
this
meeting,
to
look
how
to
make
this
progress.
The
I
don't
think
that
Carlos
would
be
currently
have
much
of
an
opinion
about
how
the
integration
should
proceed.
I,
I,
guess
that's.
E
What
we
should
do
is
just
try
it
out
with
an
editor
which
supports
that
and
maybe
see
whether
we
can
find
good
Suite
of
test
cases
or
other
ways
to
ensure
that
what
you
are
proposing,
the
request
would
work
and
then
we
can
patch
that,
as
once,
there
is
a
profile
of
concept
so
yeah.
We,
we
asked
I
believe
still
interested
in
having.
D
Perfect
yeah,
I
appreciate
and
any
form
of
communication
that
is
most
efficient
to
you
is
welcome,
so
you
can
choose
any
form
if
you
like
more
async,
that's
fine
to
me.
I've
made
experience
with
having
a
synchronous.
Conversation
gets
a
lot
of
things
out
of
the
way
very
quickly
so
but
yeah
I'll
leave
it
up
to
you.
Thank
you.
A
Great,
thank
you
so
Fred
I
think
is
now
here.
Is
that
correct.
A
So
he
asks
a
question
which
maybe
we
can
answer
for
him.
Should
we
create
a
branch
for
4.0.x
and
switch
the
main
branch
to
B
4.1
so
that
we
can
start
merging
feature
adding
PRS
any
volunteers
to
do
it?
Yeah.
C
A
F
We
take
a
look
at
at
how
many
issues
open
at
4.
X
Milestone.
This
is
just
something
I
asked
myself
hearing
this
question.
E
E
I
I
think
those
can
be
once
there
is
a
pull
requests,
then
those
can
be
back
ported,
so
I
I
think
we.
We
wouldn't
be
saying
that
we
are
focusing
on
4.1.
Now
it
would
be
saying
we
are
happy
to
merge
some
of
the
pull
requests
and
we
understand
that
this
might
make
back
porting
a
little
bit.
D
A
E
Yeah,
as
an
outer
of
four
of
these
pull
requests,
I
yeah,
I'm,
biased,
simply
oh.
A
A
A
C
A
And
I
can't
do
it:
I've
lost
it.
I
guess:
I
can
open
it
up
in
a
simple
thing:
yeah,
okay,
so
the
next
thing
Fred
had
was
a
couple
of
follow-ups
that
Jupiter
lab
four.
So
congratulations
Andrew
for
doing
release,
4.0.2.
A
The
demo
has
been
updated,
but
apparently
it's
missing
our
packages,
so
I
think
this
is
a
call
for
help
and
the
extension
examples.
Repo
has
been
updated
to
work
with
labs.
For
so
I,
don't
know
this.
Anyone
feel
like
they
can.
Maybe
look
at
the
stupid
live
demo.
Perhaps.
A
Okay
well
I,
for
now,
just
it's
on
the
edge
I
know.
At
least
people
will
see
it
and.
F
Thanks
so
I
want
to
tell
us
to
mention
that
so
yeah
I
I
did
the
release.
Please
ask
me
in
the
future:
if
you
need
to
do
a
release,
I
can
do
that
now.
So
yeah
and
the
point
that
I
wanted
to
discuss
is
the
point
that
Darien
was
bringing
up
last
call,
and
here
is
a
link
to
the
issue.
I
will
also
add
it
to
the
we'll
set
it
to
the
hack
MD.
F
Yeah,
so
essentially,
how
should
we
proceed
with
the
initiative
to
handle
hosting
the
weekly
Jupiter
lab
call?
So
one
question:
there
is:
how
should
we
provide
access
to
to
Egyptian
account
for
hosts,
so
credentials
are
stored
in
one
password,
based
on
the
discussion
with
Steve?
There
is
no
apparent
way
to
safely
provide
access
to
like
anyone,
Clarion
yeah.
A
So
I
don't
know
if
you
are
with
the
latest
update
to
this
Zoom
account,
but
we
used
to
have
one
blocker
that
was
needing
to
use
the
project.
Jupiter
Gmail
account
as
the
to
the
multi-factor
and
that
problem's
been
resolved.
So
now
we
can
share
the
multi-factor
and
the
credentials
with
people
using
one
password.
So
so
at
least
we
have
that
we
still
don't
have
the
way
for
an
arbitrary
person
and
I,
don't
believe
we
ever
will
because
it's
it's
an
account
based
system.
So.
F
Please
continue
I
think
then,
taking
that
into
account,
it
seems
like
it
would
make
sense
to
maybe
restrict
it
initially,
at
least
to
Jupiter
lab
council
members
that
volunteered
and
then
kind
of
like
look
at
it
at
person
by
person
basis
based
on
the
like
applications.
You
know
from
community
members
or
something
yeah.
So
this
was
one
point
and
the
second
one
was
in
the
same
thread:
I
published
I
put
their
link
to
a
hosting
guide
draft,
got
some
feedback
already
from
Jason
there.
F
A
F
F
Okay,
so
thank
you
on
that.
Are
there
any
opinions
on
that
previous
point
about
you
know,
providing,
maybe
solution
would
be
here
to
provide
access
to
all
gypso
lab
console
members
or
what
are
the
next
steps
here?
Is
it
some
things
that
Security
Group
needs
to
discuss?
What
do
you
think
here.
F
C
A
Against
others
to
have
access
to
those
credentials,
okay,.
F
C
A
I,
didn't
I
didn't
push
for
that
this
week,
because
I
was
open
to
sort
of
entice
others
to
also
volunteer
basically,
but
but,
as
people
add
themselves
as
volunteers,
there
I
can
give
them
the
the
access
to
those
credentials
and
also
once
we
have
a
couple
more
people.
Maybe
let's
just
have
a
call
together
and
or
or
we
could
do
it
in
an
issue
depending
on
how
difficult
it
is.
But
yeah
we
can
pick.
E
E
A
Mike
said
his
availability
increases
in
Q3,
and
so
that's
another
a
few
weeks
from
now
and
beyond
that,
you
know
if
we,
if
we
split
it
into
three,
that's
much
better
for
me,
obviously,
but
more
than
Mary
right
cool
great.
Thank
you
very
much
Andrew!
Yes,.
A
Oh
perfect,
I
haven't
looked
at
that
issue
in
a
little
bit,
so
I
missed
that
that's
great
awesome!
Okay,
thank
you!
Cool,
okay,
so
Mike
you're
next
and
take
as
long
as
you
wish.
I
don't
want
to
have
the
additional
discussion
conversation,
so
you
really
pad
it
out.
Yeah.
E
There
is
another
point
and
touch
and
that
being
added
as
we
speak,
so
maybe
I
shouldn't
take
as
much
time
but
yeah.
So
in
Jupiter,
lab
4.0,
when
we
migrated
to
code
mirror
six,
we
removed
keymaps.
E
That
means
that
the
key
bindings
are
fixed
and
there
is
no
way
to
change
them
to
preset
such
as
Vim
emacs
Etc,
and
it
was
brought
to
our
attention
that
this
is
a
regression.
It's
not
an
international
one.
I
understand
that
this
happens,
because
in
the
course
of
migration,
there
just
wasn't
enough
time
to
address
all
the
issues,
and
this
one
was
missed
unintentionally
or
maybe
intentionally
add
a
it's
just,
not
clear
that
there
was
a
conscious
decision
to
to
remove
the
key
maps.
So
there
are
two
questions.
E
One
is
because
the
the
code
mirror
six
no
longer
offers
built-in
came
UPS.
Should
we
bring
them
back
into
the
call
using
the
third
party
extension,
which
is
from
Rapids
and
terrific
notice,
it
correctly,
and
then,
if
yes,
I
should
go
into
Jupiter
lab
4.0,
because
that's
fixing
a.
E
H
So,
just
just
to
sort
of
make
sure
the
context
is
clear
here,
because
I
think
minusing
is
there's
still
like
a
lot
of
thing,
a
lot
of
key
codes
that
can
be
matched
keyboard
shortcuts.
That
can
be
mapped
right
now,
but
this
is
specifically
talking
about
the
code
editor.
H
C
E
A
different
conversation
whether
we
should
completely
abandon
their
key
management
by
the
code
editor
and
instead
integrate
all
the
shortcuts
into
our
existing
shortcuts
editor.
That
would
be
require
possibly
more
work,
but
potentially
provide
a
better
user
experience,
because
users
will
be
able
to
modify
every
single
shortcut.
A
A
H
I'd
like
to
ask
a
question
about
this:
sorry:
I
don't
have
Solutions
I
just
have
questions
but
I
just
been
working
a
little
bit
with
the
code,
so
editors
and
so
I'm
and
I
haven't
used.
I
haven't
tried
to
use
like
I,
haven't
in
previous
versions,
tried
to
use
like
a
Vim
mode
for
code
cell
editors
I'm
like
I,
guess
I
I'm
confused
like
what
would
happen
if
you're
you
know
in
edit
mode
in
a
code
cell
editor
and
you
press
the
Escape
key.
E
So
is
not
super
useful
in
the
notebook
bytes
of
which
is
why
tourists
at
Jupiter
lab
perfume
extension
to
facilitate
that,
and
there
are
different
options.
So
you
can
choose
what
is
the
behavior
that
you
expect,
but
even
if
in
in
the
notebook,
you
don't
have
the
Beam
mode,
you
can
still
use
that
exclusively
in
the
file
editor,
which
is
what
some
people
were
using
and
finding
useful.
E
So
having
like
a
split
notebook,
behaving
like
emacs
like
and
Pio
editor
behaving
because
of
him
yeah.
It
was
also
pointed
out
that
the
VM
extension
would
actually
need
to
include
this
extension,
bringing
the
key
map
itself
as
well,
and
if
we
had
that
Decor
that
would
possibly
make
it
easier
to
pull
that
extension
to
Jupiter
lab
4.
A
E
So
I
think
I'm
going
to
open
up
requests,
bringing
Inc
code
mirror
Bim
as
a
dependency
and
let's
see
how
it
works
if
it
works.
Well,
maybe
we
can
add
additional
key
maps
later
on
I
think
that's
a
good
balance
between
adding
external
dependencies
and
trying
not
to
introduce
too
many
features,
attachments,
cool.
A
All
right,
the
German
things,
no
okay,
okay,
so
next
is.
C
C
So
I
have
opened
up
for
request.
I
have
linked
that
in
the
chat.
So
we
need
to
discuss
that.
Should
we
add
this
icon
or
not,
and
what
other
changes
can
be
done
too
Edition.
C
B
Yeah,
so
for
a
little
more
context,
this
is
a
follow-on
to
some
of
the
work
that
I
did
and
it
was.
You
picked
up
the
follow-up
issue
that
we
we
filed
about
this,
where
there
is
currently
no
icon
to
indicate
the
behavior
of
the
toggle
output,
scrolling
behavior
in
Jupiter
lab,
and
so
you
have
to
Mouse
over
it.
B
Your
cursor
changes
to
a
zoom
icon,
which
was
kind
of
a
stopgap
thing
that
we
put
in,
and
this
proposal
adds
an
icon
if
there's
enough
room
for
it
and
I
believe
we're
also
going
to
remove
the
those
cursors
as
well.
Is
that
right,
yeah,
okay-
and
there
were
some
open
discussion
about
that
with
some
other
folks.
But
if
you
want
to
weigh
in
on
this,
this
would
be
good
to
have
as
well
I
I.
B
Personally,
like
the
icon,
we
discussed
it
a
while
back
Gabriella
contributed
some
good
assets
for
it
and
some
feedback
but
curious.
What
other
folks
in
the
community
think
about
it?.
F
D
B
F
Oh
sorry,
I
want
to
say
that
if
someone
has
it
compiled
and
on
their
screen,
you
know
feel
free
to
share.
So
everyone
on
the
call
could
see
what
we're
talking
about,
but
yeah.
E
Great
Point,
when
I
wanted
to
to
highlight,
is
that
I
think
I'm
not
sure
are
other
screenshots
in
the
top
level
command
up
to
date.
So
with
the
different
sizes
were
those
just
not
updated.
C
E
A
Okay,
is
this
unstuck,
like
did
we
know.
F
So
here
we're
looking
I
guess
and
what
bridge
was
sorry
if
I'm
making
your
username
was
writing
in
the
hack
MD?
Is
that
he's
looking
for
more
design
feedback
and
there
was
a
fruitful
there?
Was
there
were
a
lot
of
comments
regarding
design
there,
so
I
guess
what
I
from
what
I'm
gathering
more
input
is
Maybe
singing
here
or
or
what
would
you
say
reach
do
we
do
you
think
we
have
a
consensus
here?
Do
you
seek
for
More
Design
feedback.
F
Do
generally
synchronous
signal
feedback?
What
would
they
say.
C
With
the
current
design
and
the
icon
size,
if
you
have
some
feedback
about
the
size
or
like
we
are
removing
the
big
like,
however
overlay,
that
is
the
gray
shared.
So
we
are
thinking
to
remove
that
so
that
that
is
the
note,
the
problem.
But
what
about
one
of
the
comments
from
Tony
first,
so
I
am
going
to
share
that.
C
So
he
says
that
one
second
yeah,
so
he
is
not
like
he's
not
liking
the
icon,
so
he
has
suggested
some
other
changes,
but
I
think
he
he
couldn't
get
the
right
discussion
but
yeah
the
is
this
like
the
good
good
to
have,
or
this
will
need
some
improvements.
F
Oh
no
worries
I
see
so
yeah.
There
was
some
discussion,
but
my
Mike
thinks
that
this
pair
is
good
to
go
and
we
can.
We
can
follow
up
on
the
changes
in
separate
parts
and
like
fine
tune.
Something
and
yeah.
A
So
thank
you
for
bringing
it
up
here,
because
I
think
sometimes
at
issue
is
yourself
much
faster
when
we
have
a
higher
bandwidth
conversation.
So
great
awesome,
okay,
so
if
no
one
else
has
anything
else
they
want
to
talk
about.
We
have
an
additional
discussion
item,
but
I
will
pause
for
a
second
to
see
if
anyone
else
would
like
to
fill
up
the
rest
of
the
clock.
So
we
don't
have
to
talk
about
the
additional
discussion
item.
C
G
So
I've
been
working
on
that
mermaid
thing:
Steve
does
not
care
and
just
merged
it
on
any
convert.
So
Envy
convert
7.5
speaks
mermaid
now
with
basically
the
same
code,
so
we
can
start
getting
some
feedback
there
on
on
whether
people
use
it,
which
is
cool,
but
in
doing
that
I
also
bumped
up
marked
to
5.1.
G
We
are
still
on
four
dot,
I,
don't
know
what
on
four
and
so
starting
to
throw
some
deprecation
warnings,
they're,
basically
getting
rid
of
a
bunch
of
their
gfm
opinions,
and
so
in
that's
in
that
4.1
timeline.
We
need
to
decide
whether
we're
gonna
go
with
the
newer
version
of
Mark.
G
It's
not
actually
part
of
the
public
API,
so
I,
don't
think
that
would
constitute
a
breaking
change
for
Downstream
Developers,
but
every
time
every
time
we
change
Mark
or
we
change
map
jacks
or
whatever
it
breaks,
something
that
somebody
wants
their
markdown
or
their
law
Tech
to
do.
But
it's
got
a
better
modularity
story.
It's
got
some
performance
improvements.
It's
got
some
redos
problems
that
it
solved.
G
G
We
identified
a
couple
changes
there
with,
like
changing
themes,
no
longer
triggers
a
markdown
re-render,
which
is
probably
great,
except
if
your
diagram
now
disappears,
because
it's
made
of
black
lines
on
a
black
background,
which
is
not
great,
so
I'm
gonna
have
to
do
something
nasty
there
and
then
I
think
that
was
the
only
like,
oh
and
then
some
accessibility,
stuff
Mermaid
has
some
accessibility
features
we're
currently
consuming
them
by
base64
encoding
it
inside
of
an
image
which
has.
G
We're
losing
the
accessibility
features
by
not
doing
an
iframe
or
directly
embedding
the
SVG
we're
not
going
to
embed
the
SVG
just
so
you
know
so
yeah,
that's
just
an
update
on
on
where
that
has
been.