►
From YouTube: 2023 02 21 Jenkins Infra 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
A
A
Yes,
the
battery
is
high
quality.
That's
really
cool,
okay,
weekly,
two
thousand
2.3
92,
so
the
packages
bits
are
ready
on
jenkins.io,
but
the
docker
container
image
is
fading.
Due
to
an
error.
Let
me
check
because
I
just
opened
the
the
raw
right,
yeah
jenkinsco
released.
That's
the
issue.
3
400.
A
Let
me
add:
the
reference
racked
in
so
I
will
explain
that,
but
we
have
an
issue
tracking
the
raw
and
that
should
be
fixed
later
today,
but
expect
a
delay
one
or
two
hours
before
the
general
availability
of
the
docker
image.
Time
for
us
to
fix
the
infrastructure
associated.
A
C
A
Okay,
cool
is
it
signed
with
the
new
or
the
old
certificate.
A
I
won't
be
on
the
office
next
Tuesday,
so
we'll
need
someone
else
to
run
the
weekly
meeting.
They
found
their
volunteer
here.
B
A
A
I
will
be
available,
Tuesday,
Morning,
I've
canceled,
my
travel
to
Leon,
but
I
will
be
I
will
try
to
do
it
remotely
because
I
will
have
to
stay
at
home,
but
I'm
only
unavailable
the
Tuesday
afternoon.
So
in
the
morning
I
will
triple
check
with
a
with
a
Stefan
aderve.
So
we
can.
You
won't
have
too
much
things
to
do.
A
Okay:
okay
upcoming
calendar
next
weekly
2.393.
A
8Th
of
March,
okay,
we'll
discuss
that
applying
then
next
security
release
we
had
one
last
week
as
far
as
a.
C
A
C
C
A
C
C
A
Okay,
when
is
it:
when
does.
A
A
C
A
C
A
cdcon
is
coming
in
May
to
Vancouver
British
Columbia
Canada.
A
Other
calendar
events,
nope
okay,
so
let's
proceed
to
the
walk
down
and
walk
in
progress
thanks
to
the
team
would
we
took
the
wealth
while
I
was
out
in
an
unexpected
notice?
A
lot
of
four
questions:
I'm
quite
happy
with
the
outcome,
meaning
it's
not
a
one
person
team.
It's
a
world
team.
A
Maven
3.9.0
has
been
generally
deployed
to
Cigar
earlier
today
we
walked
a
bit
on
that
element,
so
an
email
has
been
sent.
So
thanks
Stefan
for
the
heavy
lifting
there
internal
sorry.
B
Yeah
I
would
have
not
just
said
that
in
a
discussion
opened
by
James
Nord
about
Maven
and
clicking
on
Jenkins
creative
list.
B
D
C
A
Which
is
still
related
to
the
infra,
but
it's
a
positive
feedback
for
me.
It's
the
fact
that
correct
me,
if
I,
if
I
understood
wrongly,
but
the
email
from
gems
is
about
a
time
after
the
infra
deployed
the
new
Maven
version,
the
time
before.
That
version
start
to
be
a
base
requirement
for
most
of
the
plugin,
which
means
the
infra
team
is
leading
the
updates
of
the
tools
we
use
to
build
Jenkins
and
Associated
tools.
Right,
that's
a
good
thing,
but
that
means
we.
B
B
A
Okay,
but
thanks
for
mentioning
that
that
means
that
there
are
discussion
prompted
by
the
fact
that
if
we
are
able
to
provide
much
more
frequent
update
of
the
main
tools
such
as
Java
and
Maven,
we
can
can
stay
ahead
and
help
developer
to
be
in
advance.
So
that's
really
a
good
thing.
A
That's
all
for
me
on
the
maven
topic.
Do
you
have
some
other
elements?
A
Yeah,
I'm
sure
all
GitHub
action
version
are
pinned
and
tracked
thanks
survey
for
Dobby
lifting
there,
it
was
an
exhaustive
listing
and
check
that
we
have
deepened
about
automatically
updating
any
GitHub
action
version
that
we
have
everywhere
on
all
of
the
Jenkins
info
repositories.
A
D
A
Nice
job
so
now
that
part
is
fully
delegated
to
depend
about
which
walking
concert
with
negative
actions,
so
that
will
avoid
us
being
cooked
by
surprise
on
any
depreciation
such
as
node.js
12
was
deprecated
a
few
months
ago
on
GitHub
action
and
not
gs16
was
required
and
that
one
could
have
broken
elements.
A
So
that's
one
of
the
numerous
examples
why
we
have.
We
need
pinned
version
to
be
sure
we
have
a
career
and
behavior
which
stay
the
same
across
time
and
we
update
all
the
time
and
since
GitHub
action
is
really
easy
to
use
with
Dependable.
That's
why
we
don't
use
update,
CLI
or
another
tool
for
that.
It's
easier
with
Dependable
for
us.
A
Can
no
longer
test
PCT
incremental
in
Jenkins
bomb,
so
that
one
was
a
tricky
one
related
to
the
ACP,
which
is
our
top
priorities
till
today.
You
want
to
explain
you
want
me
to
to
explain.
B
Yes,
so
is.
B
Couldn't
determine
the
correct
repository
to
use
it
was
trying
to
use
the
public.
One
for
retrieving
is
the
BCT
and
criminals,
and
this
is
due
to
the
fact
we
are
using
mistakes
in
the
mirror
half
section
of
the
settings
to
be
able
to
mirror
every
modern
repository.
B
But
adding
this
effects
made
Maven
confused
that
the
repository
to
use
and
with
Tanya
and
the
other
yeah
we
found
out
that
adding
the
new
Maven
layout
or
specifying
the
default
repository
helps
the
narend
to
know
which
report
to
use.
A
So
that
that
was
a
huge
team
walk
on
numerous
level,
because
it
was
tricky
and
the
age
cases
it
was
scoped
to
only
the
dependency
gets
goal
of
Maven
with
the
remote
repositories
flag
set
up
to
a
list
of
repository
which
goal
is
to
end
Maven,
which
Preparatory
to
use
to
check
for
the
required
dependency.
That's
slightly
different
than
the
usual
Maven
clean,
build
package
verify
test
commands
where
the
full
dependency
trades
automatically
determined
from
the
pawn
parents
with
the
usual
thing.
A
That's
what
we
have
on
most
of
the
repository,
but
here
Maven
is
not
able
to
automatically
detect,
which
repository
us
to
dependency
the
new
layouts.
We
had
an
issue
like
this
one
that,
with
the
releases
with
the
maven
release,
plugin
3.0,
so
there
might
be
some
other
components
of
Maven.
That
has
the
same
issue
where
at
the
moment
on
time,
the
old
layout
is
marked
as
deprecated
and
the
side
effect
in
that
specific
case
was
every
time
the
first
one
was
always
used,
always
the
default.
A
A
What
did
we
have?
Rick
and
Pedro
Duty
alert
disk
space
so
that
one
is
fixed.
The
windows
Docker
image
build
for
Jenkins
and
Jenkins
agent
were
using
way
more
disk
space
than
what
we
provided.
So
after
searching
and
checking
the
build
logs
were
able
to
find
build
failures
and
by
increasing
the
size
at
150
gigabytes,
we
were
able
to
have
this
build
passing.
A
That's
main
I
assume
it's
because
we
had
more
dependencies
and
we
built
all
the
windows
on
the
same
machine.
If
we
split
on
different
machine,
we
won't
need
more,
but
the
additional
cost
is
almost
nothing
between
130
and
150
gigabytes.
It's
enough
that
reserves
an
opportunity
to
use
premium
ssds
for
this
machine,
since
we
know
that
the
Windows
Virtual
machines
are
pretty
higher
bound,
especially
for
tests
on
Jenkins
score
and
other
ath
stuff.
So
that's
why
using
premium
ssds
is
clearly
a
service
to
the
developer.
A
Again,
we
can
afford
that
additional
cost,
because
we
were
able
to
to
decrease
the
Azure
build
since
the
Batmans.
So
I
expect
three
or
four
hundred
additional
dollars
per
month,
but
we
were
able
to
decrease
2.5
k.
So
that's
that's.
Okay,.
B
Just
yeah
sorry,
we
received
a
notice
about
Microsoft
or
an
increase
of.
A
C
A
Here
it's
only
virtual
machine
agents:
The
Next
Step
will
be
to
focus
on
the
Windows
container,
which
is
still
a
tricky
part.
A
Anything
else
on
that
topic:
okay,
Contour
image
for
weekly
not
published
last
week.
So
this
was
an
issue
mainly
related
to
the
shell
script
used
on
the
official
Jenkins
CI,
slash,
Docker,
Repository
thing.
It
was
fixed.
The
maintenance
of
that
repository
were
able
to
work
on
that
and
fix
it
was
mentioned
and
the
infrastructure.
So
we
had
an
audit
log
and
we
will
have
an
historic
trace
of
what
was
done.
A
Nothing
expected
more
from
the
infra
team
because
we
were
able
to
quickly
check
it
wasn't
related
to
the
infrastructure
itself,
but
to
the
publication
script
to
GitHub
permission
repository
to
Archive.
So
thanks
a
lot
Alex
a
nil
pointer
exception
and
stable
CI
job.
A
B
Because
yeah
it
was
you,
it
was
a
temporary
hook,
it
was
a
test,
I
was
doing
and
he.
B
C
Well,
it
says
that
my
RSS
monitoring
of
of
job
failures
of
certain
precious
jobs
is
working
or
are
they
was
the
innocent
victim
of
my
job
monitoring
but
I.
C
There
was
a
there
was
an
issue
related
to
container
image.
Getting
the
wrong
image.
Was
that
already
hidden
in
one
of
the
others,
or
is
it
later.
A
B
C
A
D
A
A
So
now
the
code
on
the
main
branch
is
removing
the
LTS
version
and
only
keep
the
weekly
version
and
then
get
the
latest
line,
which
is
still
fragile
code,
but
that
should
be
okay
for
that
fix,
and
now
we
need
to
republish
a
new
weekly
to
be
sure
that
the
the
latest
tag
are
okay,
okay,
but
good,
point
it's
not
in
for
relatives,
but
we
will
have
to
finish
the
job
today.
A
A
Okay,
now
walk
in
progress,
so
two
new
issues,
first
one
it's
so
that
one
might
create
May
a
montrusted
CI
since
two
weeks
at
the
puppet
agents
is
telling
us
the
it's
failing
to
run,
untrusted,
cig
and
kinsai
virtual
machine.
The
issues
is
related
to
third
Bots
and
it
looks
like
the
third
bot
version
between
the
plugin
we
use
for
DNS,
Challenge
and
Azure,
and
the
third
board
to
install
is
failing
to
integrate.
There
is
a
weird
issue
that
might
be
fixed,
but
right
now
it's
failing.
A
So
we
cannot
renew
you
automatically
the
certificate
on
trusted.
Ci
the
same
issue
might
or
might
not
appear
on
search
CI
as
well.
It's
only
these
two
machines
that
have
the
problem,
so
it's
not
blocking,
but
you
might
see
on
trusted
or
third
CI
issues
related
to
the
certificate.
If
it's
the
case,
there
is
no
problem
to
accept
temporary
self-state,
the
state.
The
self
signed
certificate.
A
Major
issue
the
one
which
is
holding
us
from
today's
weekly.
It
looks
like
that,
since
we
bumped
the
agents
templates
to
the
latest
Docker
23
on
Ubuntu
2004,
that
now
the
buildix
plugin
is
not
installed
anymore
by
default
in
our
setup.
So
I'm
not
sure
if
it's,
if
it's
because
it
used
to
be
a
package
dependency
of
Docker
CE.
If
it
was
part
of
the
package,
is
it
a
new
package?
A
A
A
B
Yeah,
this
is
to
the
main
name:
it's
I
yeah.
It
seems
really
Legit
To
Me,
sending
an
email
to
the
new
one
to
ask
if
it's
correct,
I,
don't
know
but
yeah
or
maybe
try
to
contact
Telus
group
to
ask
if
they
change
their
domain
name
but
yeah.
A
A
Otherwise,
as
soon
as
we
are
sure
enough
that
the
person
is
the
person
who
they
claim
to
be,
then
we
can
go
at
worth
checking
if
that
person
maintains
a
plugin,
because
that's
not
the
same
if
it's
a
personal
account
or
a
plugin
manner.
That's
not
the
same
level
of
danger
and
checking
the
history
of
shiradwell.
B
Yes,
just
to.
D
B
A
B
A
C
A
A
B
D
A
A
It's
just
a
word
of
question.
If
that
person
does
not
manage
any
plugin,
then
the
risk
is
clearly
lower,
but
still
there
is
a
rift
yeah
Maven
17
labor
longing
on
CR
Jenkins,
so
there's
been
a
lot
of
discussion,
but
what
we
saw
from
the
metrics
is
that
the
each
time
we
have
a
new
LTS
release
the
bone,
the
amount
of
bomb
builds
I'll,
clearly
big
enough
to
be
to
request
more
resources
than
we
can
provide.
A
As
we
discussed
some
of
us,
the
goal
is
now
first
to
increase
the
amount
of
bills
that
can
be
taken
over
in
digital
ocean
which
will
increase
the
you
see
this
Plateau
here
of
around
150
160
available
and
used
executor
immediately
the
red
curve,
while
the
gray
curve
is
the
amount
of
requested
executors.
So
if
we
can
increase
the
amount
of
builds,
we
will
have
to
check
the
digitalization
credits,
of
course,
but
that
should
help
especially
the
8th
march,
with
the
new
LTS.
A
Another
thing
will
be
trying
to
split
the
workloads
between
bomb
builds
and
plugins
or
other
things
to
avoid
annoying
plugins.
While
a
build
is
running
that
one
would
not
make
the
the
agent
come
faster,
but
I
will
be
sure
that
we'll
have
a
pool
of
agent
for
one
another
Pool
which
physically
separates
the
two
workloads,
and
that
should
avoid
annoying
plug-in
developer
when
they
need
to
build
that's
more
convenience
for
our
user
than
really
a
performance
or
capability
increase.
A
C
A
A
A
Cool
terminates,
Next
Issue
terminate
build
stocks
in
Q
and
infrasti
that
one
is
I
think
a
complicated
one.
Each
time
we
have
a
full
restart,
usually
the
weekly
upgrade
on
infra
CI.
A
lot
of
builds
are
stuck
waiting
with
that
terrible
message
that
same
terminating
with
extreme
prejudice,
despite
having
a
timeout
which
seems
to
be
triggered
still
the
jobs
our
Sinners
are
currently
running.
A
A
A
Most
of
them
are
corrupts
after
three
or
four
restarts
that
happen
during
the
check
of
that
Port.
So
what
we
saw
in
the
metrics
is
that
there
was
a
lot
of
CPU
IO
and
a
lot
of
CPU
used
both
both
of
them.
So
the
CPU
user
usage
on
Jenkins
can
come
from
numerous
area,
but
for
sure
the
CPU
io8
comes
from
the
CPU
waiting
for
Io
operations,
and
we
all
know
that
Jenkins
is
really
even
a
operation
when
restarting
so.
A
The
first
step
we
took
was
to
increase
the
quality
of
service
of
the
underlying
persistent
volume
on
the
Sun
System,
provided
by
Azure.
We
are
able
to
change
the
the
quality
of
service
of
the
SSD,
which
increased
a
lot,
the
amount
of
iops
that
are
available,
because,
even
if
it's
burstable,
which
means
you
can
use
for
a
certain
time
way
more
iops.
We
were
clearly
over
the
budget
and
we
were
already
limited
by
the
storage
system.
A
Eventually,
if
we
still
have
CPU
I
usage
or
memory
I
usage
that
are
preventing
the
controller
to
restart
only
once
when
updated,
then
we
might
think
about
increasing
the
amount
of
CPU
and
memory.
But
right
now
we
have
to
check
if
the
new
iOS
has
an
impact
and
see
if
it's
still
using
a
lot
of
CPU
when
restarting
today's
weekly
release
once
released
and
apply,
will
show
us
way
more
metrics
and
we
can
take
a
decision
based
on
that.
A
So
we
hope
it's
not
a
burgundy
pipeline,
but
we
saw
that
less
and
less
so,
let's,
let's
see
later
to
continue
unless
there
is
a
question,
no
point
or
something
I
missed.
A
That
one
is
a
is,
is
worrying
me
or
Mark.
I
might
need
help
on
this
one.
A
D
A
Maybe
if
no
one
objects
I
will
just
ask
elbow
double
check
from
the
security
team,
just
in
case
that
we
don't
do
anything
wrong,
because
in
that
case
it's
literally
a
plugin.
So.
C
Well
and
I
do
have
contacts
I
have
recently
established
some
contacts
at
atlassian-
oh
not
in
this
organization,
but
I
have
contacts
inside
atlassian
that
have
helped
us
with
the
Jenkins
the
issues
that
jenkins.io
license,
and
so,
if
we
had
to,
we
could
always
ask
someone
that
is
known
to
be
authenticated
inside
atlassian.
To
help
us
understand.
Is
this
person
that's
claiming
this
actually
part
of,
or
is
that
GitHub
account
actually
part
of
the
Ops
Genie
team
at
atlassian?
So
good.
C
A
Okay,
since
I
I
assign
myself
no
objection
if
I
check
what
is
on
our
leldap
database
trigger
a
password
requisite
then
tell
us.
You
have
received
a
password
reset
on
the
associated
mail
check
internally
with
the
other
teams,
otherwise
take
contact
from
your
email
to
Jenkins,
infra
or
whatever.
So
we
acknowledge
they
won't
have
a
silent
issue
and
we
and
then
I
will
take
over
and
if
we
need
to
wait
weeks,
I
will
let
them
know
so
they
won't
have
to
wait.
A
As
your
credential
for
certiary
expired,
a
quick
one,
the
credit,
the
Azure
token
used
by
the
search,
CI
private
controller,
to
spawn
virtual
machine
to
be
used
as
agents
add
a
token
which
expires
we
generated
one
month.
One
and
I
have
to
I
should
have
paired
with
stefanolio
today,
but
isn't
available.
Today,
the
goal
is
to
use
a
workload
identity,
that's
a
topic
that
Airway
and
timia
combo
already
brought.
A
So
the
idea
is,
instead
of
having
a
token
that
we
have
to
store
in
Jenkins
it's
to
use
as
your
capability
to
authenticate
the
workload
so
no
need
for.
For
having
a
token,
it's
usually
oidc
authentication
under
the
hood.
It's
the
same
thing
as
automatic
I
am
profile
on
AWS
and
that
avoids
storing
any
kind
of
credential,
which
means
no
need
to
to
to
have
a
credential
to
renew
it's
automatically
generated
every
hours
for
us.
A
So
that's
the
definition
of
done.
I'm
not
sure
we'll
have
time
to
do
this
one
next
week,
but
that
yeah,
that
should
be
a
nice
experiment.
B
The
end
of
line
is
soon
I,
didn't
put
it
in
the
issue.
I
will
add
it.
B
A
B
It's
in
a
predict,
I
think
I.
Don't
let
me
let
me
check
it
and.
B
A
A
We
splits
on
different
provider.
We
need
to
parallelize
the
different
provider
on
this
one,
but
yeah
I,
don't
mind
you
starting
the
change
log
I
can
help.
If
that's
okay,
for
you.
A
C
We
captured,
we
captured
a
series
of
screenshots
and
from
those
screenshots.
We
think
we
may
benefit
by
doing
an
update
to
the
document,
because
the
the
documentation
that
does
exist
was
three
years
old
and
the
prompts
are
slightly
different.
So
we
followed
the
documentation,
it
helped
us,
but
it
was
slightly
different.
I've
captured
those
screenshots
stored
them
on
two
different
places
so
that
if
my
hard
drive
dies,
we
don't
we
don't
lose
them,
but
we
we
still
have
work
to
do
on
this.
A
C
A
C
A
Especially
since
you
are
going
to
be
out
of
office
soon,
if
we
have,
if
you're,
very
Stefan
and
higher
to
take
over
on
that
area,
good.
A
Thanks
a
lot
mark
AKs
ad
cluster
public
Gates.
B
It's
immigration
of
services,
which
has
been
boost
for
now;
okay,
aim
for
all
private,
the
next
steps
we
have
to
have
two
update
the
issue
with
the
immigration
plan.
We've
come
up
with
Stefan
and
yeah.
We.
A
So
if
I
understand
correctly,
we
won't
work
on
the
issue
public
case
new
cluster
for
the
upcoming
week.
Given
the
amount
of
work,
however,
work
has
been
started
by
Stefan
and
you
will
be
continued
about
the
private
teams
and
the
scope
is
preparing
and
planning
carefully
the
migration
of
release.
Cigen
can
say
you
from
the
current
production
cluster
to
the
new
private
Crystal
s,
so
on
the
to-do
list.
A
B
Yeah
is
that
correct,
that's
true!
Yes,
we
have
to
delete
the
all
the
time
private
cluster,
too
yeah
I.
A
Forgot
about
that
yeah.
That
would
be
another
issue
blunderbated
to
B
return
in
issues
there
for
new,
not
pools
to
be
review,
merge
deployed,
okay,.
A
B
C
Mind
I
think
I'd
be
happy
to
review
it
and
that's
one
of
those
tools
that
really
needs
some
intelligence
added
to
it
right
now.
It
is
absolutely
failing
to
retain
at
least
if
I
understand
correctly
failing
to
retain
all
history
right.
It
doesn't
get
any
benefit
from
anything
every
week
it
rebuilds
all
sorts
of
things
horribly.
So
with.
C
A
I
don't
know
if
the
ath
accidents
tests
are
necess
is
also
using
ACP
or
nuts.
It's.
B
Using
run
Maven,
so
it's
as
I
have
to
check,
but
I
think
it's
using
the
ACP.
Most
of
the
repository
are
now
using
certification
proxy.
So
when
which
doesn't
the
one
where
Maven
is
called
from
java?
A
Problem,
it's
just
that
that
one
is
even
builds
so
also
just
checking.
B
A
Adding
ACP
to
EV
builds
as
an
outcome
for
us,
which
is
if
it
helps
to
have
faster,
builds
that
mean
less
machine
time
to
pay
for
cool
okay.
In
terms
of
the
data
that
g
frogs
sent
to
us
last
week,
where
you
were
someone
able
to
check
if
there
has
been
an
impact
or
not,
unfortunately,.
C
A
Okay,
so
that
one
is
more
on
the
realign
Parts
more
than
the
ACB
discussion
still
in
progress.
Is
she
frog
on
the
big
consumers
detected
outside
ourselves
right,
nothing
done
on
the
ldap
I've
de
prioritized
that
or
dab
slash,
Authentication.
A
A
C
And
I
I
still
think
that
makes
sense.
The
the
the
authenticated
access
would
not
have
blocked
any
of
the
ACP
usages
and
it
would
not
block
the
current
single
largest
user
from
China
they're.
Both
public
look
they're
both
locations
for
artifacts
that
we
publish
so
we
need
we
authenticating
won't
help
because
those
are
intentionally
not
authenticated.
A
A
So
we
had
we
had
it,
we
added.
Oh,
yes,
a
request
for
Alex
to
access
through
State
CI
Chinese
website
and
the
rest
are
things
that
we
already
covered.
So
two
new
issues,
I'm
adding
this
one
to
the
Milestone
as
well.
A
We
refused
that
a
few
months
ago
before
the
previous
elections,
because
edx
was
even
though
being
a
trusted
and
valuable
contributor.
Wasn't
a
Jenkins
board
member
elected
board
member
and
the
only
reason
for
him
to
access
trusted
is
to
be
able
to
kick
a
new
Docker
Jenkins
Docker
container
built
thing
is
that
even
with
his
new
statues
one
month
ago,
I
would
have
said
that
Jenkins
officer,
we
don't
need
better
to
spend
the
effort
on
migrating
the
job
to
release
CI
where
it
should
be
done.
A
C
No
objection
from
me
Alex
great
choice
and
yes
long
term.
We
want
to
get
that
job
off
trusted
CI.
So,
ultimately,
his
need
for
Access
will
go
away,
as
we
hope
will
many
of
our
needs.
C
Low
low
priority,
this
one
does
not
need
to
be
an
upcoming
work.
The
the
intent
here
is
that
we
need
to
the
the
Chinese
website.
Jenkins.Io
zh
is
has
not
had
new
translations
in
two
or
more
years
and
we're
now
getting
issue
reports
from
Chinese
users
when
they
read
the
instructions
in
Chinese
how
to
install,
and
they
are
completely
outdated
right.
C
You
think
about
all
the
changes
we
made
in
two
years
to
how
you
install
Jenkins
the
system,
D
transition,
the
packaging
updates
for
to
for
containers
all
sorts
of
things,
so
the
for
me,
the
Chinese
site,
is,
is
becoming
more
liability
than
help
to
Native
Chinese
speakers,
and
so
we
do
want
to.
We
want
to
stop
it
and
but
have
its
Pages
somehow
redirect
to
the
English
Pages
I,
don't
know
how
to
do
that.
I
also,
don't
think
this
is
urgent.