MsxHub first beta release. Call for help

Page 5/5
1 | 2 | 3 | 4 |

By ducasp

Paladin (669)

ducasp's picture

23-08-2020, 04:56

bsittler wrote:

I use this with GR8NET and it works great to the point of downloading the first file in the package, but when it is about to download the second it says there is a timeout very quickly. When I try with /d it again works for the first file, but for the second exits after printing "invalid connection state". When I fetch the second file using HGET and the MSXHUB API URL printed by /d it works fine and I get the file

Hi bsittler,

KDL recently helped me understand that some providers do not work well with keep alive connections, so there should be a retry for some errors. I'm working on a fix for it, meanwhile, you can use the previous version of HUB that do not have keep alive support, to downgrade it:

HUB UPGRADE HUB:1.0.3-1

If you haven't installed/updated it using hub itself you will get an error message telling hub is not installed, you can try:try

HUB INSTALL HUB:1.0.3-1

And don't update hub until 1.0.5 is released Wink

By bsittler

Master (247)

bsittler's picture

23-08-2020, 05:49

Thank you! Indeed, the older version works fine

By fr3nd

Expert (112)

fr3nd's picture

23-08-2020, 17:49

@ducasp, so it seems that keepalive is giving issues with some providers? I guess you're already working on a fix, right? if not I guess we can just revert the last changes. What do you think?

By ducasp

Paladin (669)

ducasp's picture

23-08-2020, 21:47

It should be available in about a week or so, if you think that rolling back to 1.0.3 is better, I see no issue with that ???? I think most people have no issues with that, what I saw with KdL is that some internet providers close the connection after transfer is done and nothing is commanded on the http channel for a very short period, and MSX takes a little bit to write to disk and that time, before closing the file and starting the next one is enough that the internet provider itself kills the connection (crazy right? This should be between client and server). The fix is an easy one, addba retry in case get fails while keeping alive, and in that case the retry will be without keep alive for the remaining session, need to test it Smile

By fr3nd

Expert (112)

fr3nd's picture

24-08-2020, 09:55

Ok, cool, don't worry. No need to rush... This bug it's been here for months already so few extra days won't hurt Smile

Just wanted to see what would be the best way to fix it. Thank you!

By ducasp

Paladin (669)

ducasp's picture

02-12-2022, 19:29

Guys, sorry for the lack of updates, 1.0.5 was available for quite a while and fixed the situation for users whose internet providers kill keep alive connections on their own... And now 1.0.6 has been released, there is no change to HUB.COM but a new version of HUBG.COM by Israel ( https://github.com/israelferrazaraujo ), the original design of HUBG used fixed size memory structures to hold package information and due to total memory constraints and myself not wanting to require a Mapper or access disk, it was hardcoded with a limit of 70 structures, so up to 70 packages per category would be stored, my guess was that it would take quite a while to have a category with more than 70 packages, and then MSXDEV entries have been added and the actual number of packages in games category is 132 packages!

So, using HUBG, you would list only the first 70, and the remaining 62 wouldn't be listed. Not anymore, thanks to Israel help, he designed a dynamic cache that allocates only the data needed for each entry instead of fixed size, which allows the current 132 entries to be listed... Yeah, I know, at some point we are going to have to resort to a better solution as soon even the dynamic allocation won't be enough, but for now, that is working fine :)

hub upgrade hub is the command to get the latest hubg (if you have hub from hub, if not, hub install hub). Or you can upgrade HUB package in HUBG local window. ;)

Page 5/5
1 | 2 | 3 | 4 |