►
From YouTube: 2021-06-24 meeting
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).
A
D
E
C
E
B
Okay,
so
let's
just
start
before
anyone
more
joins.
B
Okay,
okay,
so
last
meeting
actions:
let's
see
packages
to
registry,
the
changes
already
merged,
so
we
should
already
appear
there
yeah
the
batch
for
the
code
coverage.
I
have
not
done
it.
Sorry,
I
I
totally
forgot
about
it.
Then
I
have
been
a
bit
full
of
work
and
couldn't
review
it.
D
It's
been,
it's
been
a
long
journey
on
that
one
still
not
still
not
accepted
yet
I
haven't
checked
it
this
morning,
but
there's
still
some
well.
Actually
I
don't
think
there's
anything
at
this
point,
but
yeah
we'll
see.
I
think
it's
just
waiting.
B
Okay,
so
we
can
keep
it
here.
Yes,
for
remembering,
I
think
I
wait
in
network
instrumentation.
I
created
the
issue
just
to
track
it.
I
did
it
today.
I
must
say:
okay,
doxy
usage
for
documentation.
You
created
an
issue
already.
I
think.
B
Recent
metrics
fixes
it
was
merged
and
yeah,
and
also
the
year
pc
tickets
are
created.
So
that's
all
from
the
last
meeting
actions
for
today
we
have
one
one
topic.
I
think
that
there
is
appear
for
a
headers
environment,
so
it
was
from
rice.
So
if
you
want
to
explain
better
about
this.
D
This
one
yeah
sure
so
for
elastic
our
apm
servers.
The
the
thing
that
hosts
hosts
the
open,
telemetry
collector
is
generally
it's
protected
through
authentication
and
they
use
like
a
token
authentication.
But
there's
no
way
to
configure
our
exporters
to
send
authentication
through
the
metadata
in
the
grpc.
D
Provide
a
means
to
configure
the
grpc
headers
via
the
open,
telemetry
environmental
variable
spec,
but
the
problem
is,
I
just
realized
is
that
I
don't
think
environmental
variables
on
mobile
will
transmit
across
all
builds,
so
you
can
run
it
locally
in
your
test
builds.
But
if
you
create
a
archive
build
that
in
those
environmental
variables
you
set
won't
get
passed
on
unless
there's
a
means
that
I
know.
B
D
D
So
I
think
yeah
we
need
to
modify
the
spec
a
little
bit
or
just
interpret
it
a
little
bit
differently
and
maybe
use
like
a
p
list
or
something
to
configure
these
things.
I
don't
know
what
you
think
would
be
best
nacho
for
that.
B
Yeah
I
I
have,
I
have
read
it
and
I
have
been
thinking
a
bit
about
it.
There
is
one
way
you
could
set
environment
variables
that
it's
with
the
set
them
c
function.
B
They
set
them
and
get
them
can
modify
environment
variables
of
a
running
application.
Yeah.
B
If
you
are,
if
you
have
there,
your
ap
keys,
api
keys
or
your
tokens
or
whatever
you
can
have
that
in
code
and
set
that
in
memory
without
a
p
list
existing
but
yeah,
we
can
also
pars
the
main
application
bundle
list
and
search
there
for
the
environment
variables,
so
you
distribute,
but
so
the
user
should
set
the
list
of
the
app
running
your
elastic
apm
software
set
the
environments
there
and
yeah
and
and
reading
from
from
yeah
we
we
should
support
reading
from
the
main
application
list,
bundle
also
so
yeah.
B
I
think
I
think
it's
a
a
good
idea
to
support
both
so
probably
maybe
supporting
first
reading
the
p
list,
so
it
can
also
be
used
on
mac
apps
and
after
that,
try
to
read
environment
variables,
okay
and
give
precedence
to
the
environment
variables.
So
in
case
you
are
running
a
mockup
without
finished,
but
you
want
to
run
in
a
different
environment.
B
You
can
change
your
local
environment
and
make
it
work
differently.
I
think
that
the
more
flexible
way.
D
D
Yeah,
I
think
that
I
think
that's
that's
fine.
My
only
concern
is
just
how
secure
putting
like
a
you
know
a
an
auth
token
into
a
p
list
on
a
on
a
mobile
phase.
B
That's
that's
yeah
that
that's
I
mean
I
mean
that's
an
issue,
but
the
user
of
the
app
yeah,
that's
yeah.
I
don't
know
in
theory,
you
shouldn't
be
providing
something
that
that
couldn't
be
somehow
seen.
I
mean
I
don't
know
how
you
are
sending
that
information,
but
is
it
done
in
a
network
request
yeah.
B
B
D
B
Yeah,
that's
that's
the
point
I
mean
it's.
You
shouldn't
use
keys
for
s,
you
know
for
sending
things
or
things
like
that,
but
that
token
is
something
that
it's
probably
already
in
your
network
request
as
a
url
parameter
or
as
a
header.
B
So
having
that
on
a
p
list
or
not,
I
don't
think
it's
a
problem
right.
They
will
transfer,
they
will
try.
First,
with
with
the
headers.
B
Url,
if
they
want
to
take.
D
B
All
right
so
yeah,
but
the
other.
The
other
option
is
using
set
them
and
instead
of
using
the
p
list,
and
if
you
use
cdm,
it's
done
just
in
memory
use.
What.
D
B
E
B
B
You
are
not
publishing
it,
but
probably
will
be
also
in
the
in
the
network.
B
But
yeah,
I
I
think,
using
p
list,
as
as
the
first
option,
giving
the
possibility
to
modify
it
with
an
n
bar.
It's
the
the
best
solution.
C
Okay
sounds
good,
so
so,
if
you
use
a
set
env,
how
do
you
you
know?
How
is
the
api
key
going
to
be
on
the
device
in
the
environment
of
the
device?
Could
you.
C
How,
how
is
the
key
in
gonna
be
the
environment
of
the
device?
You
know,
because
every
device
will
have
access
to
that
key
right
to
be.
D
Oh
yeah,
it's
not
going
to
be
a
unique
device.
It's
not
going
to
be
a
unique
device.
It's
just
a
general
token.
I
guess
like
it.
It
provides
like
some
means
of
reducing
the
number
of
possible
connections
to
those
who
have
access
to
the
actual
device
itself,
but
you
know
it'd
be
pretty
it's
pretty
easy
to
to.
You
know,
share.
D
It
yeah
at
the
end
of
the
day,
the
goal
is
to
provide
a
keyless
access
to
the
to
the
collector,
with
rate
limiting
on
that
end.
So
it's
not
like
the
yeah.
The
the
issue
of
security
on
mobile
is
obvious,
so
this
is
more
of
a
stop
gap,
just
in
just
in
term
or
just
in
case
like
we're
not
able
to
get
the
the
keyless
stuff
set
up
prior
to
when
we
release
our
agent.
So.
C
Yeah,
I'm
looking
at
I'm
looking
at
the
data
dog
sample
that
you
have
exporter.
That
also
has
a
client
token
an
api
key
right.
How
do
you.
B
B
Yeah
the
sample
that
is,
with
the
empty
key
yeah
yeah,
how
how
I
am
using
that
yeah
I
am
yeah.
I
am
not
sharing
that.
I
mean
it's
like
it's
in
it's
set
in
a
framework.
The
usage
I
am
doing
is
for
is
testing
instrumentation,
so
I
distribute
in
a
framework
that
links
with
open
telemetry
and
sets
internally
the
key
there.
Okay,
okay.
B
I
I
am
writing
it
from
outside
and
setting
there,
because
I
need
those
keys,
as
I
imagine
bryce
needs,
but
I
pass
it
in
the
configuration
and
the
way
I
read.
It
is
not
because
I
am
not
using
the
tlp
exporter,
so
I
don't
need
to
set
those
keys
on
the
exporter
before
generating
the
calls.
That
is
what
price
needs.
B
I
am
just
setting
them
and
I'm
doing
the
just
connecting
with
my
backend
from
that
from
the
exported
code,
using
the
keys
that
come
from
from
yeah.
C
So
question
is:
how
does
how
does
this
thing?
Do
you
that
other
framework
does
it
also
store
it,
get
it
off
the
device
or
how?
How
does
it
is
it
stored.
B
B
Yeah,
but
currently
my
usage
is
for
developers,
so
it's
it's
okay
for
developers,
so
developers
set
the
environment
variables
inside
xcode
because
they
are
going
to
run
tests
with
xcode.
B
That's
the
point
of
my
so
I
don't
have
that
need
currently:
okay,
okay,
but
in
the
past
I
did
something
also
with
tokens
and
keys
and
started
in
in
the
p
list
of
the
application
yeah.
So
I
think
it's
a
good
place
to
set
that
if
you
are
distributing
or
the
user
can
change
that
value.
B
So
if
you
are
asking
your
user
to
set
their
key,
they
should
put
it
in
a
field
list
yeah.
I
think
so.
B
B
D
D
Yeah,
that's
a
that's
a
good
point
yeah!
Well.
Originally
I
wanted
just
to
expose
those
the
the
option.
I
can't
remember
what
the
name
of
that
object
was,
but
the
optional
like
info
on
the
exporter
object
yeah,
but
I
was
trying
to.
I
was
trying
to
keep
it
in
spec
with
open
telemetry.
So
that's
why
I
went
down
that.
B
Yeah,
I
don't
know
yeah
using
embarrass
or
plist
should
be
the
way
for
for
your
tokens,
but
I
don't
know
if
happy
list
is
the
way
for
configuration
of
open
telemetry.
B
I
mean
it
can
be
done,
but
it
sounds
a
bit
I
don't
know
convoluted
or
yeah.
So.
B
B
Because
you
released
dynamically
from
abandoned,
so
I
don't
know
maybe
reading
for
the
bundle
that
has
some
class
configuration
class
or
something
like
that,
because
you
can
read
the
main
bundle
you
can.
Your
current
bundle
but
open
telemetry
is
going
to
be
in
a
third
bundle.
That
is
not
going
to
be
your
the
configuration
or
the
main
bundle
that
will
be
the
user
application
bundle,
yeah.
D
B
In
I,
in
the
bundle
that
you
you
will
be
linking
up
in
telemetry
and
providing
to
the
user,
probably
you
should
set
the
bundle
to
the
otlp
exporter,
the
name
of
the
bundle
that
you
are
going
to
use
in
the
otlp
exporter
as
the
band
that
will
provide
the
list
right.
E
B
So
as
part
of
the
configuration
somehow
setting
an
optional
bundle,
so
you
can
say
the
configuration
is
in
this
bundle.
So
read
the
police
from
there
yeah.
E
B
B
I
mean
you
can
usually
find
settings
that
you
could
pass
in
the
project
somehow
also
instead
of
p-list,
but
that
will
be
a
similar
problem.
I
think
yeah,
I
think
that's
even
more
difficult
for
the
user.
D
There's
no
there's
no
configuration
structure
available
yet
is
there
we
haven't
added
anything
like
that
in
the
swift
sdk.
B
Do
we
have
configuration
for
some
exporters?
Okay,
so
this
is
a
kind
of
exporter,
so
maybe
you
can
provide
a
configuration.
D
B
B
Yeah
because
I
think
it's
something
that
should
be
private,
I
mean
it
should
be
private
from
your
users
of
you,
your
library,
yeah.
D
B
B
That
you
need
for
your
keys
or
something
like
that,
and
maybe
some
of
them
must
be
read
from
the
user
p
list
if
they
use
a
different
token
for
connecting.
So
they
said
that
token
there
you
read
that
token
from
the
main
plist
but
configure
otlp
exporter
with
your
that
key
and
other
tokens.
Maybe
that's
the
cleanest
way.
D
C
B
So
maybe
for
yeah,
something
like
that
because
yeah
it's
but
yeah-
and
I
I
am
using
internally
that
exporter
with
that
configuration,
but
I
configure
it
myself
for
another,
but
I
only
expose
I
mean
if
it's
a
developer
and
uses
the
exporter
from
open,
telemetry
yeah,
it
must
configure
it
all.
But
what
I
provide
to
the
of
my
product
is
just
only
an
api
and
I
feel
the
configuration
in
another
intermediate
framework
that
it's
more
or
less
what
I
think
bryce
wants.
D
D
D
And
then
yeah
and
we
can
extend
it
with
the
other
various
you
know
configuration
settings
that
otil
that
they
define
in
the
hotel,
spec.
B
B
Currently,
it's
a
bit
messed
up.
I
mean
you,
you
must
know
about
sweet
package
manager
in
order
to
properly
set
your
dependencies
for
it
to
link
and
work.
So
you
know
that
you
must
use,
for
example,
static
libraries
when
you
are
incorporating
all
of
them,
because
if
you
use
dynamic,
libraries,
probabilities
and
you
are
using
several
components,
it
will
say
that
it
doesn't.
C
Use
because
it
has
duplicated
things
right
right
and-
and
I
was
going
to
ask
you
that
you
know
I
was
trying
to
use
it.
You
know
with
a
swift,
ui
app
and
if
I
use
the
dynamic
version
of
the
library
it
doesn't
like
it,
I
have
to
use
a
static.
B
B
B
So
I
was
thinking
about
exporting,
for
example,
something
that
just
say
open
telemetry
as
a
module
that
internally
has
the
dependencies
of
all
the
modules
inside
the
package,
for
example.
B
So
you
can
just
import
that
library
and
you
have
all
the
exporters
and
you
have
all
the
instrumentation
and
you
just
have
to
call
it
instead
of
having
to
know
if
I
have
to
import
this
library,
this
other
library
or
that
order,
I
don't
know
what
do
you
think
about
that,
and
also
that
that's
one
of
the
things
and
the
other
that
is
one
step
more,
is
having
a
binary
package
of
open
telemetry.
So
users
don't
have
to
compile
every
single
code.
Every
time
they
yeah.
D
B
They
build
that
project.
I
don't
know
what
you
think
about
the
having
a
single
dependency
thing.
That's
the
first
topic
and
the
second
is.
C
B
Project
page
directly,
and
then
it
shows
all
the
possible
targets
or
libraries
that
you
can
link
you.
B
Yeah,
that's
right
and
you
have
to
select
the
static
ones.
If
you
are
selecting
more
than
one
or
it
will
pay
necessarily,
I
mean
yeah.
So,
for
example,
if
you
are
writing
an
exporter,
you
can
import
just
one
of
those
libraries,
but
the
user
of
your
exporter
should
include
statically
the
sdk
and
your
exporter,
for
example,
or
will
have
duplicated
things.
So
I
was
thinking
that
for
a
final
user,
maybe
having
a
single,
open,
telemetry,
binary
distribution
that
has
dependencies
of
all
the
projects
could
work
well.
D
B
D
Think
that's
excellent.
I'm
I
thought
that
the
hip
thing
was
just
to
import
packages
these
days.
So
I
thought
that
you
know
single
dependency.
Binary
packages
were
a
thing
of
the
past,
but
yeah.
If
that's,
if
you
think,
that's
yeah,
I
think
it's
a
good
idea.
I
like
it.
B
Okay,
yeah,
it
simplifies
for
the
for
the
users
that
are
not
so
you
know,
don't
have
so
much
experience
with
the
tool
or
with
the
project.
Yeah
users
are
used
to
cocoapods,
for
example,
that
just
import
what
they
need
and
simply
works
and
swift
package
manager
is
a
bit
more
difficult
to
use.
When
you
have
several
things
and
to
understand
why
it
does
that,
because
you
think
if
it's
dynamic,
that's
great,
because
everything
is
dynamic
and
everything
will
leak,
no
right.
A
B
So
I
think
it
can
be.
It
won't
be
worse
than
what
it
has
now.
The
the
other
thing
is
that
you
can.
That
that's
another
point
is
that
you
can
have
a
binary
package
with
sweet
package
managers,
insects
code,
12
that
you
distribute
an
xc
framework
in
your
package,
so
the
user
of
the
library
doesn't
have
to
download
everything
and
compile
everything
every
time
it
uses
it.
B
It
only
needs
to
link
that
library
that
should
be
binary
compatible
with
newer
and
all
versions
and
just
downloads
a
binary
instead
of
all
your
dependencies
and
all
the
things
that
it
depends
and
link
with
that.
But
I
it's
not
easy
to
set.
If
you
are
configuring
versions,
because
right
now
we
have
we
are
distributing.
We
are
just
marking
a
release
with
attack
and
that's
all
we
need
to
do.
B
But
if
you
have
a
binary
distribution,
you
have
to
or
have
the
binary
in
in
your
repository,
or
you
have
to
have
another
repository
that
just
that
just
has
a
reference
to
a
binary
that
must
be
stored
somewhere.
So
if
you
have
in
your
own
repository,
you
cannot
have
the
tag
in
the
binary.
B
We
don't
have
a
way
to
build
that
binary,
that
binary
before
the
task
is
created,
except
if
we
build
that
every
time
we
have
a
push
and
if
you
create
a
release
before
a
push
is
finished,
it
will
be
touched
before
the
binary
is
created.
So
we
we
couldn't.
B
I
have
not.
I
have
been
thinking
that
also
for
another
project,
but
I
I
there
is
no
way
to
I
mean
in
the
cicd
to
build
your
ta
with
the
framework
and
set
it
inside
the
repo
before
the
community
is
created.
I
mean
before
the
task
or
the
reach
release
is
created
because
you
are
modifying
the
repo
after
so
yeah.
A
B
So
it
it's
more
thought
for
linking
with
external
binary
libraries
than
for
providing
your
own
binary
framework.
I
don't
know
if
I
explain
it.
C
C
So
if
you
know
any
app
that
is
going
to
use
this
has
to
make
it
you
know
as
to
statically
build
it.
B
Yeah,
the
point
is
that
when
you
have
a
dependency,
a
big
dependencies
have
to
download
of
the
library
so,
for
example,
currently
a
user
that
links
with
open
telemetry
street
will
have
to
download
the
three
library
just
because
the
jagger
exporter
uses
script
for
that.
So,
even
if
you
don't
want
to
use
jagger
exporter
once
you
include
the
the
project
in
your
the
or
the
espn
package
in
your
project
that
uses
open
telemetry,
it
will
download
the
threat
library.
C
Distribute
a
binary
so
is
it
is.
Is
it
more
like
optimizing
on
the
during
the
run
time,
like
you
know,
when
you're,
when
you
have
okay,
no,
not
on
runtime
yeah,
just
for
building
right
now?
So
if
you
have,
if
you
have
three
apps
on
on
my
device
using
open
telemetry
and
all
of
them
are
going
to
be
statically
built
with
the
open
telemetry.
Where
is
the
dynamic
aspect?
B
Yeah
in
the
iphone
app
you,
you
cannot
see
other
apps
ex,
except
for
the
system,
libraries.
So
you,
the
concept
of
dynamic
library,
for
the
system,
is
only
for
the
system.
You
cannot,
you
can
serve
it
in
apps
if
you
are
the
same
developer
and
blah
blah
blah
blah,
but
only
messages
and
things
like
that,
not
libraries
or
code,
but
it
can
be
useful
in.
B
In
a
mac
application,
for
example-
but
you
if
you
had
third
party
linker
or
things
like
that,
but
usually
dynamic
libraries
are,
if
you
do
that
on
a
mac,
you
will
probably
only
load
one
of
them
if
they
are
the
same
person,
but
it
you
would
save
on
on
mac
only.
B
But
it's
more
about
not
having
to
build
all
the
code.
Every
time
that
that
that's
the
that
was
my
point,
but
maybe
it's
not
so
important.
So
maybe
it
can
be
done.
For
example,
when
bryce
distributes
his
library
to
a
third
party
just
to
have
their
binary
there,
instead
of
having
to
distribute
it
with
all
the
dependencies
and
all
the
open,
telemetry
things
I
I
think
so
it
was
an
idea,
the
good
way
for
having
a
binary
package.
B
You
will
have
to
have
another
repository
just
with
the
swift
package.
That
includes
a
your
binary
that
you
generate
in
the
other
in
the
other
project,
and
it
will
have
to
be
probably
modified
before
the
after
the
the
the
framework
is
really
built,
or
something
like
that,
so
would
mean
having
a
different
repo
for
distributing,
because
you
cannot
do
that
with
your
own.
D
So
I'm
having
difficulty
tracking
having
a
single
exported,
exported,
binary
or
multiple
exported
binaries
would
be
yeah.
B
Yeah
having
no
in
the
same
way,
we
have
a
single
dependency
that
we
have
of
the
libraries
is
distributing
that,
instead
of
in
source
code
right
now
will
be
a
source
code.
I
mean
it.
Will
half
of
the
dependencies
will
download
all
the
dependencies
will
build
all
and
generate
the
binary
when
you
build
the
project
that
uses
open,
telemetry
or
the
other
way
is
having
a
binary
that
has
that
dependency
compiled
already.
So
when
you
import
open
telemetry,
it
just
takes
that
compiled
framework
in
your
project
and
links
that
yeah.
D
Yeah,
it's
it's
a
weird
one
because,
like
we,
the
open
telemetry
project
does
have
a
lot
of
other
other
third-party
dependencies
like
all
the
grpc
stuff,
and
I'm
wondering
what
what
happens
when
yeah
it
just
it
really
sucks
that
it's
all
it
all
has
to
be
static,
but
I
think
I
think,
just
having
a
package
all
as
one
x,
one
binary
is,
is
very
convenient.
So
that's
the
that's
the
trade-off
and
I
think
it's
worthwhile.
I
mean
at
least
I
think
some
developers
will
find
it
worthwhile.
B
The
problem
is
that
you
cannot,
I
I
didn't
find
a
way
to
do
that
with
a
single
I
mean
if
we
could
distribute
the
binary
with
our
project
when
that
will
be
great,
it
will
be
another
option
more.
So
you
select
that
if
you
prefer
just
to
have
the
binary
yeah,
but
the
problem
is
that
you
cannot
do
that
right.
Currently,
because
the
I
mean
the
package
must
include.
B
D
Yeah
is
this:
do
you
think
the
problem
is
we
need
a
somewhere
to
put
the
binary
like,
like
you're
you're,
considering
putting
it
in
another
repo,
but
is
there
like
some
sort
of
some
sort
of
like
storage
area
that
we
could
put
it
like
s3
or
something
like
I'm
wondering
what
we.
B
A
B
B
To
have
a
section,
okay
right
right
or
you
can
have
your
binary
in
a
local
path
inside
your
project,
but
in
any
case,
in
any
case,
when
you
create
a
release
version-
and
you
talk-
you
are
setting
already
this
file.
B
Because
you
know
what
I
mean
yeah,
it's
a
like
a
continuous
integration
or
continuous
development,
ci
cd
problem.
I
want
to
generate
attack
of
something
that
I
still
have
not
built.
So
I
don't
know
when
to
make
the
so
currently
you
have
when
you
have
a
release,
you
create
a
build
and
whatever,
but
in
the
same
time
you
have
to
set
it
or
both
the
section
or
the
path
or
or
the
files
inside
the
project
already
there.
B
B
D
D
Let's,
because
we're
gonna
like
let's
say
we're:
gonna
cut
the
main
branch
as
the
release
it'll
make
the
main
branch
build
it
all
it'll
tag,
it'll
tag,
the
release
with
the
version
that
it
creates
the
package
and
then
it'll
create
a
a
release,
branch
of
that
release
version.
D
Let's
say
it's
like
1.3
and
then
in
that
same
github
action,
it'll,
add
this
new
package
to
the
release
branch,
it'll,
update
the
package
binary
or
does
the
the
the
the
the
swift,
the
spm
like
package
info
and
then
commit
it
all
at
once?
I
don't
know
if
that
is
viable.
B
Do
you
mean
like,
for
example,
now
create
a
release
and
instead
of
saying
1.0.03
say
something
more
here
like
prep,
something
like
that
and
when
the
action
runs,
it
sees
that
the
name
has
a
breath
and
builds
the
real
1.033
with
all
the
information
here.
D
Maybe
something
like
that,
the
problem,
I'm
not
that
familiar
with
github
actions-
I
guess,
is
the
problem
because
I
would
say
like
we
would
want
to
trigger
this
action
by
like
creating
a
release,
branch
or
something,
and
then
it
automatically
builds
it
from
main
or
whatever
and
then
inserts
the
the
necessary
things
during
the
build
like
it'll
build.
It
first
grab
that
binary
that'll
be
like
the
released
binary.
D
You
know
and
tag
it
in
in
this
github
action
as
it's
running
and
then
create
the
rest
of
the
like
the
the
the
package
info
along
with
it
after
it's
built
but
yeah.
I
don't
know.
B
C
B
B
Yeah,
that's
exactly
because
the
way
they
are
setting
the
configuration
is
that
yeah,
it's
nice.
If
you
have
a
third-party
framework
that
you
want
to
depend
on,
so
you
just
download
it
and
link
with
your
with
the
rest
of
your
project
or
if
you
have
a
different
repository,
just
to
distribute
your
project.
What.
B
B
D
I
think
oh
so
I
vaguely
recall
that
the
checksum
can
be
left
blank
and
then
it'll
like
auto
populate
at
some
point
is
what
am
I
thinking
of.
I
feel
like
I've
fiddled
with
this
before
and
there's
like
some
there's
some
caveat
about
the
checksum
that
you
can
you
can
you
can
kind
of
get
away
with
it
not
being
set
when
you
build.
B
D
A
D
Yeah
so
yeah,
it's
maybe
the
maybe.
This
is
like
a
separate,
a
separate
swift
package
or.
B
So
you
can
do
that
without
another
repository
where
you
store
your
pipe,
but
not
with
your
own
project.
Yeah.
B
B
But
yes,
I
think
I
can
start
with
having
a
single
dependency
with
all
things
there,
so
it
can
be
used
from
anyone
easily
and
we
can
go
with
the
binary
distribution
as
a
next
step.
D
D
Yeah,
so
you
might,
you
might
be
able
to
before
you
before
you
as
a
target,
so
you
might
be
able
to
locally
build
your
framework,
your
xc
framework
and
then
get
the
checksum
out
of
it.
What
it
creates
if
you're
done
making
code
changes,
because
the
checksum
is
just
based
on
the
code,
not
the
package,
the
not
the
swift
package.
B
Yeah
that
that
yeah
that's
an
option,
but
it's
like
what
happens
if
I
forget
building
that
before
creating
the
release
or
yeah
yeah
that
that's
my
main
problem
is
yeah.
D
I
mean
I
mean.
Maybe
we
could
create
a
github
action
that
just
that
that,
as
a
pre-process
of
the
release,
it'll
it'll
build
the
build
the
artifact
capture,
the
checksum
inject
it
in
there
and
then.
B
But
with
I
think,
it's
a
problem
with
any
other
ci
cd.
Can
you
do
something
before
release
is
created
or
attack
is
created
in
it?
No
because
it
usually
sends
you
a
message
after
the
thing
has
been
done
and
not
before.
B
C
So
how
are
the
other
libraries
you
know
like
released.
B
If
they
do
that,
but
it's
like
telling
the
user
you
have
this
repository.
If
you
want
your
source
code-
and
you
have
this
other
repository,
if
you
want
to
use
directly
the
exit
framework.
D
D
D
Okay,
just
one
last
thing
before
we
wrap
up
if
y'all
could
take
a
look
at
that
mobile
carrier
info
pr
and
just
add,
you
know
your
thoughts
there.
There
are
a
couple
of
different
conversations
going
on
in
there
about
carrier
names
and
actually
mostly
it's
around
cell
radio
technology
and
how
to
categorize
them
or
if
we
wanna
use
them
and
there's
there's
some
confusion.
I
think
so.
D
Maybe
some
additional
clarification
for
for
people
can
could
you
know
from
from
another
source
besides
me,
but
yeah.
B
B
D
B
Yeah,
I
will
try
to
at
least
try
to
approve
it
or
something
yeah.
Okay,.