►
From YouTube: ☀️ GSoC CloudEvents plugin mentor meeting 2021.8.02
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
C
C
And-
and
so
it's
it's
also
for
the
jenkins
it's
running
inside
of
my
cluster,
but
we
can,
you
know
in
the
future,
try
implementing
an
ingress
for
the
broker,
so
it
doesn't
really
work
if
it's
like,
if
you're
trying
to
reach
it
from
outside
of
the
cluster.
You
know
something
maybe
a
cloud
event
from
a
postman
or
something
it
doesn't
work.
It
only
is
right
now
working
for
within
the
cluster,
but
we
can
obviously
add
a
new
ingress
or
something
like
that,
make
sure
that
it
also
works
outside
of
the
cluster.
B
C
So
this
is
the
broker
url
for
k
native
and
it
does
have
a
trigger
attached
to
it,
and
the
trigger
is
filtering
on
cloud
events
attribute
ce
type,
so
here
are
some
scripts
which
I
will
be
pushing
out
to
you
can
find
hopefully
soon
so
everyone
can
take
a
look
at
it.
Okay,
so
this
is
we.
This
is
the
this
is
tact
on
trigger,
which
is
a
different
thing.
C
We
want
to
be
looking
at
canada
trigger
it's,
it's
actually
been
kind
of
fun,
just
looking
around
different,
like
tools
and
whatever
terminology
that
they've
been
using.
C
So
this
is
so
here
it
is.
We
have
the
k
native
trigger,
and
this
is
the
attribute
type
which
is
so
it's
filtering
on
cloud
event
and
obviously
you
can
so
the
trigger
is,
or-
or
I
would
say
not
the
trigger,
but
the
sink
essentially,
which
is
stuck
on
is
outside
of
k
native
event
space.
So
that's
why
it's
just
the
uri
here.
Otherwise
it
could
be
a
service
if
it
was
deployed
as
a
product
initiative,
and
this
is
just
the
default
broker,
which
is
an
in-memory
broker.
C
So
whenever
we
want
to
change
that,
to
let's
say
popcar,
maybe
rabbit
and
key
will
just
need
some
change
in
in.
However,
this
is
being
like
written
out
alongside
the
channel
implementation
and
the
broker
implementation.
So
this
is
just
the
default
implementation
right
now
and
again,
this
is
the
url
of
the
k
native
broker,
which
has
the
trigger
involved
and
also
taking
a
look
back
at
the
trigger
itself.
It's
just
filtering
on
cue,
enter
and
reading
okay.
B
C
Actually,
you
know
what
we
can
also
do
is
look
through
the
entire
flow
okay.
So
here
we
are
so
this
is
the
tactile
trigger.
This
is
there's
so
many
things,
I'm
so
confused
about
okay.
So
this
is
the
uri,
of
course,
and
this
is
the
uri
for
the
teton
trigger
or
the
you
know
like
wherever
tecton
is
going
to
be
listening
so
like
the
tecton
event,
listener
and
tectonic
event,
listener
has
the
trigger
inside
of
it.
C
So,
let's
see
here,
I
think
I
also
have
the
events
listed
right
here.
Yes,
so
this
is
the
the
url
that
we
were
looking
at
for
the
broker
or
subscriber
uri.
So
this
is
the
cd
event
listener,
where
all
of
the
events
from
the
broker
4k
native
will
be
routed
to
tactile
event
listener,
and
then
here
we
also
can
do
trigger
binding
inside
of
tecton.
So
I
just
wanted
to
sort
of
check.
C
If
you
know
all
of
the
metadata
is
coming
in
correctly
which,
but
but
we're
not
really
using
it
inside
of
any
script,
it's
just
a
way
to
test
and
make
sure
that
if,
if
we
were
to
pass
any
parameters
from
jenkins
to
tucked
on
to
trigger
a
job
or
anything,
it
was
working,
but
I
right
now
the
script.
I
just
change
it
to
a
simple,
but
it
is
working.
You
know
if
you
wanted
to
pass
it
right
or
job
name.
C
You
just
have
to
maybe
say
like
has
to
put
the
arguments
here,
and
this
is
the
trigger
template,
which
is
just
using
a
simple
task.
Run
of
hello.
Hello
world.
Follow
us
with
these.
So
that's
basic.
Okay,.
B
C
C
C
Working
I'm
so
happy,
so
it
really
is
only
one
again
because
it's
like
filtering,
but
then
there's
also
another
one
which
is
test
two
which
has
a
downstream
configured.
So
if
we
were
to
build
this,
it
would
have
like
two
different
task
runs
since
they're
two
different
jobs
of
the
type
and
try
to
like
see
type
entered
reading.
So
you
can
also
yeah
so
this
one's
just
started
so
there
should
have
been.
I
guess,
two
more
yes,
there
are
two
more
so
fun
yeah.
C
So
that's
the
the
poc
for
now
and
the
the
next
thing
that
I
have
been
trying
to
do
is
so
the
city
not
not
cd,
the.
If
we
were
to
move
from.
Let's
say
this
simple,
like
event
format,
to
like
this
simple
issue
for
protocol
binding
to
kafka
protocol
binding,
we
will
just
have
to
change
a
few
things
inside
of
the
cloud
events
like,
however,
cloud
events
is
written
now,
so
partition
name
the
the
key
wherever
we
are
sending
it
to
for
the
kafka
broker.
C
So
I've
just
been
I've
been
working
on
that
and
it
seems
to
be
working.
I
just
need
to
make
sure
that,
in
terms
of
the
partition,
it's
sort
of
aligned
with
the
broker
that
we
have
it's
just
figuring-
that
out
at
this
point
and
also
there
was
another
thing
which
is
testing
with
arguments.
As
I
said
earlier,
I
was
able
to
do
that.
C
You
know
just
by
passing
in
the
argument
to
hello
job
name,
to
make
sure
that
the
arguments
were
passed
incorrectly
and
the
next
big
thing
is
obviously
going
to
be
creating
the
other
part
of
the
poc
type.
This
week
I
was
not
able
to
work
much
inside
of
like
jenkins
as
a
sync,
like
the
the
ui
part
of
configuration
that
we've
been
talking,
but
I've
been
researching
about
event,
filtering
options
in
java
and
how
we
can
you
know.
C
Like
the
last
time
we
were
talking
how
we
can
implement
it
in
a
way
which
makes
it
easy
to
parse
through
the
entire
body
of
an
event.
But
but
as
mauricio
said
right
now,
if
you're,
starting
with
like
a
simple
use
case,
there
might
not
really
be
a
need,
because
even
if
you're
talking
of
tecton
or
if
you're
talking
of
k
native
broker
as
well,
which
they're
mostly
filtering
on
the
header
itself,
you
know
not
the
header
but
the
cloud
events
metadata.
C
Rather
than
like
the
cloud
and
status
bulb
and
the
the
ceo
which
they're
using
for
like
inside
of
flight
attention.
Let's
go
back
to
the
poc.
C
So
the
interceptor
that
they're
using
here
and
then
you
know
they're
doing
the
matching
or
the
filtering
based
on
the
like
the
cl
interceptor
and
for
body
as
well
like
body
dot,
sh
captain
contact.
So
I
think
it's
over
here
since
it's
like
a
direct
direct
in
the
sense
that
they
know
that
it's
a
connection
with
captain
between
captain
and
tact
on.
So
that's
why
I
like
mentioning
something
like
body.shk
contacts.
C
Is:
is
more
viable
here
than
it's
going
to
be
for
us.
So
I
think
like
right
now,
I'm
more
focused
on
filtering
again
based
on
the
header
or
the
cloud
events
metadata.
If
you're
talking
about
like
the
structured
binary
format
of
cod
events-
and
let
me
see
if
I
can.
A
C
Yeah
maybe
like
we
can
create
a
folder,
which
is
events
like
poc
inside
of
the
cloud
events
plugin,
that
we
have
yeah
well,
I
still
have
the
changes
in
my
like
local
system,
but
again,
like
this
week,
was
more
just
trying
and
testing
around
with
the
poc
itself
just
to
get
an
idea
of
how
these
different
systems
are
working.
C
So
we
can
implement
something
similar
inside
of
jenkins
and
again,
the
I
think
the
one
or
two
kind
of
main
things
which
which
are
to
be
done
inside
of
jenkins,
is
a
sink
and
I
feel
like
now.
It
would
be
ideal
to
implement
that,
and
I
should
start
working
on.
C
It
is
obviously
like
first
when
we
have
the
filter,
like
with
the
filter,
coming
in
I'm
giving
options
to
trigger
different
kind
of
actions,
so
just
that
following
of
filter
and
then
filter
to
action
inside
of
jenkins-
and
another
thing
is,
if
you
know
so,
we
have
the
system
of
jenkins
to
okay
native
to
tact
on,
and
it
does
so
for
for
us.
If
you're
talking
off
as
a
sink,
it
does
take
away
or
even
not
even
has
a
thing,
but
even
as
a
source.
C
C
You
know
this
should
be
something
that's
included
as
part
of
a
plugin
and
if
so,
how?
Because,
if
it's
not,
then
again,
I
I
think
that
we
might
have
to
implement
that
system
of
h,
like
resistance
to
network
failures
and
all
of
that
stuff
inside
of
jenkins,
you
know,
maybe
as
a
source
or
maybe
jenkins,
doesn't
think
I
would
like
love
to
hear
you
guys
ideas
and
that.
A
Something
that
makes
this
process
and
makes
this
plug-in
more
resilient
against
network
failures
is
super
interesting,
but
it's
also
it's
an
additional,
quite
big
piece
of
work.
If
we
can
use
an
existing
tool
that
does
that
for
you,
then
I
would
lean
heavily
on
that
for
now
and
then
leave
that
additional
work,
if
we
are
bringing
it
into
the
plug-in
for
a
little
bit
later.
Does
that
that
seem
like
a
good
workflow
for
you,
or
is
it
something
that
you
were
really
excited
to
tackle?
Okay,.
C
Yeah
I
mean
I
feel
like
I
am
certain,
like
I'm
actually
kind
of
excited
the
prospect
of
including
like
k
native
broker
inside
of
jenkins,
especially
like
jenkins
as
a
sorcerer's
sink,
and
I
think,
like
I
don't
know
it
just
really
excites
me
when
I
feel
that
our
system
is
going
to
be
both
implementing
asynchronous
flow
of
sending
events
and
receiving
events,
but
also
just
yet
it's
going
to
be
resistant
to
all
transient
failures
and
stuff
like
that.
C
But
it
does
make
sense
to
for
now
like
focus
on
just
in
consistency
class
is
and
then,
when
that's
done,
then
we
can
think
of
implementing
this.
As
like
an
additional
feature,
you
know
like
collaborate
with
canada
broker.
A
C
Just
configuring
this
was
so
fun
but
like,
as
I
was
saying
so
when
I
so
there
you
know
there
obviously
are
different
name
spaces
and
when,
like
I
was
running
some
of
these
scripts,
I
did
not
know
that
some
of
them
were
actually
like
going
to
default
name
space
just
like
so.
For
example,
if
I
had
the
tech
tone
event
listener,
which
is
which
was
listening
on
like
cd
events
or
text
on
cd
ones,
then
another
part
of
tekton,
which
was
actually
from
the
trigger,
which
was
just
on
default
namespace.
C
C
If
you
have
no
idea
how
many
times
I
went
through
the
same
process
of
deleting
the
k-native
namespace
implementing
the
k-native
like
eventing
part,
which
is
like
the
k,
native
core
components
and
the
k
native
additional
like
crds,
every
time
and
running
those
cube,
ctl
apply
whatever
whatever
is
gmo
files
and
then
it's
it's
always
giving
me
the
same
that
your
empty
channel,
just
like
the
multi
tenant
channel
for
okay,
the
the
default.
It's
like
that's
I've,
all
of
the
pods
are
running,
except
that
I'm
like
what
is
going
like,
I'm
not
sure.
C
What's
going
on,
I
don't
and
then
I'm
like
debugging
and
I'm
like
looking
at
the
logs
and
I'm
still
like.
I
don't
see
an
error.
I
don't
see
any
error
inside
of
the
logs.
It's
all
info,
no
error,
no
warning
and
then
just
for
a
reason.
I
just
simply
logged
into
aws,
and
I
just
like
looked
inside
of
my
cluster
just
for
I
had
no
idea.
I
was
just
like.
Maybe
I'll
just
like
try
looking
what's
going
on
and
it's
it
says
you
don't
have
enough
cpu
cores
and
I
was.
C
C
That
is
good
right
yeah!
I
think
it
was.
C
It
was
quite
fun
implementing
this
and
next
I'm
really
looking
forward
to
the
opposite
part
of
jenkins,
being
the
sink
and
tucked
on
or
captain
being
the
source
and
also
trying
this
out
with
captain
as
well,
because
because,
like
you
know,
we
are
developing
this
across
a
suite
of
tools
or
like
for
a
variety
of
tools,
so
it'll
be
kind
of
fun
to
see
how
this
is
going
to
work
with
not
just
tecton
but
also
kept
in
or
whatever
tools
are,
can
act
or
are
using
cloud
events.
C
A
Yeah,
I
think
that's
awesome,
so
I
know
we
spoke
a
little
bit
before
before
the
recording
about
writing
things,
but
it
would
be
really
interesting
to
add
as
much
of
that
as
you
could
into
the
jenkins
interoperability
in
the
cloud
post
for
the
cdf
newsletter,
because
that
is
very
exciting
and
you
may
or
may
not.
I
totally
do
this
up
to
you.
I
mean
it's
your
work
and
you
can
present
as
you're
like
it
might
be
nice
to
get
some
feedback
to
you
from
the
event
sake
on
that.
A
A
A
So
we
are
posting
up
all
the
pre-recorded
videos,
including
yours,
that
we
have,
and
I
just
need
to
figure
out
if
we're
going
to
put
it
in
a
cdf
channel
or
we'll
put
it
in
the
and
one
of
the
jingles
channels,
probably
for
gsoc,
and
then
you
can
link
to
that
for
your
post.
If
you
are
comfortable
writing
one,
we
would
love
for
you
to
write
one
for
the
jingen's
blog
and
then
when
these
are
all
up,
they'll
probably
be
scooped
up
in
some
manner
from
the
cdf
and
referenced.
A
You
know
either
in
a
blog
post
or
in
some
way,
and
then
there's
the
cdf
newsletter
and
then
there's
also
devops
world.
We
definitely
want
you
to
present
it'll,
be
a
lightning
talk,
but
I
I
sent
around
an
email.
I
don't
know
if
you
saw
the
email
this
devops
world
would
like
lightning
talks
and
it'll
be
shorter,
but
they
want
to
do
it
soon.
So
it's
kind
of
I
don't
know
how
different
the
presentations
will
be
from
the
midterm
demos,
but
it
doesn't.
It
doesn't
really
matter,
but
they
want
to
record
that
soon.
C
Yeah
that
all
sounds
really
fun
and
exciting,
and
I'm
really
sorry
the
midterm
vlog
took
a
bit.
It
was
like
I
was
planning
on
doing
it
earlier,
but
that
week
with
like
power
cuts
everything
don't
even
want
to
talk
about
that
and
in
terms
of
the
devops
world
presentation
yeah.
I
actually
am
mostly
really
excited
about
that,
and
I
just
saw
I
did
see
the
email
and
I
feel
like
I
might
do
another
presentation
with
the
new
sort
of
poc
that
we
have.
You
know
that's
cool.
A
C
It
was
interesting,
but
at
that
point
it
like
you
know
unless
you
see
something
working
with
other
other
sort
of
systems,
because
we
are
developing
this
essentially,
for
you
know:
interoperability
between
ci
cd
tools
but,
like
you
all
suggested
such
a
great
idea
of
doing
this
poc,
and
it
just
puts
everything
so
much
more
in
perspective,
and
that's
nothing
really
and
also
we
have
the
first
star
on
the
repo
and
I
got
so
excited.
A
C
Great,
that's
awesome,
so
I'm
excited
for
how
people
might
end
up
using
it
and
in
terms
of
feedback
from
the
wednesday
community.
C
How
to
what
maybe
I
can
do
is
try
the
like
the
demo
that
we
are
doing
for
maybe
devops
world.
I
can
try
creating
that
and
maybe
like
submitting
that
to
the
eventsec
team,
so
they
can
have
a
look
at
it
and
suggest
additional
feedback,
but
I
feel
like
I
might
want
to
do
it
after.
I
also
have
captain,
as
a
sync
included,
just
to
like
just
to
kind
of
you
know,
demonstrate
that
it
works
with
different
systems.
C
So,
like
people
know
that
it's
not
actually
like
tightly
coupled
yeah,
I
feel
like
we
can
create
multiple
subscriber
uris
inside
of
the
inside.
C
Like
you
know
safely
how
a
single
your
eyes
we
have
one
single
subscriber,
maybe
we
can
like
either
create
another
subscriber
which
can
be
the
captain
or
just
create
another
trigger
which
is
listening
on
different
kind
of
attributes
for
cloud
events
and
then
trigger
captain,
but
I
feel
like
we'll
have
to
see
it.
How
captain
works
with
this,
since
you
know,
since
techdon
definitely
had
kind
of
a
straightforward
way
if
there's
an
event
listener
an
event.
Listener
has
a
trigger
connected
to
it.
So
so
I
was
just
it's
straightforward
in
that
sense,.
C
Yeah,
I
might
also
create
another
sort
of
like
an
ingress
for
so
this
is
an
ingress
that
I
had
to
or
like
I
created
for
the
the
cloud
events
listener
for
text
on
like
the
event
listener
for
techdon.
So
you
know
how
we
had
the
public
subscriber
uri
instead
of
like
a
uri
for
the
clusters.
C
The
cloud
events
broker
k
native
broker,
so
we
can
again
like
reach
out,
send
in
requests
outside
of
yeah.
Those
are
those
are
like
the
few
things
that
I'd
like
changing
inside
of
the
poc
and
see
how
fast
we
can
accomplish
that.
I
hopefully
should
be
fast
enough,
but
if
that
doesn't
happen,
maybe
you'll.
Just
like
post
the
video
with
tucked
on
when
we
like
typed
on
jenkins.
C
It
still
looks
okay,
so
we
can,
you
know,
have
cloudvents
player
or
sockeye
and
then
tucked
on
for
both
the
event
16
and
also
for
the
cdf
interoperability
article
and
also
the
box
one,
and
we
can
see
how
far
it
gets
by.
C
And
I
like,
I
did
have
one
another
question
on
so
this
is
not
really
related
to
the
plugin
itself,
but
it's
more
about
like
licensing
and
also
where
should
we
put
our
you
know
if
someone
has
any
issues
or
any
bugs
or
they
would
want
to
submit
a
request
for
a
feature
book
or
anything?
Where
should
we
put
that
for
our
plugin.
C
A
Yes,
I
have
a
strong
preference,
always
for
github,
but
it's
true
that
jingles
has
this
whole
system
with
jira.
So
it's
really
to
some
extent.
Up
to
you
I
mean
the
jenkins
jr.
I
guess
makes
sense
for
the
jenkins
project,
but
I
would
imagine
people
will
often
jump
on
and
raise
issues
on
the
github.
But
I
guess
you
should
have
information
in
the
readme.
D
D
C
Yeah,
that's
that's
true.
A
C
Yeah
we
we
might
have.
I
am
obviously
I
feel
like
more
comfortable
using
the
github
repo
because,
like
I
have
looked
around
jenkins
jira
and
maybe
like
looked
around
how
we
can
submit
an
issue
or
like
a
request
or
whatever,
but
I'm
not
really
sure
how
it's
going
to
tie
up
with
the
entire
like.
If
someone
raises
an
issue,
do
I
have
to
like
go
and
check
every
time,
or
does
it
directly
get
pulled
in
from
jira
into
the
I'm,
not
sure
so
I'll
again
have
to
look
into
that?
C
It's
and
once
we
have,
I
think
he
has
submitted
a
request
for
jira,
and
once
we
have
the
repo
like
posted,
then
maybe
I'd
know
better
in
how
people
can
go
in
and
raise
issues
there,
because
since
I
don't
really
know
how
it's
going
to
look
outside.
Obviously
right
now,
I'm
more
comfortable
with
looking
at
home.
B
C
Yeah,
I
just
need
to
be
added
to
the
jenkins
org.
So
when
I
was
trying
to
push
it
out,
it's
been
like
quite
quite
some
days
and
trying
to
get
this
release,
but
I
think
the
first
error
was
the
maintainer
when
I
did
not
have
access,
but
then
the
other
was
getting
permissions
for
hosting.
So
I
was
not
sure
if
it's
an
issue
with
you
know
jira
or
is
it
some
other
issue?
C
So
I
think
without
is
helping
with
that
and
he
has
requested
for
being
added
to
the
gen
can't
org
itself
inside
of
github.
Hopefully
that's
going
to
work
and
and
on
licensing
I
definitely
see
that
the
default
is
mit
or
jay
are
like
gnu,
but
just
sing.
You
guys's
opinion.
C
No,
no,
I
was
just
I
feel,
like
you
guys,
have
more
experience
on
this
than
I
do.
So
that's
why
it's
appropriate
to
ask
you
for
a
second.
D
It's
just
it
it's
le
it's
it,
it's
less
respected
than
than
some
versions
of
the
the
other
licenses,
not
not
all,
but
it's
you
know
it's.
It's
just
easy
to
know
what
you're
getting.
C
C
So
if
you
guys,
you
know,
can
give
me
information
on
just
like
vulnerabilities
and
other
security
issues
inside
of
the
plugin
and
if
there's
additional,
like
anything
that
I
can
include
in
inside
of
our
home
file,
which
does
that
for
us.
A
Partnered
with
snek
to
do
scanning
on
on
the
jenkins
project
and
and
a
lot
of
its
plugins.
So
that
would
be
what
we
would
go
with,
and
I
will
just
double
check
how
to
add
that
to
the
rebound
stuff
and
make
sure
that
that's
appropriate
for
this.
But
it
that
will
likely
be
the
the
answer
to
the
question.
C
And
that's
snake
you
mentioned.
A
A
Projects
and
jenkins
has
been
involved
in
a
lot
of
the
discussions
of
this
and
might
yeah.
So
I
think
snake
will
will
be
the
way
that
we
go
forward
with
it
and
I'll
just
I'll
find
out
some
info
for
you.
A
But
yes,
it
was
a
very
good
question
and
really
important.
Well,
it's
very
positive
for
the
plug-in
to
do
scanning,
and
I
think
that
sounds
like
a
really
good
thought
on
your
part.
It's
great
that
you're
already
thinking
about
that.
It
will
probably
help
adoption
as
well,
but
in
any
case
it's
the
right
thing
to
do
so.
C
I
was
like
fascinated
when,
like
I'd,
go
and
see
okay,
vulnerabilities
and
plug-in,
but
also
it
became
more
sort
of
like
present
inside
of
my
mind
when,
when
we
were
inside
like
when
we
were
when
we
were
looking
at
all
of
the
demos
for
the
first
phase-
and
I
was
like
you
know-
obviously
when,
if
you're
talking
often
like
runtime
security
and
if
we
have
like
jenkins
running
as
a
container
or
whatever,
there
are
tools
for
that,
but
but
for
you
know
like
there's,
falco
and
whatever
stuff,
but
when
we
are
referring
to
like
the
plug-in
itself
and
all
like
additional
vulnerabilities
inside
of
this
single
plug-in.
C
So
you
know
like
that
last
and
from
like
the
kubernetes
security
operator
that
we
were
looking
at
and
it
was
like
if
this
plug-in
has
vulnerabilities,
it's
not
going
to
install
and
I
was
like
whoa
okay.
So
we
need
to
work
on
that.
So,
yes,
that's
why.
That
has
been
sort
of
on
my
mark
to
make
sure
that
we're
complying
with
security
issues
as
well,
because,
that's
obviously,
I
think,
very
important.
A
Yeah-
and
I
I
really
like
that
in
this
gsa
gear,
I
feel,
like
all
the
gsac
projects
really
had
that
in
their
mind
and
we're
really
thinking
about
it,
which
I
think
is
one
really
impressive
from
the
point
of
view.
The
students
really
good
for
the
jenkins
project
as
well,
and
then
just
really
nice
to
see
that
becoming
sort
of
an
accepted
top
level
concern.
You
know,
I
think
that's.
It
was
really
excellent.
So.
C
Yeah
yeah
it's,
it
was
like
actually
really
cool
hearing
issues
because
there
were
two
or
three
different
plugins,
also
the
plugin,
the
spinnaker.io.
C
That
was
like
the
runtime
security
for
the
containers
that
you're
going
to
be
running
and
and-
and
then
you
know
so-
I
was
just
like.
Well,
obviously
we're
not
running
an
entire
system
or
we're
not
running
some
like
multiple
sort
of
like
containers
as
a
part
of
the
plug-in,
but
but
still
the
plug-in
itself.
It
can
have
different
vulnerabilities
from
our
dependencies
I'll
check
out
snake
and
those
were,
I
think,
questions
I'm
so
just
going
to
add
the
date.
C
A
A
You
can
realistically
expect
in
a
in
a
few
short
weeks,
so
I
wouldn't
expect
what
the
gsox
students
have
to
advance
that
much,
but
nonetheless
just
updating
that
information
and
then
on
that
email
chain
I
put
alissa
tong's
email
address,
that's
really
the
person
who
will
have
more
additional
information
on
how
to
sign
up
for
like
scheduling
your
recording,
so
they
what
they
would
like
to
do
from
my
understanding.
A
Is
they
don't
want
you
to
do
your
own
recording
they
want
you
to
actually
sign
up
and
do
a
live
presentation
which
is
kind
of
fun,
although
you
can
discuss
it,
if
you
prefer
to
do
a
pre-recorded
one,
I'm
sure
there's
some
flexibility
there,
but
I
would
respond
and
just
ask
like
how
do
I
sign
up,
because
I
don't
actually
know
how
you
all
sign
up
for
to.
I
was
just
kidding
information,
although
I
can
I
can.
I
guess
I
can
paint
on
this
and
say
well
how
how
do
they
all
sign
up?
A
C
No,
that's
totally,
okay,
and
also
like
again
thank
you
for
for,
like
putting
pulling
together
such
a
great
event
for
for
the
demos
and
everything
that
was
absolutely
that
was
really
fun
and
amazing
and
yeah.
C
A
That's
sweet
yeah,
I'm
so
happy
with
gsoc
this
year,
especially
especially
your
project,
but
all
of
the
products
are
great,
so
it's
really
nice
to
sort
of
give
as
much
of
a
platform
for
for
the
students
and
especially
you
to
discuss
your
work
and
celebrate
it
because
it's,
it's
really
amazing,
actually
what's
being
done
this
year,
so
very
excited
any
other
questions
you
have
for
the
work
you're
doing,
but
also
so
I
was
thinking
what
what
you
were
saying
about:
aws
cpu
course
again.
A
C
Thank
you.
I
might
have
to
take
you
up
on
that,
because
I'm
not
I'll
have
to
like
check
on
what
I'm
running
at
this
point
yeah.
Sometimes
the
charges
will
just
sneak
up
on
you.
Just
I
don't
know
where
what
my
limit
is
running
at
this
point,
but
I
should
check
that
that's
important
yeah,
I
don't
have
any
more
questions.
A
Pretty
much
the
same
for
me,
the
only
the
only
thing
so
I
know
you've
been
having
additional
meetings
with
bob,
which
is
fantastic.
I'm
super
thrilled
with
that.
I
haven't
been
able
to
make
that
because
the
last
couple
weeks
have
been
crazy,
but
I
hope
to
start
being
able
to
join
so
generally.
You
all
are
meeting
on
wednesdays.
Is
that
right
or
or
whenever
during
the
week.
C
C
So
we
like
figured
out,
I
think
the
weekend
which
like
worked
for
the
both
of
us
and
I
think
the
week
earlier
too,
I
wasn't
able
to
make
it.
But
again
it's
not
like
it's
hot.
It's
like
happening
every
week,
it's
more!
If
something
that
needs
attention
and
something
that
needs
work,
we
try
and
like
he
he's
like
very
generous
in
helping
whenever
he's
able
to,
and
so
is
everyone
else.
C
But
yeah
he
is
very
generous
in
helping
with
the
release
of
the
plugin
and
again,
no
no
specific
date.
Really.
Okay,.
A
Okay,
but
yeah
just
keep
posting
them
in
slack
and
I'll,
probably
start
jumping
on,
because
I
hopefully
will
have
a
little
more
bandwidth
right
now,
but
I
just
want
to
make
sure
you're
getting
all
the
advice
and
support
that
you
need
to
from
the
mentors.
But
I
I
like
that
everyone
is
has
been
quite
attentive.
I
think
I
think,
there's
a
lot
of
interest
in
this
project,
a
lot
of
excitement.
So
I'm
glad
that
that's
you
know,
I'm
glad
that
people
are
jumping
on
quite
enthusiastically
to
to
give
you
support
and
help.
C
And
the
the
the
cloud
native
said
this
or
like
the
last
week,
the
friday.
I
think
that
was
really
really
helpful.
You
know
like
hearing
from
ratio
and
what
everything
has
been
working
wrong
and
like
in
terms
of
the
poc.
C
A
I
would
love
that
too,
because
marcia
really
has
a
lot
of
contacts
and
knowledge
in
this
area,
but
it
was.
It
was
on
the
cloud
native
meaning
because
he
he's
on
vacation
in
barcelona
this
week,
so
he's
like,
I
can't
do
it
on
monday.
I
have
to
have
to
friday
sounds
good.
So
so
that's
why
we
moved
it
to
then.
C
Mean
only
only
if
again
only
if
he
has
time,
because
you
know
asians
are
important
and
I
seriously
don't
want
to
you
know,
take
away
that
time
from
vacationing.