►
From YouTube: JupyterLab Team Meeting - August 3, 2022
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?q=is%3Aissue+label%3A%22Dev+Meeting+Minutes%22
A
Welcome
to
the
August
3rd
weekly
Jupiter
lab
call.
Today,
we've
got
20
people
on
the
call.
If
you
haven't
already,
please
sign
in
I,
just
pasted
the
agenda
Link
in
the
chat
and
without
any
announcements
up
top.
Why
don't
we
get
started
now?
Fred?
You
are
number
one
on
the
list.
B
Just
a
quick
question
about
issue
forms,
so
I
I
noticed
that
many
users
who
fill
out
microbots,
omit
certain
sections
and
issue
forms
must
make
it
easier
to
understand
what
we
are
asking
for
in
second
favorite
experience
of
coming
in
the
issues
myself
of
the
user's
Place
maintenance.
So
it
gives
this
a
new
picture
which
is
still
in,
but
but
many
other
projects
have
adapted
and
my
question
was:
should
we
are
prepared
to
having
issues
across
representative
languages.
A
Cool
love
them
thumbs
up.
It
seems
like
how
about
this.
If
anyone
has
an
objection,
now's
a
good
time,
if
not,
why
don't
we
try
it
out?
It
seems
pretty
low
stakes
to
try
it
out
and
might
be
helpful.
C
Yeah
I
think
it
would
be
nice
if
contributors
could
kind
of
skip
that
form,
because
sometimes
sometimes
you
know
we
run
into
a
book
and
it's
very
well
known.
It's
a
bug
and
it's
easily
reproducible
I
think
we
should
give
contributors,
perhaps
the
benefit
of
the
doubt
and
allow
them
to
skip
that
form.
A
You
can
I
mean
this
is
probably
too
big
a
thing
to
ask,
but
you
can
modify
the
GitHub
URL
to
go
to
issue
Slash
new
and
just
get
a
blank
issue.
Oh.
D
Discourage
it,
but
it
is
possible
also,
we've
seen
issues
come
in
that
way
when
people
move
them
from
another
repo.
That
just
does
a
blank
form.
E
D
D
A
Cool,
so
do
you,
do
you
object
to
the
form
existing
or
do
you
just
want
it
to
be?
Do
you
want
the
fields
to
be
optional,
like
what
what's
the
request.
C
I
mean
I
I,
guess
like
for
me.
It's
just
like
this
form
that
I'm
seeing
it's
you
know
it's
pretty
long
like
for
a
contribute
for
like
established
contributors
who
already
you
know,
we
already
sort
of
had
that
implicit
trust
that,
like
contributors,
kind
of
know,
what
they're
doing
it
would
just
be
a
bit
cumbersome.
That's
all
like
I
mean
if
you
can
override
it
with
Slash
issues,
Slash
new,
then
I,
don't
really
have
any
objections.
A
A
A
We
have
been
thinking
about
some
of
the
long-standing
maintenance
and
other
things
that
are
in
lumino.
Since
2019.
A
we
have
a
bunch
of
deprecated
classes
because
we
wanted
to
make
sure
anyone
who'd
written
a
phosphor
theme
or
was
targeting
phosphor
CSS
classes,
which
all
had
the
P
prefix
didn't
have
to
modify
their
code,
and
we
had
to
change
the
typescript
to
make
sure
both
of
those
classes
were
added,
and
we
also
had
a
strict
backward
compatibility
requirement
when
it
came
to
switching
over
to
pointer
events
instead
of
mouse
events.
So
we
had
both
attached
that
no
longer
seems
necessary
all
the
browsers.
A
We
support
except
Mouse
events
or
emit
Mouse
events
as
pointer
events,
so
we
can
just
switch
straight
to
just
pointer.
There
are
changes
that
were
made
to
Icon
but
were
kept
in
a
Backward
Compatible
way,
so
icons
had
a
signature
that
was
a
little
bit
wonky
because
they
could
either
be
a
string
which
was
the
icon
clasp
or
they
could
be
undefined
or
they
could
be
an
icon,
renderer,
and
that
is
confusing.
A
A
So
we
never
operated
typescript,
which
meant
there
were
some
nice
features
of
the
language
we
couldn't
use,
and
so
a
lot
of
that
stuff
is
in
the
default
branch
of
lumino
now,
but
there's
outstanding
things
to
do,
I
think
it's
reasonable
to
basically
just
pick
an
arbitrary
point
and
ship
there,
because
strictly
speaking,
this
doesn't
have
to
be
a
major
sorry.
It
doesn't
have
to
be
a
release
that
contains
many
new
features.
A
A
I've
heard
a
few
people
make
the
claim
that
lumino
Farms
performance
and
their
applications,
and
one
of
the
big
things
that's
come
up-
is
hit
testing
for
the
menu
system
and
I
linked
to
a
really
well
documented
comment
that
might
grow
attempting
to
fix
this
and
I
think
getting
this
into
lumino
2
would
be
great.
A
There's
another
issue
that
the
Chrome
developer
tool
showed
that
sum
up
related,
which
is
about
passive
events,
as
opposed
to
like
things
like
scrolling,
which
can
create
latency
and
it
can
create
locking
so
I
was
going
through
the
places
in
the
code
where
that
exists
and
I
kind
of
want
to
see
basically
how's
this
going
to
impact
people,
especially
widgets,
and
you
know,
are
there
people
that
want
to
work
on
any
luminal
things
and
what
are
your
thoughts
in
general.
E
We
had
a
discussion
about
this
in
the
in
the
widgets
meeting
yesterday.
My
guess
is
that
it
won't
well
I
think
it
depends
on
the
release,
we're
releasing
our
pay
widgets.
Eight
very
very
soon.
E
A
A
But
you
know,
if
there's
a
strong
objection,
then
we
all
have
to
have
the
conversation
and
see
if
we
can
arrive
at
an
answer.
My
intuition
is.
It
would
be
good
to
get
it
into
four
and
that's
my
aspiration
in
the
work
that
I've
been
putting
on
it.
A
It's
a
question
of
how
limited
should
our
Ambitions
be
right
now,
I
think
I
actually
made
a
mistake
and
maybe
the
document
building
is
incorrect,
but
otherwise
it's
fairly
shelf
stable,
every
new
PR
that
goes
in
I
think
the
intention
is.
We
could
stop
right
there
if
we
had
to
so
we
can
pick
a
time
and
say
that's
the
time
after
which
we
won't
add
stuff,
because
I,
don't
think,
there's
any
shortage
of
stuff.
We
might
want
to
add.
There's
open
issues,
there's
optimizations
to
be
found.
A
There's
tests
to
be
done,
there's
places
to
go,
replace
you
know
all
of
the
option,
checking
that
we
did
now
well
now
that
we
have
optional
chaining.
So
there's
a
lot
of
stuff
we
could
do
like
my
PR
was
thousands
of
lines
of
code.
Unfortunately
right
and
it's
hard
to
review
that
stuff,
but
because
there's
so
much
of
that
I
think
it'd
be
better
for
us
to
say
pick
a
time
and
say:
let's
not
publish
it
any
later
than
that,
because
there
will
be
Downstream
consequences.
A
E
T
with
minimal
changes
for
us,
probably
just
updating
the
dependency
it'll,
probably
break
up
by
which
it's
seven
so
I
guess
it's
good
timing
that
we'll
be
releasing
iPad
widgets
eight.
So
people
can
migrate
before
Jupiter
lab
four,
but
it
sounds
like
it'll
break
output,
widgets,
seven,
which
I
I
think
it's
okay.
As
long
as
we
get
up
high,
which
is
eight
out
soon
enough
that
people
can
start
migrating
to
it
before
Jupiter
before.
A
Okay,
piyush
and
Gabe
offered
to
work
on
luminos
stuff.
We
don't
really
have
a
fully
triage
and
prioritized
list.
That's
it
so
far,
I
think
it's
only
four
issues
attached
to
it,
there's
two
more
that
are
in
the
notes
that
aren't
issues
they're,
just
like
hints
as
to
how
we
can
fix
stuff
and
I
I
think
it's
time
to
go
through
the
issue
backlog
and
see
which
ones
we
can
associate
with
lung
node.
A
Two
and
I
wanted
to
ask
Mike
if
he
could
either
comment
or
take
a
look
at
or
give
me
a
hint
on
this
hit
test
one
because
it
seems
like
you've
done
a
lot
of
thinking
about
it,
and
it
might
be
that
we
already
have
a
path
out
of
it
and
that's
the
biggest
that's
the
biggest
complaint
I've
heard
so
far,
that's
about
performance
and
lumino
and
it
seems
like
fixing
that
would
be
really
good.
A
Okay,
Steve,
you
are.
B
Yep
thanks
so
I
just
want
to
highlight
the
open
PR
ahead.
My
original
plan
for
the
hatch
migration
was
to
have
everything
in
place,
including
the
blog
post
before
merging
anything,
but
it
turns
out
that
Jupiter
lab
PR
is
self-contained.
The
switch
to
the
hatch
build
back
end,
so
it
probably
makes
sense
to
get
that
in
sooner
than
later.
So
we
can
get
an
alpha
releaser
to
experience
with
that
under
our
belts
and
it's
compatible,
regardless
of
whether
extensions
use
setup
tools
or
hatch.
B
So
if
anyone
I
was
willing
to
review
that
and
get
that
in
I'd
be
appreciate
it,
and
so
what's
holding
up
to
the
blog
post
is
just
me
writing
more
documentation
in
Hatch
Jupiter
Builder
itself.
That
I
can
refer
to
in
the
blog
post.
Just
find
the
time
to
do
that.
A
Okay,
David,
you
are.
C
Yeah,
so
I
just
wanted
to
call
attention
to
some
of
the
work
that
I've
been
doing
for
pretty
much
the
past
month.
Yeah
so
I
wrote
a
design
dot.
So,
okay,
let's
take
a
few
steps
back
like
so
there's
a
lot
of
server
and
client
work
that
we're
doing
in
Jupiter
lab
that
kind
of
meets
the
idea
of
a
file
ID
service
which
basically
it's
basically
the
whole
point
of
a
file.
Id
service,
is
to
track
the
track,
the
identity
of
a
file
across
its
entire
lifetime
right.
C
So
we
have
so.
The
idea
is
like
we
associate
each
file
with
an
immutable
ID
and
given
this
ID,
you
can
always
resolve
it
to
a
path
and
given
a
path,
you
can
always
resolve
it
to
an
ID.
So
this
relationship
is
bi-directional
and
the
whole
point
of
the
service
is
to
preserve
consistency
between
the
ID
and
the
path
and
there's
a
lot
of
tricky
questions
that
come
up
when
we're
dealing
with
what
we
call
out-of-band
edits
right.
So
an
in-band
edit,
is
what
we
do
through
the
contents
manager
right
so
like.
C
C
What
gets
tricky
is
out
of
band
handling.
So
how
do
you?
How
do
you
monitor
file
system
events
that
you
can't
really
listen
to
right
like?
How
do
you
track
that
consistently
and
it's
a
pretty
tricky
question
but
I
over
the
past
few
weeks,
I've
put
together
a
design
document
and
a
rough
implementation
of
how
this
can
be
handled
so
I
just
want
to
welcome
PR's,
there's
already
some
unit
tests
that
track
the
functionality
of
this,
but
I
was
mainly
curious.
C
C
I
think
Kevin
is
already
reviewing
so
I.
Don't
think
anyone
should
feel
pressured
or
obligated
to
review.
I
know.
Zach
is
also
taking
a
look
at
it,
so
like
I
mainly
just
want
to
put
it
out
there.
That's
all
awesome.
Thank
you.
A
Great,
so
we
have
one
item
for
additional
discussion,
but
I'll
wait
a
minute
in
case
there's
an
update.
Anyone
else
wanted
to
make.
B
A
You
know
what
actually
there's
something
I
wanted
to
say
so.
Last
week,
I
floated
the
idea
of
a
roster
on
people
hosting
this
call.
A
I
talked
about
it,
some
more
after
this
call
with
a
few
people
who
stayed
on,
and
then
it
came
up
again
and
the
governance
call
and
I'm
gonna
be
looking
more
into
how
to
set
up
support
for
people
to
do
it
and
making
a
sign
up
sheet
and
helping
sort
of
on
board,
because
even
though
it's
obviously
not
a
very
complex
process,
as
you
see
me
not
doing
all
that
much,
it's
still
some
amount
of
context
that
you
need
to
know
beforehand
and
without
that
I
can
imagine.
A
I
can
imagine
very
few
people,
volunteering
so
I
want
to
make
it
not
a
complex
thing
to
have
to
undertake
and
not
a
big
burden
and
as
soon
as
I
have
some
more
to
show
for
that.
I
will
bring
it
up
again,
but
in
the
back
of
your
own
mind,
if
occasionally,
you
would
like
to
post
the
call
just
keep
that
in
mind,
because
there
will
be
a
sign
up
sheet
sometime
soon.
You
can
do
that,
and
everyone
would
be
grateful.
Most
of
all
me.
B
A
Who
added
the
sci-fi
2022
tutorial
link
and
is
there
anything
about
it?
You'd
like
to
discuss.
E
I
added
it
and
nothing
in
particular,
just
FYI
and
all
the
other
side
by
22,
2022
videos
are
are
linked
there
as
well
and
well.
I
guess,
the
one
thing
I
wouldn't
say
is
thanks
again
Martha
and
Alex,
and
others
that
worked
on
this
tutorial.
D
B
C
E
Same
there
is
also
a
widgets
tutorial
and
several
other
I
think
mentions
of
Jupiter
lab
throughout
the
conference.
So.
A
That
is
awesome,
I'm
glad
what
other
people
can
see
it.
It's
not
just
who
could
show
up
and
talk
about
it.
That's
really
good,
too.