►
From YouTube: JupyterLab Team Meeting - November 23, 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
Hello,
everybody
Welcome
to
the
Jupiter
quickly
meeting
it's
gonna
be
probably
a
short
one,
thanks
to
Thanksgiving
so
and
let's
not
start
with
me,
but
with
Jeremy,
and
if,
in
the
meantime
you
have
additional
points,
you
want
to
bring,
don't
hesitate
to
write
them
on
the
agenda.
B
Okay,
so
the
first
item
is
new
for
the
opportunities,
so
it's
31
check
it
out.
There
is
also
a
new
group
to
add
it
to
the
agenda.
A
new
notebook,
7
queries
as
well
based
off
this
one
from
Lab,
and
the
other
point
I
wanted
to
bring
was
something
that
that
came
up
during
this
pull
request
that
added
the
deprecation
warnings
to
the
blood
extension
store,
update
and
install
commands
and
Nick
raised
the
question
of
whether
we
should
consider
moving
some
of
the
node.js
comments
to
a
different
package.
B
There
will
be
a
sidecar
package
and
there
will
be
a
hard
dependency
on
that
package
for
cloud4
and
then
move
it
to
an
optional
package
for
about
five
and
just
giving
up
time
for
people
to
do
the
switch
yeah.
That's
it
so,
let's
in
this
issue
that
is
linked
there,
we
can
discuss
it
here
or
also
on
the
issue.
Either
is
fine
and
that's
fine,
that's
it
for
me.
A
And
if
nobody
has
additional
comments,
then
I
can
do
my
points.
So
normally
this
should
be
the
performance
meeting
after
this
one,
but
because
it's
not
the
the
best
week
for
people
in
the
US,
we
will
not
making
that
meeting.
A
Sorry
for
the
late
notice,
then
some
question,
so
the
announcement
PR
has
been
backwarded
to
3.6.0
to
be
a
release
in
some
future
and
it's
reading
news
from
us
in
a
specific
repository,
that's
under
a
Jupiter
lab
organization
and
to
create
a
new
news.
We
need
actually
to
publish
a
new
blog
post.
It's
a
it's
a
GitHub
pages
that
Repository
and
and
the
question
is
what
what
protection
like?
What's
rules
do?
A
A
There
are
some
people
that
may
have
additional
rights,
of
course,
because
they
have
rights
on
the
organization
level
and
and
for
no
nepr
needs
to
be
approved
by
two
people
to
get
merged,
and
this
is
not
possible
to
bypass
the
rules
or
except,
of
course,
if
you
are
a
big
admin
and
then
you
remove
the
rules,
merge
it
and
then
put
it
back,
and
the
other
thing
I
have
done
is
that
only
one
blog
post
is
published
on
the
news
feed.
A
C
I
see
the
posts
are
marked
down,
markdown
can
sometimes
have
HTML
things
in
it
are
so
if,
if
we
show
this
rendered
markdown
to
people,
then
we're
not
also
we're
not
just
having
a
reputational
damage
risk
right
in
case
somebody
posts,
somebody
malicious
posts,
something
nefarious
in
it.
They
could
potentially
also
be
a
security
risk
right.
C
So
there
might
be
also
an
important
question
about
locking
down
the
sanitation
and
and
kind
of
texting
against
injections.
Are
we
putting
them
in
iframes,
for
example?
Should
we.
A
So
maybe
I
can
give
additional
information
on
the
implementation
side.
Let
me
share
the
screen
this
one
I
hope
you
can
see
my
screen,
so
a
blog
post
example
is
here
and
actually
what
would
be
displayed
in
the
UI
is
not
the
blog
post
itself,
so
this
part
won't
be
seen
in
Jupiter
lab
UI.
The
only
thing
that
will
be
used
is
the
title
and
the
excerpt
except
to
have
a
notification.
That's
not
too
big.
A
C
A
C
A
But
so.
D
Can
I
can
I
suggest
a
few
things?
I
think
this
is
an
awesome
way
to
reach
out
to
our
users.
Jupiter
lab
is
the
front
door
to
not
just
the
Jupiter
ecosystem,
but
like
the
entire
scientific
ecosystem
for
millions
of
people,
so
certainly
like
we're
discussing
here.
I
think
there
should
be
a
high
bar
and
what
content
gets
published
and
making
sure
we're
not
annoying
people
but
giving
people
useful
information,
obviously
giving
them
ways
to
turn
it
off
if
they
want
to
or
resubscribe
Etc
with
communication
channels.
D
This
broad
I
would
I
would
suggest
we
do
two
things
before
turning
it
live.
One
is
going
to
the
the
new
executive
Council
that'll,
be
presumably
taken
into
you
know,
formed
in
two
weeks,
which
is
be
sort
of
the
stamp
of
authority
from
Jupiter
and
and
I
would
say.
I
would
encourage
us
to
go
to
the
security
team
and
I
mean
vdar
is
bringing
up
some
excellent
security
audit
type
questions
and
I.
Would
the
security
team
might
have
some
good
insights
to
weigh
in
here.
C
D
Is
there
some
place
that
the
sort
of
end-to-end
system,
if
we're
going
to
like
the
security,
Council
or
the
executive
Council,
and
they
haven't
seen
any
any
of
the
background
that
we've
seen
and
and
these
meetings
in
previous
in
previous
meetings?
Is
there
a
short
summary
of
you
know
what
we're
trying
to
do
here?
Kind
of
the
impact
that
this
work
will
have
with
the
process
that
we're
proposing
sort
of
a
design
dock
of
some
kind
that
we
can.
D
Or
even
I
mean
this
repo
that
we
have
the
Jupiter
lab
static
assets,
repo
that
would
be
an
excellent
place
for
sort
of
long-lived
documentation.
That's
a
live
documentation,
not
just
an
issue
that
gets
closed
later
and
maybe
that's
a
good
place
for
us
to
to
gather
around
and
vet
the
process
and
vet
the
mechanism
that
content
is
delivered.
Etc.
D
C
C
This
it's
a
good.
D
And
I
think
it'll
be
helpful
to
have
this.
Also
like
we
don't
have
a
published
process
for
posting
Twitter
tweets
or
you
know
medium
blog
posts,
it's
sort
of.
If
you
know
then,
or
if
you
know
somebody
then
they'll
tell
you
how
to
do
it
Etc-
and
this
is
setting
a
good
precedent
for
us
publicly
documenting
what
our
communication
channels
are
and
how
they're
run,
which
I
think
is,
is
really
healthy
for
the
community.
D
D
We
have
a
medium
blog
right,
that
sort
of
posts,
official
things
from
Jupiter
and
and
is
sort
of
officially
gated
in
some
for
some
notion
of
official
and
same
with
the
Twitter
account,
we
have
an
official
Twitter
account
that
posts
official
things
from
Twitter
for
some
definition
of
official,
but
the
processes
around
publishing
things
to
these
venues
is
not
well
understood,
I
would
say,
and
certainly
not
well
documented,
at
least
not
publicly
documented,
and
so
this
is.
D
D
Use
yes,
and
maybe
it's
the
answer
for
some
people
that
have
been
talking
here
and
there
about
is
Jupiter
stay
on
Twitter.
Well,
this
is
our
new
Social
Network
Jupiter
lab
installations.
Oh.
C
A
Will
definitely
be
great
for
reaching
out
to
people,
so
thanks
a
lot,
a
lot
for
all
those
feedbacks
and,
and
then
I
start
opening
issue
or
notes
or
whatever
for
for
the
executive
console
and
for
the
security
team
and
I
will
address
the
technical
part
of
wrapping
in
an
iframe.
The
notification.
A
Yeah
for
for
now,
actually
it's
yeah,
it's
I'm
by
default,
parsing
it
with
the
Martin,
parser
and
and
then
displaying
it.
D
A
Okay,
then
I
think
I
can
move
to
the
next
question.
So
I've
seen
is
implemented
the
event
service
for
Jupiter
lab.
So
that's
a
new
features.
That's
coming
with
Jupiter
server,
V2
and
so
I've
seen
has
extended
the
Jupiter
app
service
for
that,
and
because
we
are
adding
the
support
for
Jupiter
server
V2
in
3.6,
we
have
back
ported
it.
The
trouble
is,
as
the
code
is
using
a
sync
iterable.
A
Action
has
to
had
to
upgrade
the
target
for
for
the
JavaScript
from
a
yes
17
to
yes,
18.
and
yeah.
I
was
not
sure
it
was
okay,
because
somehow
it's
kind
of
backward
incompatible,
because
that's
mean
implicitly
that
you
need
a
more
recent
web
browser
than
before
and
so
yeah.
The
question
is:
is
it
okay
or
not?.
A
To
to
say
that
the
3
6
packages
will
be
of
a
different
Target
than
three
five,
three
four
and.
C
Oh
see
this
is
for
the
iterators.
C
It's
partial
back
part
of
the
iterators
right.
E
C
A
Actually
I've
seen
has
introduced
it
only
for
the
event
services,
so
he
has
back
ported.
It's.
C
A
A
C
D
I'm
tentatively
plus
one
on
it,
but
so
our
current
browsers
are
is
a
rather
harsh
set
of
browsers.
It's
I
think
current
versions
of
chrome,
Firefox
and
Safari,
and
maybe
Edge.
D
Okay,
yeah,
but
but
that
that
that
is
rather
harsh
for
corporate,
especially
corporate
where,
where
the
LTS
versions
of
these
browsers
are
are
behind,
unless
we
actually
officially
support
the
LTS
versions
of
the
browser,
which
makes
a
lot
of
sense.
F
C
Test,
yeah,
I,
guess
also
a
lot
of
our
tests,
no
longer
use
actual
browsers
for
for
running
them
right
now,
so
jstom
kind
of
things
for
a
lot
of
the
tests.
We.
C
Sure
but
I
mean
that
most
of
the
unit
tests
are
also
just
using
abstractions
or
headless
things.
E
B
So
the
question
was
whether
it's
okay
to
make
the
change
in
a
manner
with
ease
right,
yeah
yeah
in
some
way
it's
kind
of
similar
to
so
one
change.
We
we
did
like
for
three
four
I
think
like
requiring
a
new
by
conversion
right,
that's
the
lower
down
I,
think
3.7,
dropping
3.6.
B
So
that
would
be
I'll
be
tempted
to
say
it's
fine
with
this
change
as
well.
Oh
three,
six.
C
It's
it's
potentially
fine
right
is.
We
should
just
be
careful
about
it
and
actually
yeah
in
control,
as
we
say,
because
the
thing
with
the
python
version
is,
if
you
drop
it,
and
you
put
that
in
the
metadata,
then
pip
will
just
no
longer
considering
installing
it.
So
you
won't
break
anybody's
install
the
problem.
Here
is
if
somebody
just
updates
as
part
of
an
automatic
pull
by
pip,
and
suddenly
the
browser
doesn't
give
some
funny
errors
or
data
loss.
That's
that's
slightly
more
important
important,
but
yeah.
It's
well.
F
F
Off
the
top
of
my
head,
I
can't
remember,
but
a
decade
ago,
when
I
worked
for
Amazon,
we
did
that
for
the
Amazon
websites,
so
I
know
that
technology
definitely
exists,
but
I
haven't
touched
it
in
a
decade.
Yeah.
C
C
C
Anyways
I
don't
know
if
it's
a
good
way
to
ask
typescript
what
polyfills
injected
into
your
build.
D
Just
glanced
through
the
can
I
use
for
all
the
features
it
lists
for
es2018
and
it
looks
like
the
features
that
might
be
a
concern
are
the
regex
features
which
I
don't
think
there
are
polyfills
for,
and
so
it
so
it
looks
like
some
of
the
regex
features
were
started
to
be
supported
by
Firefox
in
version
78
released,
June,
29,
2020.
D
and
so
I.
Don't
think
there's
polyfills
for
those,
so
my
guess
is
there's.
No.
None
of
these
reg
X's
are
in
the
code
base
the
current
code
base.
So
if
we're
not
using
those,
then
it's
not
an
issue.
The
other
features
seem
to
be
supported
up
through,
like
20
early
2020
into
2019.
C
Yeah,
for
me,
the
the
can
I
use
page
is
slightly
broken.
It
shows
the
Prototype,
but
finally
I
promise
to
find
anything,
but
it
doesn't
list
any
data
for
it.
So.
A
So
if
there
is
no
additional
comments,
I
can
move
to
the
last
Point
William
thanks
for
the
the
later
comment.
I
just
move
it
in
all
the
thing
to
make
it
to
position
it
at
the
same
as
the
announcement
thing,
yeah.
E
A
No,
don't
worry
and
then
the
last
point
is
I
finished
a
pure
open
by
an
external
contributor
for
adding
an
option
for
asking
close
confirmation
on
the
document.
The
initial
issue
was
to
make
it
obtain
in
the
current
PR
I
mixed
it
out.
A
The
reason
for
that
is
because
I
think
that
people
tend
to
not
read
changed
luck,
so
it's
better
to
display
them
the
pop-up
and
there
is
a
checkbox
now
on
the
pop-up.
They
say
you
don't
ask
me
again,
and
so
they
won't
see
it
again.
But
the
question
was
raised
on
the
pr:
should
we
still
keep
it
as
an
opt-in,
so
yeah
I'm
just
bringing
the
question
so
that
people
can
provide
their
feedback
on
that
and
I
have
no
trouble
to
change
back
the
the
settings
to
be
opt-in
instead
of
upload.
A
So
let
me
try
my
screen:
it'll
be
probably
easier,
okay,
so
the
there
is
no,
this
pop-up
that
is
showing
if
you
want
to
close
the
document
and
is
shown
by
default,
and
you
can
avoid
like
I
did
by
checking
the
box
like.
Do
not
ask
this
thing
again,
and
the
initial
issue
was
to
have
it.
Opt-In
doesn't
mean
that
by
default
you
don't
see
the
dialog
at
all,
except
if
you
go
to
the
settings
and
activate
the
feature.
C
A
I
think
it's
probably
for
people
that
have
big
notebooks
that
takes
time
to
open,
I
guess
is
the
reason
yeah.
C
I
think
that's
sounds
like
an
opt-in
feature,
because
it
will
be
very
annoying
for
everybody
else.
Even
if
you
have
this
checkbox
a
lot
of
people
spin
up
like
Cloud
things
where
you
don't
have
persistent
settings
right.
C
So
all
everything
that
you
add
where
you
have
to
do
something.
The
first
time
you
launch
Jupiter
lab
a
lot
of
people
will
have
to
go
run,
jump
through
those
Hoops
a
lot
during
a
week.
So
every
little
pop-up
every
little
dialogue
that
you
have
to
that
you're
exposed
to
user
2.
Even
if
it's
the
first
time
there
is
a
cost
to
it.
So
I
think
we
should
be
careful
with
them.
A
A
If
you
want
to
display
them
and
I'm
pretty
convinced
that
for
newcomers,
it's
better
to
have
opt
out
than
opt-in,
because
diving
into
the
settings
is
tough
because
you
first
need
to
know
about
them,
and-
and
you
need
to
like
find
the
one-
that's
yeah
makes
sense
for
you,
so
yeah,
but
I
I
know
the
con
I
understand
the
the
trouble
for
more
experienced
user.
B
Yeah,
just
I
think
what
you
were
trying
to
say
right,
Vidar
was
on
ephemeral
environments
like
on
binary,
for
example,
like
you
just
want
to
share
some
things
with
someone,
and
in
that
case
they
probably
don't
need
to
get
these
pop-ups
right,
even
the
ones,
but
trying
to
ask
them
to
update
to
their
latest
app
because
they
are
not
going
to
do
it.
The
environment
is
going
to
be
destroyed
once
they
they
leave.
So
SEO
I
see
the
point
of
her
not
putting
these
pop-ups
unless
they
are
really
necessary.
A
C
C
Right
so
Jupiter
lab
tour
right
foreign,
so
just
for
for
binder.
You
can
kind
of
go
around
this
because
you
can
control
the
settings
that
the
binder
ship
with
and
if
you,
if
you
have
the
binder
image,
includes
I'm
saying
default-
stereotype
that
that
might
not
be
the
defaults
for
everyone
that
that
can
you
know,
ameliorate
the
problem
slightly.
The
other
thing
I
was
thinking
of
that.
Previously
right
we
had.
C
Can
have
the
the
double
conflict?
If
you
go
back
and
forth,
then
you
can
do
all
these
things.
But
part
of
me,
considering
is
whether
some
of
these
settings
could
be.
You
know
persisted
to
local
store
in
the
browser
instead,
so
that
they're
shared
across
all
Jupiter
lab
instances,
maybe
server
specific
or
URL
specific
or
something
like
this,
but
because.
C
Goes
away
and
you
have
something
like
binder,
then
you
know
if
you
store
the
local
store,
it
still
persists
in
the
browser,
but
there
are
still
technical
challenges
around
it,
but
it
might
be
worth
giving
some
extra
thought
to
it.
Just
some
way
to
to
use
use
local
store
to
to
avoid
some
of
these
pain
points.
B
So
yeah
I
commented
on
the
chat
about
the
binder.
Your
skin
is
like
sure
it's
like
you.
Of
course
you
can
configure.
If
you
can
configure
it,
you
can
configure
a
lot
of
stuff,
but
it's
still
right.
It
adds
quite
a
bit
of
work
to
the
the
ones
who
want
to
configure
their
repo
right.
They
need
to
know
how
to
configure
binder.
So
that's
not
very
obvious
for
the
first
time
and
then
they
probably
want
to
know
to
do
that
for
me
repos.
E
Just
wondering
if
it
doesn't
pop
up-
and
this
is
when
you
close
a
file
that
you
haven't
saved
yet
is
the
other
option
that
it
just
Auto
saves
when
you
try
to
close
it
or
I'm
just
curious.
What
the
whole
picture
is,
because
people
have
expectations
about
web
apps
that
are
different
than
desktop
apps.
Typically.
A
E
A
The
current
behavior
is:
if
your
document
is
not
saved,
the
pop-up
is
not
the
one
shown
in
that.
Pr
is
another
one.
Let's
say:
do
you
want
to
close
it?
Do
you
want
to
save?
Do
you
want
to
discard
the
change,
or
do
you
want
to
stop
the
action?
Okay,
and
this
one
is
the
request
from
some
users
that
want
to
to
have
a
pop-up
anytime,
even
if
the
the
document
is
not
dirty.
Oh.
C
E
E
E
E
C
Yes,
it
makes
sense
for
notebooks
right
if
where,
if
sometimes,
if
you
configure
your
settings,
if
you
close
the
tab,
it
will
close
to
shut
down
the
kernel
right
right,
right,
yeah,
so
that
that
it
might
make
completely
sense
for
some
users
but
I'm.
Just
what
I'm
saying
this
should
be
opt-in,
but
that's
this
subjectively
from
my
head,
but
yeah
going
back
to
that.
C
That's
why
I
I
also
want
some
sort
of
global
store,
not
even
local
store,
in
my
browser
to
say
whether
I
should
have
Auto
closing
closing
brackets
or
not
right
for
Jupiter
lab,
because
I
don't
want
to
have
to
put
this
settings
everywhere.
I
get
a
new
triple
lab
instance
and
and
change
that
setting
every
time
I
visit
a
binder
or
visit
somewhere
else.
It
has
a
Jupiter
lab
instance.
I
want
it
to
be
the
same
everywhere
right.
G
E
I
made
it
so
that
if
you
close
your
whole
browser
tab
for
cook
it
pops
up
a
notification
and
I
had
that
on
by
default
and
I
got
a
large
number
of
complaints
and
people
were
angry.
So
then
I
switched
it
to
be
disabled
by
default
by
something
you
could
enable,
and
people
were
much
happier
with
that.
So
that's
my
personal
experience
with
a
similar,
but
not
the
same
kind
of
thing.
C
Yeah,
so
the
pattern
where
you
have
a
lot
of
dialogues
initially
and
then
you
use
these,
don't
ask
me
again:
thanks,
is
you
know,
typically
a
very
good
way
to
add.
You
know.
Iteratively
have
users
fill
in
settings
as
they
go,
but
it's
that
works
very
well
for
desktop
apps,
but
for
things
where
you
have
throw
away
instances
like
web
apps,
where
you
can
never
reuse
the
settings,
it
is
it's
just
the
logic
changes
but
yeah.
Don't
ask
me
again:
things
is
otherwise
very,
very
powerful.
F
Just
to
word
a
warning
on
the
don't
ask
again:
a
lot
of
people
will
refrain
from
checking
that
box
because
they
don't
know
how
to
undo
it
later.
So
anybody
who's
not
familiar
with
how
to
get
into
settings
and
customize.
Those
might
never
check
that
box
and
just
thrash
against
their
environment
for
forever,
because
they
don't
want
to
do
something
that
they
don't
know
how
to
undo
speaking
as
somebody
who's
done
exactly
that
in
some
apps
before.
F
A
So
thanks
a
lot
for
the
discussion
and
all
the
comments,
all
right,
and
maybe
there
are
there-
are
10
minutes
left.
We
may
stop
the
recording
if
people
want
to
bring
additional
points
out
of
out
of
that.