0:00:27
what is going on guys welcome back to
0:00:29
another session of buildbreaking fix
0:00:32
brought to you by the one and only the
0:00:34
raw coder today as well
0:00:37
no code is because the coders are a bit
0:00:40
occupied with some other stuff so it's
0:00:43
only the one quota
0:00:46
yeah so first thing is first let's play
0:00:49
the acknowledgement of the country and
0:00:50
play our own respects to the elders of
0:00:52
the past present and future so here we
0:00:58
i begin today by acknowledging the
0:01:00
traditional custodians of the land on
0:01:02
which we gather today and pay my
0:01:04
respects to the elders past present and
0:01:07
future i extend their respect to
0:01:09
aboriginal and torres strait islander
0:01:14
fantastic so that was smoothly done as
0:01:19
uh so just to give a bit of a context
0:01:23
so actually i almost forgot we need to
0:01:26
play the background music
0:01:32
which one can we go for this time
0:01:38
i'll pick probably
0:01:49
r is d so i've got two options for
0:01:53
the let's play the
0:01:55
the first one this one
0:02:14
right cool so today what we're going to
0:02:17
be doing is we're going to be
0:02:20
fixing a websocket bug which i'll tell
0:02:23
you which one it would be
0:02:30
picture speaks a thousand words isn't it
0:02:37
now to do let me just open up my project
0:02:40
actually first i need to share screen
0:03:02
so let's get the ball rolling and i'll
0:03:06
open up the project
0:03:14
open up the folder
0:03:19
scramble enhancements
0:03:55
so uh yeah forgot to tell you guys that
0:03:58
i didn't manage to do the merge so
0:04:01
all the git repo has been cleaned up
0:04:07
just have to really hope for that if it
0:04:09
works properly or not so
0:04:12
let's do a quick run
0:04:17
i need to open up cd client
0:04:35
test on board and that we should
0:04:39
go to the next page automatically
0:04:42
which is fantastic
0:04:48
i did a bit of a mess up in probably the
0:04:54
and um now we've got this a bit of a big
0:04:57
issue which says that um
0:05:02
it's it cannot read the prophecies of
0:05:04
undefined reading which is
0:05:09
that one is basically over here
0:05:15
aws look yeah so you can't read this
0:05:25
which means that our websocket isn't
0:05:39
we're gonna have to fix this first in on
0:05:42
in order to move on
0:05:45
let's hope we get this fixed
0:05:48
by the end of this session
0:05:50
which would be epic all right so let's
0:05:55
so it's saying that cannot read the
0:05:56
properties of undefined reading send
0:06:10
this one isn't being picked up
0:06:16
this is being there with
0:06:46
so how do we fix this one if this is not
0:06:50
showing up as in descent
0:07:23
so what we are basically doing
0:07:33
oh what's not being picked up
0:07:39
so they're talking to me
0:08:07
so it doesn't even connect to websocket
0:08:10
anymore because the websocket isn't
0:08:15
properly done probably
0:08:25
missed a branch when i was merging it
0:08:30
that might be the case
0:08:36
fix merge conflict yeah that is fine
0:08:42
so how many branches are there
0:08:45
this is get bored get uh-huh
0:08:52
get bored functionality
0:09:16
all the requests active still
0:09:33
so where did the branch emerging
0:09:37
where did this why are you not
0:09:39
picking this one off 465
0:09:59
465 which is there
0:10:02
actually websockets and
0:10:18
so it doesn't even call that one
0:10:25
when it comes to index
0:10:28
let me go in this one and check
0:10:36
yeah that should be fine
0:10:43
the front there's still front end has
0:10:50
and dispatch action yeah
0:10:55
not even opening up
0:11:02
it doesn't even open it up does it
0:11:12
yeah it doesn't even come here on
0:11:27
but they should come to on connect
0:11:31
check with initialize websockets and
0:11:44
okay that is done in the load board page
0:11:51
yes is crashing here
0:11:54
which means they won't calm down
0:11:58
and they stop crashing this
0:12:02
is basically crashing
0:12:26
so where is websocket being defined
0:12:34
websocket is being defined
0:12:45
let's okay this one
0:12:49
is the euro right and is the api
0:12:56
right as well let me just have a look
0:12:59
because i've got suspicion
0:13:01
that the apa url isn't right
0:13:47
because it might be the api get raising
0:13:58
yeah that is the right one
0:14:01
and websockey url 2c4155
0:14:15
two c four one five five yeah
0:14:20
that's right as well
0:14:26
um so webs this one is okay
0:14:30
what else can be wrong
0:14:40
websocket thing it is in there as in
0:14:46
maybe let's have a look
0:14:51
is in the other branch though
0:14:54
let's have a look at that where we got
0:14:58
sv because it was working fine in this
0:15:01
branch which is sv80
0:15:04
so let's go to that branch and see
0:15:09
node modules are okay so i'm gonna have
0:15:14
switch to that one
0:15:24
okay and my note modules are here
0:15:30
i should have websocket here
0:15:43
is this not in the main branch then
0:15:49
because this might be the reason why
0:15:51
that's not working because the module
0:15:54
isn't there in the first place
0:16:20
node tools okay so if i go to
0:16:24
just comparing the branch that works
0:16:27
with the price that doesn't work
0:16:34
oh hang on a minute
0:16:36
so they're two node modules
0:16:40
it must be in a different one then
0:16:59
this is in the other one as well
0:17:17
ws yeah is in that one as well
0:17:20
okay now go back to
0:17:25
the other one and see if we had to
0:17:27
install it especially
0:17:29
local server no no no
0:17:44
boom being there and check
0:17:57
socket no it's not there either
0:18:02
sucky io tiny bini
0:18:15
no it's not either
0:18:19
node modules install websocket basically
0:18:22
i might need to install in there
0:18:51
okay how do we use this
0:19:03
there's just that one
0:19:31
the sock isn't working at the moment
0:20:08
so websocket isn't there
0:20:48
providing space website roommates to
0:20:55
see if i do websocket
0:21:08
open yeah but why is he not sending i
0:21:12
think it doesn't even connect in the
0:21:16
so that's where we probably have to
0:21:20
because it's not taking
0:21:30
the selkie method sends
0:21:40
it was working bit before the merge
0:23:08
send this causing the problem
0:23:11
although if it does
0:23:15
i promise cannot read prophecies
0:23:20
it doesn't even connect at the moment
0:23:43
all right here we go
0:23:47
that seems to be something i'm looking
0:23:55
when you turn off accidentally
0:23:56
repeatedly my variable that
0:23:59
i've talked instead of using the global
0:24:05
undefined at that moment
0:24:16
so wherever you use the
0:24:22
because that's apparently coming up as
0:24:27
that's what it's saying in the
0:24:34
how is that possible
0:24:39
not defined anywhere
0:24:44
cookie url websocket websocket yeah
0:24:49
and then i'm using everywhere
0:25:08
it's all on my pen
0:25:58
let me see if any comments have come up
0:26:11
so websock is basically coming up as
0:26:21
so ah so this is being initialized
0:26:25
with this being initialized
0:26:29
interface produce and receive
0:26:40
initialized over here which is great
0:26:56
so if that's loading the board page
0:27:06
where is that coming in
0:27:14
okay so he's crashing on get bored by
0:27:22
the question on this one then it doesn't
0:27:29
one seven seven forty one seven
0:27:36
those boldness so it doesn't come any
0:27:56
i don't want to peek i want to view that
0:28:27
so basically there might not even be the
0:28:30
problem i'm just viewing the wrong thing
0:28:38
if i get rid of that
0:28:41
and open another session
0:29:06
websocket is in the problem the problem
0:29:08
was the board column that's all
0:29:16
web stock is working fine basically
0:29:19
so we just have to
0:29:26
um that bug which is i'm gonna explain
0:29:34
this is the bug apparently that we
0:29:37
we're gonna focus in now because
0:29:40
the websocket problem i thought isn't
0:29:43
the problem the problem is the board
0:29:58
it's coming here so if i type in one
0:30:06
do that see it doesn't move
0:30:09
so we need to send
0:30:16
the position through the websocket as
0:30:18
well which it might not currently have
0:30:22
so there is a problem that we need to
0:30:26
does he have the position yes it does
0:30:45
right so the value isn't coming here
0:30:48
this isn't uh the position value isn't
0:30:51
coming here the color id and value is
0:30:55
but the position isn't color
0:31:07
in data but we need to add the position
0:31:12
all right uh where was your received
0:31:17
need to go to this received message and
0:31:21
see what's happening over there
0:31:28
which one was this
0:31:41
i'm gonna create a new branch and which
0:31:47
what was the problem there
0:31:51
which ticket was it on i need to check
0:32:10
the problem was board not moving card
0:32:26
voila a branch already it's okay we can
0:32:31
switch to that branch then sp
0:32:41
now we need to go through
0:32:50
what does the data have
0:33:01
uh we need to be able to receive the
0:33:15
so at the moment we are seeing date
0:33:27
this is interesting didn't expect this
0:33:38
oh because i haven't played it yet
0:33:44
i haven't ran a project
0:33:52
and then projects and then now we're
0:33:55
gonna run it and do 1 19
0:34:12
okay and then do this one
0:34:19
i think we need to open this one up
0:34:29
okay non-searches so it's got the text
0:34:34
but in this one the position doesn't
0:34:38
so what does it have instead
0:34:43
say instead is good in data score action
0:34:46
and date data is called action and data
0:34:52
and then in data it's got
0:35:02
date in the data is called coloradian
0:35:24
very going wrong here
0:35:28
value actually i'm gonna go
0:35:37
this would be script
0:35:52
so we need the children images
0:36:07
and data position maybe
0:36:19
there you go this is the one that we
0:36:22
color and position
0:36:27
what would the position be
0:36:32
target test content
0:36:49
let's check if that works
0:37:00
we can really class so the position is
0:37:03
already there there
0:37:06
apparently saying that position is
0:37:43
i cannot really declare constant
0:37:48
position new problem
0:38:07
oh so position is already here
0:38:13
so we don't need to declare this again
0:38:16
you can just basically use this
0:38:23
go away why is it not
0:38:31
yeah i got the point now go away
0:38:57
you're slightly annoying now
0:39:05
well here we go perfect
0:39:08
where's the value coming from and text
0:39:11
is coming from here
0:39:13
from value position
0:39:22
body position then transition would be
0:39:27
let's see if this works
0:39:38
okay cool let's try this if this one
0:39:44
it might work you might know who knows
0:39:47
nonetheless you try it
0:40:08
okay let's give it a shot now
0:40:16
okay let's see if no
0:40:34
colon null is coming
0:40:42
what's the events bringing
0:40:45
i need to find that one out first
0:40:48
what does the event bring
0:41:44
that can't be it then
0:41:52
i'm just doing in basically
0:42:00
but why can't i see
0:42:10
dispatch action message
0:42:18
action is that one data is
0:42:28
so i need to see what's coming in the
0:42:37
what's in the event
0:42:53
position before can rest the position
0:42:56
before initializing
0:42:59
all right so that's not gonna work
0:43:18
why is this not being printed
0:43:37
can i just talk before initializing
0:44:04
card element that one okay
0:44:07
now check what does it do
0:44:23
oh right now hang on
0:44:49
action i date id value color
0:45:33
let's see if this gives me what i want
0:45:48
does he give me what i want
0:45:56
no it doesn't give uh it gives me the
0:45:58
color white here oh yeah
0:46:01
that's fine so now if i insert the
0:46:34
doesn't make it doesn't make you go
0:46:43
now you must be something else for the
0:46:51
target and heart dip content
0:47:19
no position there is
0:47:26
let me do in this way
0:48:30
if i do text content
0:48:56
what does that give me
0:49:04
ah position isn't coming right
0:49:07
so position isn't coming in the target
0:49:21
send message here position
0:49:30
so what happens if i do it
0:49:43
so it does give me position
0:49:53
thing for position i need to have a
0:50:26
edit card websocket on card change
0:50:35
oh hang on here you go
0:50:40
see and then i can add the
0:51:51
all right we'll probably have to come
0:51:52
back to this afterwards
0:51:57
because we're really really really close
0:52:09
yeah guys we're really really close to
0:52:12
finishing these projects all be with me
0:52:15
and um we will come back to the bug fix
0:52:18
tomorrow because at the moment my brain
0:52:20
isn't working at all whatsoever
0:52:24
yeah but it was really great having you
0:52:29
and um if you want to see
0:52:33
how we solve this problem feel free to
0:52:36
join us tomorrow same time same place
0:52:39
and a different task all right i'll see
0:52:41
you guys tomorrow have a good night
