Invision Community 4.6.0 Beta 1 released

[Pete]

I'd assume the issue in question was the result of trying to offload the TLS decryption off to the GPU (because it'll do it faster and with less energy consumption than the CPU doing it) and going wayward as a result.

 

[zappaDPJ]

I'd assume the issue in question was the result of trying to offload the TLS decryption off to the GPU (because it'll do it faster and with less energy consumption than the CPU doing it) and going wayward as a result.

That sounds about right

 

[Zelda]

I'd assume the issue in question was the result of trying to offload the TLS decryption off to the GPU (because it'll do it faster and with less energy consumption than the CPU doing it) and going wayward as a result.

Any clue on why this only happens on Windows?

 

[Pete]

Likely because Linux has a sane networking stack that doesn't try to cut odd corners for 'performance'.

Though possibly we should consider splitting the topic

 

[KimmiKat]

Might be a good idea sing the FF thing got more attention then another mboard software update thing.

Likely because Linux has a sane networking stack that doesn't try to cut odd corners for 'performance'.

Though possibly we should consider splitting the topic

 

[Pete]

Getting this back on track, I am mildly annoyed at myself now for making my test install ips44.domain.com because I can't change it to just ips.domain.com... but the Docker container is currently building so I can play around with IPS 4.6!

 

[Taylor J]

Getting this back on track, I am mildly annoyed at myself now for making my test install ips44.domain.com because I can't change it to just ips.domain.com... but the Docker container is currently building so I can play around with IPS 4.6!

You've just reminded me I need to figure out and get a Docker instance up and going for both IPS and XF (after i renew my IPS license)

 

[Pete]

So one thing I will point out - if you are like me and run Linux containers on Windows, you're going to probably have an unfortunate time: I did the install without realising I was installing a fresh 4.5 (stable) and it ground itself to a pretty hefty halt upgrading to 4.6 - we'd gotten to the 'upgrade the database' step before it timed out, and whatever it did in that phase where it timed out, it jammed up the entire installation where nothing would obviously unjam it. At least, I hit refresh a couple of times so presumably it couldn't resolve where it got to in the process and tangled itself up in so doing.

I'm not fluent enough in IPS to unpick what went wrong, nor do I really care - I nuked it and reinstalled from the 4.6 install package and it was fine, but that's something to consider: if ignore_user_abort() wasn't on (and I get the impression it wasn't), the process would have continued in spite of the 504 error I got - I have a local nginx in front of all the Docker containers so it has 1 minute to complete the job before nginx gives up - and if ignore_user_abort() isn't set, that'll terminate the process too.

I bring this up because Linux containers on Windows have some *serious* disk overheads, like a couple of hundred file_exists calls from Composer's autoloader weighs in at half a second levels of overheads, and this is almost certainly what screwed up the upgrade. (Install doesn't, by comparison, run afoul of this specific problem, and neither would a CLI tool.)

This is not an IPS problem and I'm not going to report it as a bug because I think it's self inflicted - but it might be food for thought for people running their test site on something equally potato-like as I do for whatever reason.