RTB Development

[Chrono]

Just because a new version is coming and in use privately doesn't mean we drop bug support for the latest, public version of it. We still don't know any exact times RTB4 will be ready, so keeping RTB3 working is still a priority.

He already stated that he wont be fixing any problems with the IRC, whether or not he releases any bugfixes for RTB3.

[Ad Bot]

[MegaScientifical]

He already stated that he wont be fixing any problems with the IRC, whether or not he releases any bugfixes for RTB3.

Still doesn't justify such cold insensitivity toward anyone bringing it up, laddy.

[Chrono]

Still doesn't justify such cold insensitivity toward anyone bringing it up, laddy.

Just stating it as it is.

[MegaScientifical]

Just stating it as it is.

Same, same. :)

[-Jetz-]

Just because a new version is coming and in use privately doesn't mean we drop bug support for the latest, public version of it. We still don't know any exact times RTB4 will be ready, so keeping RTB3 working is still a priority.

Should we put the IRC bugs on the list for the next version then?

[PVC Potato Gun]

Should we put the IRC bugs on the list for the next version then?

Why would we when it will be removed in the next version?

[Crown2]

Why would we when it will be removed in the next version?

[-Jetz-]

Why would we when it will be removed in the next version?

Why would we when it will be removed in the next version?

Well done missing the joke, you two.

[Ephialtes]

The primary thing holding RTB4 up at the moment is some sort of bug on v19 osx whereby net objects are somehow causing crashes. To me it looks a bit like a memory corruption type issue but the xcode debugger apparently doesn't work so it's up to me to have a look into it and see if there's anything I can do.

On a side note I've started working on the new API for RTB. It's another ground-up re-design but won't make much difference to anyone for the moment. Initially I'll just be re-doing all the stuff from the old API and streamlining/standardising everything a bit more. Eventually I'll open it up as an actual web API for people to use but that's only once I've decided what it could actually do that people might benefit from.

[Ephialtes]

The primary thing holding RTB4 up at the moment is some sort of bug on v19 osx whereby net objects are somehow causing crashes. To me it looks a bit like a memory corruption type issue but the xcode debugger apparently doesn't work so it's up to me to have a look into it and see if there's anything I can do.

Traced the issue back to some poor handling in the TCPObject::disconnect() engine method which caused the object table to get messed up. Instead of waiting for some engine patch for that I'm going to hack up the RTB networking a bit to avoid it entirely and that should sort it.

[MegaScientifical]

So far, that makes two engine related bugs messing with RTB that I can remember. Will they both be fixed, even if one is being avoided through RTB's network instead? As a precaution, I mean.

[Ephialtes]

As long as my workarounds actually work then I don't have much interest in fixing engine bugs - I doubt Badspot does either.

I'm only going to be hacking this solution into the networking for the moment since I'm planning to rewrite the entire thing at some point to accommodate the new RESTful API which uses JSON as opposed to some weird tab-delimited mess.

[Darkmaster20]

I don't know if this will be fixed in the next beta, Are you going to fix the problem with continuous disconnections?

[Ephialtes]

I haven't heard anything about continuous disconnections. Maybe you should try reporting it like I instructed you to when you signed up for this.

[Blocker Ctgr]

Didn't someone leak the RTB4 Beta?