[DiscordArchive] The squash issue is more important but at the same time.. isn't it getting close to a year since the
[DiscordArchive] The squash issue is more important but at the same time.. isn't it getting close to a year since the
Original source
You said it more kind
rektbyfaith
01-07-2024, 02:55 AM #21Archived author: Kitzunu • Posted: 2024-01-07T02:55:56.548000+00:00
Original source
You said it more kind
Original source
But yea
rektbyfaith
01-07-2024, 02:56 AM #22Archived author: Kitzunu • Posted: 2024-01-07T02:56:01.162000+00:00
Original source
But yea
Original source
Xd
rektbyfaith
01-07-2024, 02:56 AM #23Archived author: Kitzunu • Posted: 2024-01-07T02:56:02.466000+00:00
Original source
Xd
Original source
I don't know the mechanics of the auto updater, I don't even use it honestly, but can't it just loop through archived updates and check if they exist in the updates table just like any other update? Perhaps not all archived updates are stored there though, I have no idea.
rektbyfaith
01-07-2024, 02:56 AM #24Archived author: Revision • Posted: 2024-01-07T02:56:53.204000+00:00
Original source
I don't know the mechanics of the auto updater, I don't even use it honestly, but can't it just loop through archived updates and check if they exist in the updates table just like any other update? Perhaps not all archived updates are stored there though, I have no idea.
Original source
Easiest is just to fix the updater. Which the idea is pretty easy. But implementing it is less easy. Especially since I dont know the structure of the updater. And I am a lazy bastard
rektbyfaith
01-07-2024, 02:57 AM #25Archived author: Kitzunu • Posted: 2024-01-07T02:57:05.713000+00:00
Original source
Easiest is just to fix the updater. Which the idea is pretty easy. But implementing it is less easy. Especially since I dont know the structure of the updater. And I am a lazy bastard
Original source
My idea is that it checks the version table. If theres mismatch it should run through latest archive
rektbyfaith
01-07-2024, 02:58 AM #26Archived author: Kitzunu • Posted: 2024-01-07T02:58:04.891000+00:00
Original source
My idea is that it checks the version table. If theres mismatch it should run through latest archive
Original source
That sounds more reasonable, I realize it doesn't make sense to loop through those archived updates every single time the server starts.
rektbyfaith
01-07-2024, 02:58 AM #27Archived author: Revision • Posted: 2024-01-07T02:58:43.669000+00:00
Original source
That sounds more reasonable, I realize it doesn't make sense to loop through those archived updates every single time the server starts.
Original source
Well run through archive first then updates.
rektbyfaith
01-07-2024, 02:59 AM #28Archived author: Kitzunu • Posted: 2024-01-07T02:59:53.247000+00:00
Original source
Well run through archive first then updates.
Original source
But to implement it I just cba to look into
rektbyfaith
01-07-2024, 03:00 AM #29Archived author: Kitzunu • Posted: 2024-01-07T03:00:04.109000+00:00
Original source
But to implement it I just cba to look into
Original source
But probably just hardcode a version number, check it to the version number in db. If it is less fire away at the archibe
rektbyfaith
01-07-2024, 03:01 AM #30Archived author: Kitzunu • Posted: 2024-01-07T03:01:29.668000+00:00
Original source
But probably just hardcode a version number, check it to the version number in db. If it is less fire away at the archibe
1 Guest(s)
1 Guest(s)