►
From YouTube: Octant Community Meeting - February 3rd, 2021
Description
Octant community meeting is held weekly. We discuss and talk about the current state and future of Octant, demo upcoming features and releases, and preview new ideas we are considering for Octant.
Meeting agenda: https://hackmd.io/CzaPxtmXT_SW8nEpdwvGzw?view
B
Yep
hello
and
welcome
everybody
to
the
what's
the
february
third
octant
community
meeting
feb
feb
february,
is
that
it's
about
february
yeah,
yeah,
so
different
than
january.
It
just.
B
You
see,
january
and
february
together,
it
looks
yeah
anyway.
Thank
you,
everyone
for
coming.
We,
it
looks
like
to
be
a
short
one.
Today,
mainly,
I
wanted
to
talk
about
the
one
outstanding
blocking
issue
and
for
for
the
next
release
and
then
kind
of
go
over.
What's
still
in
the
project
board,
that's
in
progress
so
I'll
just
get
started
with
the
preferences
persistence,
so
we
landed
a
new
pr
just
recently
that
pull
it
up.
So
folks
can
see
it
it's
here
somewhere,
I
could
search
for
it.
B
That
would
be
easier,
but
yeah
I'll,
just
search.
Why
am
I
doing
this
preferences?
I
spell
that
right.
I
think
so
there
we
go.
So
this
is
the
pr
we
landed.
It
adds
some
general
preferences
for
like
light
and
dark
theme
and
navigation
being
collapsed
and
expanded.
It
also
will,
by
default,
now
use
your
your
your
desktop
theme
setting
like
if
you
have
a
dark
mode
set
on
mac
or
windows,
it'll
kind
of
it'll,
infer
that
and
use
it
by
default,
so
that
got
merged
in
there
was
some
outs.
B
There
was
some
work
that
was
done
previously
when
we
were
first
looking
at
electron,
where
we
created
some
electron
settings
using
st
electron
and
the
the
that's
gonna
go
away
essentially,
and
so
we
we
opened
up
an
issue
to
do
the
persistence
for
these
various
things.
We
had
a
couple
different
methods
of
how
we
were
storing
things
and
there's
like
some
back-end
storage
for
the
original
electron
stuff,
because
it
was
all
done
and
go.
B
There
was
electron
store
which
was
added
to
I
believe
for
storing
the
well.
We
have
a
link
to
it
right
here.
I'm
pretty
sure
it's
system
traced,
yeah,
so
the
electron
store
for
system
tray
and
prompting
of
like
how
do
you
want
to
minimize?
What
do
you
want
to
happen
when
you
close
randomize
octane?
I
created
a
state.json
file
that
for
remembering
the
window
size
and
position,
you
get
the
point
we
it's
kind
of
a
little
over
the
place.
B
B
I
think
I
think
we're
going
to
end
up
using
electron
store,
since
it
was
already
introduced,
we'll
migrate,
some
this,
this
front-end
proxy
url
setting
over
and
then
we'll
also
migrate,
the
window
application
stuff
over
and
and
it'll
all
be
under
electron
store,
so
which
I
think
in
the
back
in
the
back
end
electron
stores
just
creating
a
json
file
that
it's
wrapping
as
or
maybe
it's
in.
Maybe
it's
local
storage.
But
it's
I
know
it's
a
json
file
right.
B
C
Special
wrapper
that
does
like
just
make
sure
like
the
transactions
to
the
config
file,
are
more
fault,
tolerant,.
B
B
These
two
issues
that
are
in
progress
by
me
are
windows
related
one
is
that
it
failed
to
start
on
windows,
because
we
introduced
time
stamping
to
the
log
files,
and
there
was
a
colon
in
the
name.
Windows
does
not
support
colon
and
file
names,
and
so
it
was
just
kind
of
bailing
out
there.
So
I
have
a
pr
coming
that
will
handle
a
bailout
on
the
logs
a
little
more
gracefully
because
it
was
you
would
double
click,
and
nothing
would
happen
you
just
like
you
would
get
no
you're
just
like.
B
Where
is
it
right?
And
then
you
look
in
the
system
tray
or
like
in
in
your
process
viewer,
and
there
would
just
be
instances
of
it
running
with
an
error
message
that
had
been
thrown
out
and
not
handled
so
cleaning
that
up
and
then
also
cleaning
up
the
the
octant
process
that
gets
launched
by
electron
to
fetch
data
from
the
kubernetes
api.
It
was
not
getting
properly
shut
down
under
node.js
and
doing
some
research
there.
Most
most
people
resorted
to
doing
an
exec
called
the
task,
kill
and
passing
the
pit
directly
into
there.
B
I
experimented
with
that
and
it
works,
so
these
two
will
be
fixed
today
and
then
we'll
be
getting
started
on
the
electron
storage.
The
monaco
editor
was
merged
in
just
recently
about
an
hour
ago.
So
that's
all
functioning
now,
under
all
three
environments,
so
we
are
yeah.
Release
is
eminent
at
this
point.
I
think
the
last
thing
is:
there's
some
testing
work
and
like
a
icon,
size
issue
that
needs
to
be
fixed
up
for
our
system
tray.
B
That
is
it's
actually
it
made
me
laugh
when
I
saw
it,
I
think
it's
I
don't
know.
I
just
think
it's
really
funny
how
big
the
system
tray
icon
got
on
mac,
but
milan
put
a
screenshot
in
there
and
you
can
see
it's
it's
the
octant
logo,
but
it
like
fills
to
the
entire
empty
space
of
the
system
tray.
B
So
it's
it
actually
is
the
logo,
but
I
don't
think
that
was
the
the
our
desired
result
is
not
to
fill
your
entire
system
tray
with
the
octan
logo,
even
if
I
think
it's
funny
so
yeah
that
is
that
is,
I
think
it
the
left,
4
electron
our
build
pipeline
is
in
place.
I
guess
it
would
be
good
to
cover
so
this
next
release.
B
B
There
we're
still
going
to
go,
and
and
by
default,
install
the
the
binary
the
cli
option,
but
we're
going
to
be
either
we
we
haven't,
talked
as
a
team
about
how
we
want
to
proceed
with
getting
people
over
to
the
electron,
build
and
eventually
phasing
out
the
distribution
of
the
cli
binary
in
in
any
of
our
package
management
places
and
like
in
things
like
that,
the
we
do
have
to
work
on
getting
our
mac
binary
signed
before
we
can
fully
deprecate
the
the
the
cli
that
we
ship.
B
So
that
is
something
that
we're
we're
going
to
be
putting
in
flight
right
after
we
release
0.17,
so
yeah
we'll
we'll
try
to
keep
the
as
we
get
information
on
on
what
the
plan
is
for
that
and
what
like
the
deprecation
and
migration
strategy
is
going
to
look
like
we'll,
be
sure
to
share
that
out
and
and
create
discussions
around
it
or
issues,
because
I
think
right
now,
we
still
don't
know.
B
The
goal
right
now
is
just
to
get
a
release,
tag
that
contains
the
electron
assets
and
encourage
folks
to
just
manually,
essentially
manually,
move
over,
but
likely
a
lot
of
people
will
just
continue
to
use
their
package
manager,
so
we'll
have
to
figure
out
what
what
it
means
to
change
the
behavior
there.
C
Yeah
speaking
of
package
managers,
we're
gonna
have
to
rewrite
that
brew
formula
or
start
a
cask,
whichever
one
seems
more
reasonable.
C
I
don't
have
strong
opinions,
it
might
be
a
little
jarring
to
all
of
a
sudden.
Do
brew,
update
and
have
a
different,
completely
different
application.
But
then
again
we
are
using
this
as
the
standard.
So
if
we
are
going
to
say
that
we're
going
to
abandon
brew,
then
we
we're
just
kind
of
saying
like
that.
Web
service
is
just
gone
like
we're.
Just
never
gonna
publish
on
brew
again,
which
would
be
the
alternative.
B
C
I
mean
those
are
just
conventions.
I
don't
know
off
the
top
of
my
head,
on
which
one
is,
which
I
mean
the
easiest
way
to
think
about.
It
is
just
like
it's
literally
a
another
link
that
you
asked
it's
kind
of,
like
a
mini
repository
that
you
asked
brew
to
look
up,
so
it
would
be
one
just
specifically
for
often.
B
Okay,
yeah,
that's
a
good,
I
think.
That's
just
an
area
we'll
have
to
research
more
than
and
find
out,
but
I
I
think,
yeah.
I
think
that
for
the
for
for
this
release,
this
we'll
we'll
update
the
formulas
and
and
everything
will
be
behave
as
people
have
have
had
it
behaving
for
the
previous
release
and
then
maybe
in
the
formula
itself,
can
we
spit
out?
Is
it
possible
to
spit
out
deprecation
messages
and
formulas.
B
Yeah
right
yeah
yeah,
so
I
think
I
think
that
might
be
a
good.
A
good
first
step
is
to
just
start
making
noise
in
any
of
the
package
managing
tools
that
say
like
like
upcoming
versions
of
octant
or
like
the
cli
version.
I
don't
we'll
have
to
come
up
with
language
around
it,
but
some
some
way
to
probably
like
make
a
blog
post
update
the
formulas
and
like
talk
about
what
it
like
when
people
could
expect
that
to
change
like
for
odd
18
or
probably
odd,
19
or
whatever.
B
C
B
C
Yeah
or
other
platforms
like
windows,
or
what's
the
other
one,
the
other
hipster,
not
not
it's
hot-
on
it's
on
our
feed
me
it's.
It's
called,
not
the
cask.
It's
scoop,
yeah
scoop.
Those
are
there's
no
alternative
right.
So
if
we
move
over,
it's
literally
just
pointing
to
the
github
artifact
okay,
so
those
are
easier
to
do.
But
still
I
don't
know
if
you
can
do
deprecation
warnings
on
those,
though
those
those
might
be
a
little
bit
different.
Okay,.
B
We
might
maybe
yeah,
I
wonder
if
you
can
yeah
we'll
have
to
we'll
have
to
research
it
I
think,
oh
like
ideally,
I
would
like
it
to
be
something
where
you
could
either
have
a
warning
in
place,
and
then
we
have
two
which
is
like
scoop,
install
octant
with
a
big
warning
that
says
this
is
going
away,
use
scoop,
install
octan,
dash,
desktop
or
something
like
that.
Instead
right,
like
here's,
the
alternative
one
and
then
eventually
scoop
install
octet
goes
away
and
then
gets
replaced.
B
So
so
we
would
end
up
with
two,
but
they
would
be
mirrors
of
each
other
like
that
would
be
a
way
to
still
have
scoop,
install
octant
and
like
that
anyway.
That's
just
one
migration
strategy
I
can
think
of
is
like
just
having
a
different
name.
While
we
yeah,
while
we
defecate
and
migrate.
B
Release,
I
think,
if
I
think
it's
worth
looking
at
for
0.17
just
to
see
if
there's
like
right
like
what
at
least
at
least
investigate
taking
some
time
after
we
publish
the
release
on
github,
because
normally
there's
like
a
a
bit
like
a
day
of
like
us,
going
like
we
publish
and
then
we
go
and
we
up
like.
We
make
sure
it's
good
and
then
we
go
and
update
all
the
package
managers
and
I
think,
in
that
process
of
kind
of
letting
like
in
in
the
process
of
going
to
update
package
managers.
B
We
can
do
like
a
what
is
the
the
work
involved
to
like
do
this?
And
if
it's
relatively,
like
some
of
these
I've
investigated
at
zero
percent.
So
some
of
these
might
even
have
deprecation
and
migration
strategies
in
their
docs
right,
like
here's.
How?
If
you're
replacing
your
thing
with
a
new
thing,
here's
how
we
recommend
doing
it
on
chocolaty
or
with
homebrew
or
whatever
like.
I
haven't,
even
looked
into
it.
B
So
I
doubt
that's
the
case,
but
I
think
it's
worth
investigating
and
then
we
can
take
it
from
there
and
and
if
we
don't
start
it
for
oh
17,
we
would
start
it
in
oh
18..
B
B
So
yeah,
so
that's
that's
kind
of
the
status
of
of
electron
right
now,
and
so
it's
so
it's
it's
eminent
as
mentioned,
and
we
are
I'll
put
this
project
board
right
into
the
right
into
here.
So
people
can
can
see
it.
A
Yes,
I
I
put
that
in
I
noticed
there
is
only
one
place
where
o
is
small
caps
in
in
the
menu,
and
I
was
wondering
what
is
the
reason
behind
that.
B
I
don't
know
I
I
don't
even
know
where
it
is
you're
talking
about
so
yeah,
so.
A
If
you,
if
you
study,
electron
app
at
least
on
mac,
the
the
like
main
window
has
like
a
menu
at
the
top,
and
the
octane
is
first
item
on
the
left
on
top
left
and
that
that
is
smoke.
Spelled
by
this
small
l.
B
A
A
B
A
B
A
So
yeah
zoom
is
small
letters
too,
but
slack
is
capital
letters.
Okay,
there
you
go.
B
Say
that
it's
okay,
we,
I
open
an
issue
for
it.
It
won't
be
a
blocking
issue,
but
it's
something
that
we
can.
We
can
look
at
yeah,
okay,.
A
Absolutely
not
no,
I
was
just
curious.
Where
is
it
coming
from?
It
seems
that
it
should
be
capitalized,
but
probably.
C
B
All
right
well
that
I
think
that
covers
it
for
this
one
I
know.
Last
last
time
we
talked
about
kind
of
what
what
was
coming
in
the
future,
so
I
don't
want
to
do
that
again
in
this
meeting,
we'll
probably
do
it
after
the
release
so
for
the
next
meeting,
so
any
other
open
q,
a
questions
or
anything.
Anyone
else
wanted
to
share
before
we
before
we
call
it.
B
C
I'm
I'm
currently
working
on
our
test
pipeline
for
the
electron,
build
I've
gotten
karma
to
work
with
our
component
library.
So,
instead
of
using
the
chrome
driver,
you
could
just
spin
all
of
the
components
up
in
electron,
which
is
the
first
piece
and
then
the
second
piece
is
going
to
be
using
spectron
to
smoke
test,
because
you
actually
can't
run
any
of
the
code
in
main
using
karma
because
they
use
node.
They
import
node
modules
right.
C
C
Let
you
the
test,
runner
will
just
fail
in
various
ways,
and
you
will
be
sad,
so
I
moved
over
to
spectron,
which
in
turn
made
me
make
some
other
decisions
that
I
won't
go
to
now,
but
I'm
basically
using
mocha
for
the
spectron
as
the
alongside
the
spectrum
as
the
test
runner
and
then
that's
going
to
be
used
as
a
smoke
test
to
check
that
we're
actually
creating
windows
so
like
an
electron
window
and
we're
actually
tearing
them
down.
There's
currently
some
issues
with
a
spec
john
starting
at
the
opted
sub
process.
C
So
that's
actually
blocking
on
this
end,
I
could
combine
it
with
a
system
tray
menu
or
not.
I
think
it's
just
going
to
be
the
test
component
to
the
system.
Tray
have
so
I've
so
far
just
been
adding
that
same
level
of
work
here,
other
things
that
we
haven't,
or
at
least
a
it's,
a
like
a
three
line
fix
but
like
something
you
might
notice
is.
C
If
you
try
to
open
a
new
link
in
the
electron
application,
it
opens
as
a
new
electron
window,
whereas
we
wanted
to
open
it
as
part
of
the
default
browser,
and
so
you
just
have
to
capture
the
window
event
and
do
like
a
shell
open
type
thing
instead
of
open
url,
instead
of
letting
electron
do
whatever
it
wants
by
default.
B
We'll
have
to
target
for
every
url,
like
what
I
mean
is
in
the
case
of
like
because
internally
we're
using
links
to
like
open
a
deployment
from
a
table,
for
example,
will
we
will
it
just
know
that
it's
external
by
default,
or
we
have
to
be
like
anywhere?
It
is
external,
apply.
This.
C
Yeah,
it
knows
it's
external
right
so
and
also
like,
if
you
kind
of
think
about
it
right,
like
octant,
is
really
just
a
single
page.
Application
like
it's
not
like
the
url
is
changing
in
the
browser,
but
it's
not
like
actually
like
flipping
through
a
different
page,
and
I
think
that's
at
least
my
that's
my
theory
on
what's
happening
versus
something
like
say,
port
forwarding.
If
you
click
something,
that's
local,
it's
too
different
for
it.
C
It
will
just
take
you
somewhere
else
and
presumably
for
something
like
say
jenkins
x,
where
it
might
link
them
back
to
whatever
pipeline
is
running
on
whatever
their
service.
The
expectation
there
is
to
just
throw
them
in
the
browser
instead
of
showing
up
in
often
there's
also
just
a
ton
of
like
really
annoying
side.
C
Things
like
the
I
think,
when
you
ask
for
like
a
prompt
when
you're
closing
right
but
like
that's
really
annoying
in
a
testing
environment,
so
I
kind
of
have
to
like
start
coordinating
like
enablement
and
disablement
of
certain
features
in
the
test
environment.
So
there's
like
a
lot,
that's
happening
implicitly.
That
will
happen
in
due
time.
B
Yeah,
that
makes
sense
and
just
to
show
for
those
who
haven't
seen.
Let's
see,
I
think
I
can
show
kind
of
what
what
sam
was
talking
about
here.
B
I
share
my
whole
screen
and
and
then
I
I
started
a
port
forward
now,
if
I
click
this,
it
pops
up
in
this
little
embedded
electron
window
instead
of
in
the
in
the
browser,
so
that
that's
what
that's,
what
sam
is
referring
to.
B
Also
yeah
things
like
prompts
are
annoying
I
for
testing
purposes.
I
agree
so
I
think
there's
a
way.
I
hope
there's
a
way
we
can
like
isolate
it,
so
that
it's
I
don't
know,
maybe
maybe
we
can.
Maybe
we
can
think
about
a
little
offline,
just
like
how
we
might
isolate
that
specific
behavior
so
that
it's
not
doesn't
have
to
be
factored
as
part
of
like
normal
test.
B
B
All
right,
I
think,
that's
it
so
with
that,
unless
anyone
has
any
final
things.
B
We'll
we'll
call
it
early.