RSS feed tests

[Hacker]

Christian,
It does now for me, thank you.

Roman

[white]

I think that line 1197 should be
$requested_forum_ids[] = (int) $pieces[1];
without the substr() code because "explode" above already did the separation.

A changed was committed for exactly that:
https://github.com/MarkDHamill/smartfeed/commit/108895e8df9475b54666614db7d77e572100947b

Background story:
https://github.com/MarkDHamill/smartfeed/commit/3b68877670c762b69a1d49a572fe0d7e76349129

[HolgerK]

The shortened forum names are lost after the update.

Confirmed, I only installed the new extension. I have re-added my changes now.

Works for me too.

Many thanks
Holger

[white]

For the beta, use:
nslookup -type=TXT releasebeta.ghisler.com

Currently it returns "10.9.22.229;1"

The 229 means: Everything above 128 is a beta version.
129 = beta 1,
130 = beta 2
etc.
229 = release candidate 1
230 = release candidate 2
etc.

But releasebeta.ghisler.com now gives "10.11.57.249;1" , which apparently doesn't mean 11.57 rc 21, but 11.57a rc1.
Does that mean the maximum number of release candidates is 20?
And that 249-255 means patch letter "a" and release candidate 1-7?

[ghisler(Author)]

Yes, the last number means the following:
0=regular release, e.g. 10.57
1=a,
2=b etc.
129=beta 1,
130=beta 2 etc;
128+101=RC1,
128+102=RC2 etc
128+121=aRC1,
128+122=aRC2

[white]

Yes, the last number means the following:
0=regular release, e.g. 10.57
1=a,
2=b etc.
129=beta 1,
130=beta 2 etc;
128+101=RC1,
128+102=RC2 etc
128+121=aRC1,
128+122=aRC2

Thanks. My tcdownload.cmd tool doesn't work because AFAIK you never said this. What are the specifications exactly, so I can fix it?

No beta is possible for a version with a patch letter (e.g., 10.57a beta 1)?
Is the max number 255, or can it simply continue?
Is a beta/release candidate also possible for a version with a patch letter "b" and so on (e.g., 10.57b release candidate 1)? If so, what would be the number?

[ghisler(Author)]

These are all possible values.

No beta is possible for a version with a patch letter (e.g., 10.57a beta 1)?

Correct.

Is the max number 255, or can it simply continue?

It's 255, because I used DNS A records (IP addresses) initially, but local addresses got filtered on some DNS servers, so I changed to TXT records.

Is a beta/release candidate also possible for a version with a patch letter "b" and so on

No, it's not possible. It's meant for emergency patches, I would have to use a new full number if I wanted to start a new beta test. But b and c releases have never happened in the past.

[white]

These are all possible values.

Thanks.

I noticed when doing "nslookup -type=TXT releasebeta.ghisler.com" repeatedly, it gives these results:

Code: Select all

        "10.11.57.249;1"
        "10.11.57.0;1"

I then tested using the IP addresses of your name servers and it turns out one of your name servers isn't updated.

[ghisler(Author)]

I then tested using the IP addresses of your name servers and it turns out one of your name servers isn't updated.

Which one?

[white]

Which one?

This one gives the good version:

Code: Select all

D:\>nslookup -type=TXT releasebeta.ghisler.com 168.235.88.148
Server:  UnKnown
Address:  168.235.88.148

releasebeta.ghisler.com text =

        "10.11.57.249;1"
ghisler.com     nameserver = name3.ghisler.com
ghisler.com     nameserver = name2.ghisler.com
ghisler.com     nameserver = name1.ghisler.com
name1.ghisler.com       internet address = 168.235.88.148
name2.ghisler.com       internet address = 168.235.88.148
name3.ghisler.com       internet address = 88.99.192.139

This one is not updated:

Code: Select all

D:\>nslookup -type=TXT releasebeta.ghisler.com 88.99.192.139
Server:  UnKnown
Address:  88.99.192.139

releasebeta.ghisler.com text =

        "10.11.57.0;1"

[white]

Which one?

This one is not updated:

I guess you fixed it, because it's working OK now. Thanks.

[ghisler(Author)]

I updated the timestamp of the primary server, so it seems the secondary now picked up the change.