►
From YouTube: JupyterLab Team Meeting - October 12, 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/152
A
Today
we
have
18
people
on
the
call
and
if
you
are
on
the
zoom
Channel,
please
find
the
link
to
the
agenda
in
the
chat
and
add
your
name
to
the
event
attendees,
if
you'd
like
to
sign
in.
If
there's
something
you'd
like
to
discuss.
A
Please
add
a
bullet
point
in
the
agenda
section
with
your
name
and
whatever
topics
you'd
like
to
talk
about
and
if
you
have
something
to
discuss
that
might
take
a
bit
longer,
then
please
add
to
the
additional
discussion
section:
I:
don't
have
any
pre
beginning
announcements,
so
why
don't
we
get
started?
Jeremy
is
not
on
the
call
I
think,
but
he
has
some
items
that
he
added.
Is
that
right
he's
not
on
the
call
okay?
A
So,
let's
see
what
has
he
added
there's
a
new
pre-release
of
duplab,
4
and
I,
encourage
you
to
try
it
out
with
the
command
that
he
has
there.
The
web
installer
preacher
Club
equals
that
string,
4.0.0
Alpha
30.
and
you
can
play
around
with
it.
If
you
don't
want
to
install
it
with
the
binder
that
is
linked
in
the
gist
in
the
agenda,
so
yeah
he's
playing
around
with
it,
and
next
person
on
the
agenda
is
right.
B
Not
yet
free
already,
but
everybody
I
can
start
so
on
the
release
front.
Normally,
today,
I
should
do
the
race
candidate
for
3.5.0.
Mic
has
asked
for
adding.
B
B
So
there
is
some
inconsistency
in
the
in
the
path.
Let's
return,
depending
on
the
drive.
B
So
it's
highlighted
nicely
in
the
in
the
test.
It's
like.
If
you
create
a
new
file,
that's
on
a
certain
path
like
full
slash
test.
If
it's
just
created,
you
would
get
a
path
that
looks
like
this
and
if
you
just
do
the
get,
then
you
will
get
a
slightly
different
path.
So
that's
the
the
first
treble,
let's
say,
and
the
link
to
like
the
the
question
behind
is
like:
oh,
is
it
possible
in
the
front
end
to
get
the
the
path
is
needed
for
on
the
server
side,
so
meaning
here?
B
In
this
case
it
should
be
full
slash
test.
So
the
pr
of
Mike
is
to
add
the
new
optional
attribute
in
the
content
model
that
always
contains
the
path.
That's
in
the
that's
useful
for
the
server,
so
that
seem
perfectly
fine
for
bringing
git
backward
in
3.5.
My
only
question
is
that
I
post
in
comments
is
like.
Should
we
fix
that
behavior
between
like
creating
a
new
file
and
getting
and
getting
a
file?
C
So
I'm,
not
pretty
convinced
about
which
way
we
should
go,
but
I
thought
that
that
could
be
backboarded
to
3.5
before
3.6
was
announced.
So
if
we
are
doing
3.6-
and
there
is
no
consensus,
I'm
happy
to
defer
it
just
seems
like
something
which
would
go
into
a
minor
release
rather
than
a
bug
fix.
Release
and
waiting
for
4.0
will
be
probably
a
bit
long
here
to
address
this
issue,
but
yeah
happy
to
hear
the
comments.
D
So
just
I,
we
use
some
more
similar
thing
to
the
dispatch
pattern
ourselves
or
the
multiple
contest
managers
in
the
back
backend,
but
I,
don't
see
normally
I
don't
encounter
any
issues
with
we
don't
use
the
drives
and
lab
side
to
put
it
like
this,
for
anything
is
so
it
seems
like
it
should.
I
should
have
something
to
say
here,
but
I
don't
understand
exactly
what
the
issue
is,
why
it
doesn't
work
or
what
it
is.
It
doesn't
work.
C
C
If,
if
you
think
that
you
might
have
some
feedback,
I'm
happy
to
differ
and
tweet
for
you
comment
on
the
original
issue,
that
would
be
greatly
appreciated.
D
B
So,
as
Mike
said,
then,
because
we
are
starting
already
at
3.6
Branch,
the
reason
for
it
is.
We
have
a
customers
that
want
RTC
to
be
fixed
in
treated
X
branches,
so,
as
they
are
kind
in
a
of
an
array
like
end
of
the
year
is
approaching
fast.
So
we
we
have
already
started
the
branch
and
we
are
we're
releasing
first
version
like
soon
because
at
const
like
where
so
with
other
colleague,
we
are
a
couple
of
us
working
on
that
project.
B
B
Soonish,
like
probably
like,
within
a
month
we're
already
the
first
beta
and
as
usual,
I
have
opened
an
issue
together,
features
if
others
have
additional
features
like
it's
not
because
RTC
is
a
big
things
that
we
cannot
put
other
stuff
in
it
and
so
feel
free
to
to
add
point
on
the
issue
that
we
of
features
you
would
like
to
to
be
back
ported
on
3.6,
and
then
I
would
like
to
thanks
Mike
and
Andre
for
reviewing
the
big
PR
of
the
notification.
Stuff.
I
think
I
have
taken
all
the
under
comments.
C
B
Account
so
if
you
could
pre-service
final
look,
and
so
we
can
merge
that
that
will
be
appreciate
thanks
and
also
regarding
RTC
I've
opened
an
issue
because
I
was
not
able
to
find
something
already
existing.
This
is
going
to
be
with
free
time,
collaboration,
some
some
discussion
needed
or
forget
to
put
the
link.
Actually,
there
is
going
to
be
some
discussion
needed
for
metadata
that
are
that
are
linked
to
view
State,
and
so
we
probably
should
decide
at
the
community
level.
What's
the
good
behavior
for
for
those
metadata.
B
B
So
in
the
real-time
collaboration
case,
it
may
be
surprising
if
two
users
are
looking
at
output,
if
one
decide
to
add
them
to
just
be
able
to
look
at
multiple
cell
in
the
same
times,
one
the
other
was
actually
looking
at
the
output.
That
may
be
not
what
the
user
are
expected,
so
those
kind
of
view
States
they
may
need
to
be
tackled
differently
in
the
real
time.
Corporation
use
case
so
yeah
feel
free
to
to
go
to
that
issue
and
and
provide
your
Insight
or
experience
on
that
field.
That
you'll
be
very
appreciated.
D
I
think
the
ones
that
sourced
to
the
left
was
first
typically
go
for
it
all
right.
T
RTC
that
you're
bringing
back
to
the
3
6
Branch
mentioned.
Is
this
like
fixes
to
the
current
implementation
that
is
in
the
3x
Branch?
Or
is
it
all
of
the
slightly
breaking
changes
that
were
made
to
fix
RTC
in
the
Forex
Branch
right
that
are
backwards,
incompatible.
B
Yeah
because
it
was
a
man
to
be
experimental,
so
that
part
we
are
taking
the
liberty
of
changing
it,
but
then
the
connection
so
the
then
we
will
still
keep
the
synchronization
of
the
ygs
model
with
the
model
DB
inside
3.5
3.6,
so
that
normally
we
will
be
able
to
have
consistent
Behavior
with
3.5
with
people
relying
on
signals
and
stuff
like
that.
So.
D
B
Yeah,
that's
the
plan.
Yeah,
okay
and
we'll
add
some
of
the
interface
like
the
side
panel
to
be
able
to
say
with
connect
it
and
to
to
in
which
files
to
jump
directly
to
a
user
position,
but
those
are
less
controversial.
Let's
say
yes,
it's
new
features.
B
They
even
won't
I
think
because
even
the
ux
are
under
the
flag.
If
the.
If
the
flag
is
not
on,
then
the
new
panel
are
not
displayed.
C
Is
the
question
regarding
the
RTC
does
that
fix
the
Global
and
to
or
document
to
item
to
issue.
B
E
C
And
for
cutting
the
notification,
PR
I
I
think
that
it's
it's
in
pretty
good
shape,
but
I
just
wanted
to
highlight
that
the
public
API,
all
these
methods
return
as
string,
which
is
the
identifier
of
the
notification,
and
my
question
is:
should
we
possibly
be
returning
disposable
object
and
if
not
that's
fine,
but
I
just
wanted
to
get
some
other
opinions
on
that
one.
Before
approving
the
pr.
A
This
is
a
4.xpr
right,
it's
not
going
to
be
backboarded,
so
we
can
still
for
a
short
while
modify
the
API
if
we
think
that
that
becomes
necessary.
But
since
we
don't
have
that
many
consumers
of
notifications,
yet
maybe
it's
not
obvious
whether
we
want
to
return.
So
what
does
the
Disposable
do
in
your
mind?
It
it
clears
away.
The
visual
notification
on
the
screen
is
that
what
you're,
envisioning
I
see.
C
Yeah
and
you
don't
have
to
worry
about
passing
the
ID,
you
have
an
object
to
work
with,
so
all
the
methods
such
as
updating
or
disposing
in
that
case
would.
A
C
I,
don't
have
a
strong
preference,
I
I
think
it's
it's
fine
either
way.
The
other
thing
is
that
when
you
have
an
object,
you
can
type
it
easily.
When
you
have
a
string
that
type
safety
is
taken
away,
so
you
might
pass
an
ID
which
is
not
an
ID
or
not
the
correct
ID.
A
Okay,
I
mean
I
I.
Think
that's
a
good
point,
but
I'm
not
sure
I
mean
what
do
you
think.
B
Yeah
I
didn't
do
it
because
first,
the
library
or
the
that
we
are
wearing
and
it's
using
a
string
as
an
identifier.
So
that's
the
reason
the
API
mainly
is
coming
from.
B
Not
sure
is
it's
really
what
we
will
we
want
to
do,
because
if
we
return
a
disposable
object,
that's
probably
mean
usually
we
are
doing
that
when
we
want
only
the
user
that
create
the
object
to
be
able
to
manipulate
it,
but
we
could
have
in
the
case
of
notification.
We
could
have
other
parties
to
interested
of
playing
with
notification
like
if
you
want
to
connect
to
to
a
back
end
the
notification
center
or
if
you
want
to
to
a
further
UI
that
are.
B
A
Okay,
I
think
in
the
interest
of
moving
forward.
Maybe
we
should
ship
this
PR
and
see
how
the
API
feels
and
see
if
it
would
benefit
from
modifying
it.
But
since
it's
already
pretty
large
and
since
people
spent
time
reviewing
it
already
and
it's
in
a
pretty
good
State
I
would
propose
putting
that
into
a
follow-on.
If
we
decide
to
go
that
way,.
F
How
long
all
right,
just
an
announcement
for
me
today
with
the
notebook
7,
pre-release,
accessibility,
stuff,
we've
kind
of
been
talking
about
it
for
a
while,
but
haven't
really
tested
it
I
know
that
knowing
how
to
look
for
these
things
has
been
a
question
for
people
a
lot
in
this
community,
whether
that's
for
a
release
or
just
in
reviewing
FDR
and
reviewing
your
own
work.
F
So
I'm
gonna
have
a
little
small
meeting
today,
15
minutes
after
the
scheduling
of
this
one,
so
I
think
it
does
overlap
with
performance
meeting
or
incorrect
on
so
we'll
be
on
a
different
Channel.
But
if
you
want
to
come,
try
some
keyboard
navigation
techniques
on
Notebook,
7,
that's
open
to
all
and
yeah
it'd
be
awesome
to
see
you
there.
F
You
don't
have
to
have
any
knowledge,
just
trying
to
kind
of
see
yeah
see
how
it
goes
see
what
we
can
teach
you
I'll
see
if
this
is
kind
of
patterns
that
we
do
keep
sharing
around
for
how
to
test
stuff
or
not
so
yeah,
exciting
accessibility,
stuff.
Maybe
okay
am
I
getting
a
agenda
yeah.
Let
me
fix
that.
Thank
you.
F
A
Cool.
Thank
you.
This
is
really
good.
If
you
do
have
the
time.
Please
help
out
on
this,
because
this
is
a
really
good
chance
for
us
to
make
significant
improvements
to
accessibility
and
notebook
because
it
is
going
to
be
built
of
or
it
is
built
of
lab
components,
and
so
anything
we
anything
we
improved
there
it.
A
It
also
benefits
the
lab
experience
and
gets
the
lab
closer
to
being
accessible
as
well
and
yeah.
Thank
you
for
leading
this.
A
Cool
okay,
any
questions
or
comments
before
we
move
on.
B
Just
the
link
you
have
passed,
this
is
private
I.
Think
as
Vdara
I
have
three
403.
G
D
Yeah,
so
just
a
technical
question
about
the
3x
Branch,
so
I
wrote
the
pr
for
the
main
branch
where
I
was
using
native
iterators
I
got
inspired
by
all
the
lumino
work
that
was
going
on.
This
is
like
hey.
This
seems
like
a
solution
for
iterators
good,
that's
cool,
I'm
thinking,
that's
probably
I
would
want
to
backboard
it
to
the
tree
Express.
If
possible.
D
A
The
version
of
typescript
and
3X
supports
native
iterators
and
if
you're,
not
if
there's
no
breakage,
because
you're
not
interacting
with
something
lumino,
expects
to
be
an
iterator,
then
you
could
have
a
native
one,
and
no
one
would
notice.
Is
that
the
situation
you're
in
or.
D
E
Just
in
time,
sorry.
G
E
Was
running
upstairs
I
opened
an
issue
that
I
linked
to
on
the
agenda
most
well
Jason
opened
it
and
then
I
added
a.
G
E
E
Now,
looking
through
the
table
of
contents
like
doing
a
zip
inspection
and
I
understand
that
a
lot
of
that
has
been
growing
very
organically,
it's
very
confusing,
especially
for
newcomers
or
folks
that
want
to
start
contributing
or
want
to
have
more
of
a
deep
dive
of
how
Jupiter
lab
is
structured,
how
to
build
extensions,
how
to
contribute
how
to
to
various
things.
E
So
in
that
Spirit
I'm
proposing
well
I
did
a
proposal
on
where
the
existing
content
that
is
already
in
the
documentation.
No,
this
is
surely
existing
content,
nothing
about
creating
new
content
or
rewriting
major
pieces
of
it,
but
where
they
would
fit
within
a
diet,
taxis
framework
that
is
more
oriented,
more,
let's
say,
goal
oriented
depending
on
what
we
want,
folks
that
are
Consulting
a
certain
part
of
the
documentation
to
get
out
of
it.
E
Whether
it
is
very
detailed,
step-by-step
guides
I
think
we
only
have
a
couple
of
examples,
namely
those
predating
on
how
to
build
extensions,
how
to
achieve
a
certain
task.
We
have
a
few
of
those
that
are
now
placed,
or
in
my
proposal
placed
under
how
to's
and
then
we
have
a
lot
of
this
reference
guides
that
are
more
nitty-gritty
details
of
how
Jupiter
lab
its
internals
certain
components
or
certain
parts
of
it
work
are
put
together.
E
It's
going
to
take
a
lot
of
work
restructuring,
so
I
want
to
get
as
many
eyes
as
possible
into
that
proposal.
First
or
a
comments.
E
Mike
has
already
made,
like
some
observations
and
comments
and
I
think
also
Darian
was
there
to
get
it
out
there
and
I
think
this
will
be
a
very,
very
significant
Improvement
for
the
whole
Community
contributors
and
it'll
also
make
it
easier
to
identify
what
parts
need
some
love,
or
some
upgrades
or
some
maintainings
long
term,
and
should
also
make
overall
the
maintenance
usability
of
the
documentation
better
and
it's
a
lot
of
content.
So
I
don't
expect
any
in-depth
details
or
thoughts
or
a
feedback
or
anything
right
now.
A
It
is
definitely
a
persistent
piece
of
feedback
we
get
about
how
it
could
be
better,
but
it's
you
know
it's
it's
easy
to
see
that
it
could
be
better
it's
hard
to
know
how
it
could
be
better.
So
thank
you
for
working
on
it.
Does
anyone
have
any
questions
or
comments
and,
if
you're,
if
you
don't
have
them
fully
formed,
please
participate
in
the
issue
for
sure,
but
if
you
have
any
questions
or
comments
right
now,
that's
cool
too.
C
A
I
just
have
two
quick
sort
of
administrative
announcements.
One
is
I'll
ask
again
if
anyone's
interested
in
hosting
this
call.
However,
please
please
do
there's
a
an
issue
where
you
can
sign
up
for
a
specific
date.
If
you
want
I,
think
I
only
filled
them
in
for
the
end
of
the
year,
but
a
lot
more
last
time
progresses.
A
If
you
have
an
interest
but
you're
kind
of
nervous
and
would
like
to
talk
through
it,
I
am
happy
to
help
with
that,
and
so
are
all
the
other
people
hosted.
This
call
in
the
past,
several
of
whom
are
on
the
call
right
now
and
yeah.
A
Please
do
the
other
thing
is
the
Youtube
channel
I
had
been
neglecting
it
for
a
while,
but
I
posted
the
last
eight
I
guess
or
nine
the
last
two
months
worth
of
calls
on
there,
so
yeah
I,
don't
I,
don't
know
who
watches
those
YouTube
but
yeah
they're
up
there
and
oh
good.
We
have
an
additional
discussion
item
to
talk
about
great
who
added
that
who
is
adding
it
currently
I
bet
it's
a
Tony
fast
joint.
G
Nick
Nick
made
a
demo
of
course,
I
didn't
do
anything,
there's
a
Jupiter
light
demo
on
page.
It's
if
you
check
it
out,
I,
don't
know
it
doesn't
use
reveal
so
it's
cool.
It
has
the
interactive
computation
inputs
and
outputs.
G
It
works
really
well
yeah.
It's
super
cool
I'm
excited
about
it.
So
yeah.
If
folks
are
looking
for
that
presentation,
replacement
I
think
we
all
are
right.
We're
tired
of
hearing.
We
want
another
Rise.
Maybe
this
could
be
a
place
to
organize
around
it.
G
Let
me,
let
me
see,
give
me
I'm
gonna
talk
out
loud
for
a
second,
while
I
figure
out,
if
I
am
yeah,
oh
and
the
other
thing
yeah,
so
I
can
talk.
While
we're
doing
this
one
of
the
things
that's
extra
sweet
about
the
demo
here.
If
I
can
yeah
there
you
go
I
do
have
a
demo.
Is
RTC
works
with
this,
so
you
can
have
so
it's
running
on,
read
the
docs,
which
means
that
it's
all
static
and
you
can
have
your
RTC.
D
G
Cool
all
right
yeah,
so
you
know
your
full
screen.
You
get
your
full
screen
view
you
can
start
moving
around
through
cells,
so
the
keyboard
navigation
is
kind
of
like
tied
to
cells.
G
G
It's
got
a
bunch
of
cool
stuff.
Thanks
for
trying
this
out.
There's
some
history
about
this
right,
so
Nick's
been
on
this
a
few
different
times
at
this
point
and
he's
released
it
everywhere.
Of
course,
you
know
this
is
just
a
weekend
hack
for
Nick,
where
he
builds
an
entire
building,
but
this
is
on
Jupiter
light
running
Empire
died,
oops
go
here
and
there's
a
place.
G
You
can
try
it
out,
or
even
you
know,
start
cooking
up
your
own
presentation
and
seeing
how
it
feels,
but
I'm
sure
that
issues
are
welcome
on
the
page.
A
A
Okay,
so
we
have
some
time
if
there
is
anyone
on
the
call
who
wants
to
talk
about
anything
that
they
weren't
sure
about
earlier
now's,
a
good
time.
I'll
give
you
a
second.
A
Okay,
well
then,
if
not,
we
can
end
the
call
a
bit
early,
so
there
are
two
calls
happening
soon.
Let's
see
23
plus
15
minutes
from
now.
One
is
the
performance
call,
and
one
is
the
accessibility
for
Notebook
seven
pre-releases.
A
So
if
you
are
interested
in
either
of
those
the
performance
ones
on
this
channel
and
the
accessibility
call
is
in
the
agenda,
that's
linked
from
this
one
under
Isabella's
name,
I'm,
going
to
stop
the
recording
in
case
there
are
any
announcements
anybody
wants
to
make.
So
brace
yourselves.