[DiscordArchive] I know how to fix that now (run clean:build) but if we have to do that every time, shouldn't it at l
[DiscordArchive] I know how to fix that now (run clean:build) but if we have to do that every time, shouldn't it at l
Original source
I know how to fix that now (run clean:build) but if we have to do that every time, shouldn't it at least be part of the update instructions?
rektbyfaith
10-10-2023, 07:42 PM #1Archived author: Fijahh • Posted: 2023-10-10T19:42:23.073000+00:00
Original source
I know how to fix that now (run clean:build) but if we have to do that every time, shouldn't it at least be part of the update instructions?
Original source
Currently the instructions just say 'git pull origin master' and then rerun build
rektbyfaith
10-10-2023, 07:42 PM #2Archived author: Fijahh • Posted: 2023-10-10T19:42:39.635000+00:00
Original source
Currently the instructions just say 'git pull origin master' and then rerun build
Original source
I have a PR in that will make it not a problem
rektbyfaith
10-10-2023, 07:42 PM #3Archived author: mynameismeat • Posted: 2023-10-10T19:42:47.297000+00:00
Original source
I have a PR in that will make it not a problem
Original source
Awesome!
rektbyfaith
10-10-2023, 07:42 PM #4Archived author: Fijahh • Posted: 2023-10-10T19:42:53.353000+00:00
Original source
Awesome!
Original source
but yeah, at the moment it's something to be aware of. I think it mounts the build config (which is conflicting, hence the error) to a volume so it's a little clunky to get rid of it. I think in the past there was an expectation of just building without cache every time or something, im not really sure.
rektbyfaith
10-10-2023, 07:44 PM #5Archived author: mynameismeat • Posted: 2023-10-10T19:44:01.137000+00:00
Original source
but yeah, at the moment it's something to be aware of. I think it mounts the build config (which is conflicting, hence the error) to a volume so it's a little clunky to get rid of it. I think in the past there was an expectation of just building without cache every time or something, im not really sure.
Original source
I don't mind doing a full rebuild because it only takes 5 mins on my machine, but it seems like if everyone's having the issue it should be part of the instructions
rektbyfaith
10-10-2023, 07:44 PM #6Archived author: Fijahh • Posted: 2023-10-10T19:44:04.003000+00:00
Original source
I don't mind doing a full rebuild because it only takes 5 mins on my machine, but it seems like if everyone's having the issue it should be part of the instructions
Original source
oh, 100%
rektbyfaith
10-10-2023, 07:44 PM #7Archived author: mynameismeat • Posted: 2023-10-10T19:44:14.078000+00:00
Original source
oh, 100%
Original source
Maybe we should add a paragraph after the instruction to run the build that says 'if you get errors that look like this, run clean:build then build again'?
rektbyfaith
10-10-2023, 07:44 PM #8Archived author: Fijahh • Posted: 2023-10-10T19:44:47.036000+00:00
Original source
Maybe we should add a paragraph after the instruction to run the build that says 'if you get errors that look like this, run clean:build then build again'?
Original source
(Looking forward to your fix, but there's probably no guarantee we won't hit it again in future)
rektbyfaith
10-10-2023, 07:45 PM #9Archived author: Fijahh • Posted: 2023-10-10T19:45:58.375000+00:00
Original source
(Looking forward to your fix, but there's probably no guarantee we won't hit it again in future)
Original source
Does running clean:build necessitate redownloading the client data? If not, how does one know when a client data update is needed?
rektbyfaith
10-10-2023, 07:49 PM #10Archived author: Fijahh • Posted: 2023-10-10T19:49:00.521000+00:00
Original source
Does running clean:build necessitate redownloading the client data? If not, how does one know when a client data update is needed?