►
From YouTube: JupyterLab Team Meeting - 22 March 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
A
22Nd
weekly
Jupiter
lab
call
I,
don't
know
how
many
people
we
have
on
the
call
today.
Oh
no
I
do
the
UI
19,
there's
19
people
on
the
call,
and
we
have
a
bunch
of
us
in
a
shared
notebook
on
binder.
So
at
some
point
later
in
the
call
we
will
talk
about
issues
that.
B
B
A
Now
we're
just
going
to
jump
straight
into
the
weekly
agenda,
so
the
first
person
on
the
agenda
is
Fred
when
he
wasn't
able
to
make
it,
so
he
has
his
boiling
point
up
with
the
proposal
to
do
beta
before
Saturday.
A
C
C
The
intention
is
to
make
that
into
beta
0
by
the
end
of
this
week
and
be
in
beta
for
two
weeks
then
get
to
an
RC
and
encourage
people
to
migrate
to
rc0
and
any
subsequent
RCS.
The
goal
is
to
have
the
4.00
final
generally
available
release
just
before
Jupiter
Khan,
so
early
May
of
this
year,
if
not
we'll
at
least
have
a
release
candidate
to
talk
about
at
the
conference.
So
this
is
kind
of
an
aggressive
timeline,
but
wanted
to
see
how
people
feel
about
moving
into
beta
by
the
end
of
this
week.
C
D
A
comment
about
bugs
in
the
chat
but
yeah.
C
D
That
beta
is
still
fine,
I
mean
you
can
still
pick
stocks
during
the
beta.
Even
during
the
release
candidate,
that's
okay,
and
as
long
as
we
don't
break
apis
and
also
I
guess,
even
if
we
end
up
breaking
a
little
bit
like
just
a
small
thing:
I
guess
it
was.
It
would
be
also
okay,
as
long
as
it's
documented
during
the
beta
cycle,
so
yeah
we're
not
explaining
it
expecting
anything
big
to
land
anymore,
I
think
so
it
should
be
good.
E
So
I
I
wonder,
are
breaking
changes
which
affect
experimental
API
is
fine
and
I
think
about
LSP.
So
there
is
an
implementation
about
this.
Implementation
might
be
clashing
with
the
extension
and
when
we
will
be
holding
the
extension
soon
and
that
work
might
start
after
we
start
better.
We
might
want
to
change
some
things,
so
I
I
guess
just
wanted
to
clarify
whether
that's
fine
or
how
should
I
proceed
here.
A
So
the
beta
doesn't
come
with
a
hard
guarantee
that
if
we
discover
a
bug
in
the
API
we're
not
going
to
fix
it
and
if
the
bug
is
a
usability
bug,
that's
still
probably
something
we
can
fix
there
at
the
lowest
cost
between
now
and
the
next
release
cycle.
So
if
there's
something
you
need
to
change
because
you're
working
directly
with
an
API
that
was
recently
created
that
the
beta
seems
like
an
okay
time
to
do
it.
Hopefully
it
doesn't
come
up.
A
Hopefully
there's
no
changes
in
the
API
itself,
it's
solid,
but
if
it
does
I
think
honestly,
even
if
we're
in
an
RC,
if
we
find
something
that's
going
to
screw
everyone
who
wants
to
use
a
new
library
that
we
just
created
that
doesn't
seem
like
a
terrible
thing
to
resolve,
so
yeah
I,
think
I
I
think
that's
compatible
with
sember
right.
Our
our
plan
to
treat
beta
a
certain
way
isn't
required
by
summer
summer.
F
A
D
Yeah
I
think
it's
good
I
just
wanted
to
say
that
the
story,
if
you
have
some
extensions
that
you
know,
will
have
to
be
ported
through
geograph
4,
then
now
it's
really
the
best
time
to
do
it,
because
then,
if
you
find
something,
it
will
be
much
easier
to
report
and
we
can
fix
it
quickly.
We've
done
this
with
notebook
7
during
the
whole
Alpha,
and
it
was
great
because
we
could
find
issues
and
fix
them
Upstream.
D
So
again,
yeah
if
you
have
big
extensions,
that
use
a
large
scope
of
the
API
surface
camera.
Please
have
a
look,
so
we
can
catch
things
earlier.
C
Okay,
you
know,
and
to
Andrew's
comment
earlier.
We
do
have
bugs
we
just
filed
about
two
dozen
bugs
across
Jupiter
lab
and
Jupiter
notebook
from
an
internal
bug
bash.
We
did
earlier
this
week,
we're
probably
going
to
get
more
bugs
coming
in
when
we
do
our
bug
bash
next
week,
which
we'll
talk
about
in
a
moment.
C
But
you
know
we
are
not
going
to
get
to
zero
bugs
by
the
time
we
release
4-0
we're
going
to
get
to
a
point
where
comfortable,
releasing
with
a
a
set
of
known
issues
and
then
fix
some
of
them
in
401
and
fix
some
of
them
in
future
issues.
I
think
this
is
something
where,
if
we
want
to
stay
on
track
for
this
release,
we're
going
to
have
to
dedicate
some
of
our
attention
to
both
identifying
and
fixing
the
bugs
to
to
make
us
ready
for
this
point,
O
release.
A
G
A
Cool
all
right,
then,
why
don't
we
continue
to
Jason
and
Andrew's
point
with
the
plan
to
proceed
as
a
threat
sauce
with
the
beta0
by
the
end
of
the
week.
B
Thank
you
very
much,
so
I
I
wanted
to
say
a
couple
of
things.
So,
first
of
all,
we
definitely
when
we
talk
about
better
we're,
definitely
not
talking
about
freezing
bug
fixes
because
well,
there
are
a
lot
of
bugs
and
we
had
a
like
a
bug
bash
within
our
team.
This
week
you
might
have
seen
a
lot
of
issues
being
created
and
we
wanted
to
extend
this
activity
and
ask
Community
to
also
participate
in
a
bug
bash.
B
What
we
mean
by
a
bug
bash
is
a
group
activity
around
one
hour,
long
that
is
dedicated
to
discovering
bugs
discussing
them
and
filing
them
as
an
issues
for
tracking,
maybe
also
assigning
people
to
those
bugs
scope
for
both
Jupiter
lab
and
Jupiter
notebooks,
and
we
would
love
as
many
people
who
work
in
Jupiter
lab
and
Jupiter
notebook
to
participate.
B
Essentially,
we
would
spend
around
40
minutes
so
just
going
each
on
our
own,
through
key
user
flows
and
trying
to
identify
problems,
bugs
inconsistencies,
your
Xbox
and
so
on
and
files
them
and
then
later
we
can
track
them
and
hopefully
squash
the
most
the
biggest
offenders.
Our
team
is
definitely
open
to
contributing.
B
After
the
bug
bash
to
fixing
bugs,
but
we
definitely
would
like
to
help
a
community
here,
so
we
look
to
the
calendar
next
Monday
March,
27
the
same
time
slot
that
is
happening
now,
which
is
9,
A.M,
PDT
16
for
UTC
or
160
1700,
BST
or
5
PM,
6,
PM
or
1800
CF
CEST.
B
So
it
seems
like
a
time
slot
that
is
similar
to
current
meeting
and
it
works
for
different
geographies.
So
yeah,
please
join
it's
already
on
calendar
next
Monday
yeah.
If
you
have
any
questions
or
comments,
please.
C
Yeah,
this
is
the
closest
thing
we're
proposing
to
a
QA
pass
for
the
point
O
release,
and
so
we
encourage
people
to
try
something
that
you
don't
normally
do
like.
I,
don't
typically
use
Jupiter
lab
and
Jupiter
Notebook
on
windows.
So
I
did
that
earlier
this
week,
when
we
did
our
our
team's
bug
bash,
you
know
if
you
use
a
different
theme
or
use
a
different
programming
language.
All
of
these
things
can
help
to
identify
potential
bugs.
C
You
know,
try
to
file
thing
I
I.
What
we
did
was
we
kept
like
a
spreadsheet
where
we
captured
everything
just
so
that
we
could
record
things
quickly
and
then
yesterday,
I
went
through
and
filed
bugs
for
any
new
issues,
and
if,
if
the
same
issue
was
filed
multiple
times
only,
you
know,
we
only
filed
it
once
so,
whatever
system
kind
of
works
best
for
you,
you
know
we
want
to
put
ourselves
in
the
mindset
of
less
experienced
users
here.
E
C
And
you
don't
have
to
do
it
at
that
time
if
that
time
isn't
convenient,
for
you
feel
free
to
block
off
an
hour
of
your
time
some
other
time
early
next
week.
But
we
want
to
try
to
get
to
get
everyone
to
play
around
with
the
software
for
an
hour
file
new
bugs
and
then
that
way.
At
meetings
like
this
one,
we
can
do
triage
or
we
can
start
to
like
identify
a
quality
bar
to
make
sure
that
we
commit
to
fixing
critical
release
blocking
bugs.
First.
A
Cool
thanks
any
questions
or
comments.
A
Okay,
cool
next
up
is
Stephanie.
G
Hi
everyone
so
basically
I
followed
this
issue.
Yes,
not
yesterday,
sorry
last
week,
basically
I'm
trying
to
do
an
extension
that
has
like
a
lot
of
themes
inside
but
when
I
was
trying
to
do
that,
then
I
I
started
wondering
because
the
API
like
the
Korean
API,
you
can
only
declare
one
theme
per
extension
and
I
know
that
Mike
in
that
issue,
he
replied
to
me.
G
Tell
me
like
another
package
that
does
have
more
than
one
theme,
but
I've
been
toying
around
with
that
one
and
I
haven't
been
able
to
install
it
in
my
development
version,
so
I'm
not
sure
what
I'm
doing
wrong
and
also
if
this
has
like
been
an
issue
before
like.
If
anyone
has
tried
to
extend
like
the
API
to
just
not
have
just
one
theme,
but
rather
like
you
know,
like
the
user,
like
the
developer
will
be
able
to
yeah
like
declare
more
than
one
theme
and
then
have
that
one
on
their
extension.
H
H
Don't
think
that
it's
likely
that
you're
gonna
get
multiple
themes
out
of
one
extension
because
they
are,
they
are
handled
in
a
special
way
and
there's
only
one
place
to
discover
stuff
inside
of
there,
but
since
you're
probably
going
to
distribute
it
as
a
python
package,
you
could
have
multiple
extensions
and
you
know
just
use
like
a
the
pattern
where
you
deploy
the
different
extensions,
not
like
the
cooking
cutter,
but
where
you
deploy
them
to
their
actual
names.
H
So
you
actually
ship
multiple
extensions
and
then,
if
you
want
to
have
shared
stuff
between
them,
you
can
have
a
you
know,
a
package
that
isn't
a
theme
extension
that
they
depend
on
like
if
you're
gonna,
you
know,
build
icons
and
stuff
like
that.
There's
no
need
to
go
in
every
one
of
those
scenes
separately,
but
that
does
not
work
today
and
it's
not
going
to
work
in
the
four
release,
because
we
can't
change
how
extensions
work
again.
G
Like
I'm
not
sure,
like
I,
couldn't
make
that
change
to
the
API.
If
we
want
to
like
later
on,
like
I'm,
not
talking
like
to
do
it
like
tomorrow
for
4.0,
but
I
I
could
do
that
change
like
later
this
year
as
well,
but
yeah
like
I
I
will
I
am
investigating
how
to
do
that
like
having
multiple
packages
inside
my
python
package.
But
do
you
have
any
example
that
is
currently
working
because,
like
the
one
Mike
Point
me
out
for
me,
like
I
I
haven't
been
able
to
install
it
in
development
mode.
A
H
G
H
G
H
So
we
used
to
we
used
to
have
a
theme
that
a
dedicated
theme
extension
cookie
cutter,
but
we
got
rid
of
it
because
we
wrapped
everything
in
one
because
we're
trying
to
make
things
less
special.
What
we
may
need
is
a
switch
for
the
top
level
of
the
cookie
cutter
that
lets
you
build
multiple
extensions
that
would
that
that
could
shift
in
one
python
package.
I
think
that
would
be
the
most
productive,
Way
Forward,
okay,.
A
Cool
it
seems
as
though
in
in
even
the
simplest
imagining
of
this.
You
would
want
at
least
dark
and
light
to
be
in
a
one
package,
so
they
install
a
theme
and
it's
starting
to
like
them
that
way,
but
you
know
maybe
maybe
having
more
than
the
two
feels
exotic,
but
if
you
think
two
is
sort
of
intuitive,
then
I
think
that
that
that
applies
to.
We
should
be
thinking
more
about
how
to
do
this
exact
thing,
because
yeah
I
think
many
many
themes
would
want
to
package
dark
light
together,
right,
yeah.
G
A
It
so
yeah
that
makes
sense,
cool,
okay,
any.
E
So
I'm,
following
up
on
the
topic
that
I
mentioned
last
time,
which
is
the
performance
of
CSS,
selectors
and
I,
suggested
on
the
call
I
opened
the
pr
which
will
include
additional
rules
to
the
style
Editor
to
styling
RC,
and
that
includes
a
maximum
of
one
per
HTML
tag
in
select
or
maximum
four
classes,
maximum
or
four
campaign
selectors
and
our
maximum
one
universal
selector.
So
this
star
we
would
ideally
reduce
those
further,
but
this
is
what
I
had
like
time
and
I'm
going
to
do.
E
One
PR,
because
there
were
quite
a
few
changes
that
we
had
to
either
modify
the
stars,
selectors
or
disabled,
to
these
new
rules
to
allow
what
we
already
have,
and
maybe
we
could
go
further.
I
didn't
know,
but
it's
already
called
quite
a
few
Styles,
which
were
actually
not
used
anymore
and
were
so
complicated.
Someone
wanted
to
look
at
them.
Probably
I
thought
that
there's
a
certain
importance,
but
actually
we're
returning
to
delete
that
code.
So
that's
a
nice
thing
about
linters.
E
If
anyone
has
feedback
or
thoughts,
please
let
me
know
on
the
PR,
but
otherwise
I
would
really
appreciate
it.
If
someone
could
have
and
review
it
as
that,
it's
Max
from
play,
because
I
can't
I,
don't
say
anything
so
many
PRS
coming
in
and
then
used
to
manually
review
styles
to
ensure
that
there
is
inspired
the
question.
B
Oh
I
got
a
couple
of
videos
how
you
can
try
to
reach
out
to
Microsoft
to
reach
out
to
support
that
might
take
time,
but
but
they.
F
E
B
Reached
out
to
them
a
couple
of
times,
also
extremely,
if
you
want
to
be
extreme,
we
we
could
tag
tag
them
on
Twitter,
but
I.
Don't
think
it's
the
most
fruitful
way
so.
E
Yeah,
the
the
problem
is
that
there
is
in
Jupiter
lab
test,
though
it's
getting
plugged
by
Windows
security,
and
there
is
a
form
where
you
can
upload
your
binary
and
say
that.
Is
it
false
positive,
but
our
binary
is
too
big
and
we
cannot
use
this
dedicated
mechanism
so
yeah
that
that's
the
issue
that
we
need
non-standard
approach
and
it
would
be
nice
if
it
was
addressed
from
Team.
A
B
Hey
so
earlier,
I
was
talking
about
bug,
bass
that
we
did
as
our
team.
So
one
of
the
bugs
we
found
was
considered
by
Brian
as
a
breaking
bug.
It
is
surely
a
ux
breaking
bug
so
essentially
in
Jupiter
lab
now,
if
you
have
a
cell
near
the
edge
of
the
viewport,
and
you
create
a
new
cell
that
is
created
outside
of
viewport
below
the
viewport
by,
for
example,
pressing
shift
and
enter
right.
B
The
viewport
is
not
scrolling
down
to
make
this
cell
viewable,
which
was
the
case
previously
so
I
have
like
binary,
searched
the
releases
and
then
commits
I
have
identified
the
pr
that
introduced
this
problem,
but
I
have
a
hard
time,
pinpointing
the
exact
line
and
fixing
it
because
it's
almost
six
thousands
line
of
code.
So
it's
a
windowed
virtual
notebook
PR.
If
anyone
can
give
me
advice
or
or
would
like
to
contribute
to
fixing
this
bug,
please
do
I
linked
both
in
the
comments
yeah.
Thank
you.
I
B
E
A
E
E
So
that
might
be
something
that
you
could
use
to
get
familiar
or
find
the
relevant
parts
of
the
code
base.
But
I
also
believe
that
we
already
test
lots
of
this
kind
of
behaviors
using
elata
visual
regression
testing.
So
maybe
first
step
would
be
adding
a
test
case
product
and
if
you
could
do
that,
other
project
or
I
could
look
at
how
to
solve
that
problem
itself,
but
like
even
having
conversion
tests
would
be
part
of
the
world.
Frequently.
A
Cool
great
Okay,
so
we
don't
have
anything
else
on
the
agenda
and
people
have
been
playing
around
in
the
shared
notebook.
F
I
F
All
the
data
control
C
stinks
control.
Z
is
just
not
working
even
when
folks
aren't
doing
stuff
I'm
having
trouble
with
control
Z
as
a
single
user
experience
I'm.
Finding
a
lot
of
the
control
shortcuts
are
broken
with
RTC
control,
X
control,
y
control,
Y
and
control
Z
break
on
multiple
cursors
I
followed
an
issue
for
that,
but
some
of
the
kind
of
corded
things
that
you
might
do
aren't
working
the
way
that
I
would
expect
so
I
think
that's
a
concern.
F
I,
like
it
I
do
it
feels
smoother.
If
we
could
see
the
cursors
and
stuff
that'll
change
things,
but
will
I
be
able
to
turn
this
off
as
a
single
user.
The
RTC
thing
m4o.
A
F
One
of
the
first
things
me
and
somebody
else
tried,
was
attachments.
They
show
up
after
you
refresh
the
UI,
but
they
don't
show
up
when
they're
pasted.
If
they
did,
though,
it's
a
really
cool
feature
like
being
able
to
like
image,
share
screenshots
in
the
markdown
cells,
they
do
persist,
but
they
just
don't
show
up
immediately.