Fastest Switchers in the West

[Sedgistan]

Eluvatar has coded up some changes to the way WA membership is managed behind the scenes. It's got a few benefits to it - allowing us to query the number of WA nations in a region (needed for Frontiers' status switching influence costs), avoiding some of the race conditions at update when players can end up accidentally multying or with ghost WA nations, and also to eventually make it possible to see who a nation has endorsed.

This needs some stress testing, so I need some volunteers who are incredibly fast raiders or defenders to have a go at switching quickly on our other test version of NS (not NS3), to check it works as intended. Please let me know (here, TG or Discord DM) if you're interested in helping out. For those that are taking part in this testing, please also use this thread to post feedback.

If you're not an incredibly fast raider or defender, please don't apply (unless you're an incredibly fast raider and defender from Lily, in which case, please definitely apply).

[Haku]

I'm interested in applying.

[Sedgistan]

I've dropped you a TG. Will do likewise for anyone else who volunteers here who has R/D pedigree.

[Eluvatar]

To be clear, not all the benefits mentioned are realized yet on the test site, but I need the intermediate stage tested first.

[Decacon]

Not volunteering due to my limited R/D credentials, but we (Europeia) have passed this along internally.

Anyway, I just wanted to say - hopefully this data will be exposed to the API! It would help us comply with rate limits, as (for example) a lot of tools right now have to manually query every nation in a region to see if it's WA or not.

[Eluvatar]

Not volunteering due to my limited R/D credentials, but we (Europeia) have passed this along internally.

Anyway, I just wanted to say - hopefully this data will be exposed to the API! It would help us comply with rate limits, as (for example) a lot of tools right now have to manually query every nation in a region to see if it's WA or not.

You can query the WA for its list of members. For the occasional bugged nation, the nations.xml dump should be more than sufficient to catch them as they are few and far between.

[Thorn1000]

I’m happy to help too!

[Haku]

I've experienced something similar to the "race conditions" mentioned in the OP.

I just tried to admit on a WA nation only to be told I already have one and I couldn't find it by dossiering all of my nations, and the activity feed shows that my last nation (Haku 160) definitely resigned properly.

However, I used the members API shard (https://www.nationstates.net/cgi-bin/ap ... &q=members) to look for it, which revealed that my first nation https://www.nationstates2.net/nation=haku is considered to be WA, even though I can look at its nation page and see it's definitely not (logging into the nation also shows no resign WA button)

What's strange is that I noticed it only started blocking me from joining the WA now when my last resign on that nation (or any other nation) was 12 hours ago.

For the record, this isn't quite identical to what I've experienced during update, which is being able to end up with multiple WA nations by the end of a fast chase, but seems similar in nature.

[Eluvatar]

This is very helpful Haku, thank you.

Looks like your problem came because I did something that I didn't know was unsafe and reset the state of the old UN code to before you'd done all your stuff. I'll know not to do that (at least on the actual site / test sites) in the future!

I'll remove that errant record shortly. Edit: You should be able to rejoin the WA on NS2 on any of your puppets now.

[Sweeze]

if bodies are still necessary i'd take an invite

[Sedgistan]

Elu's advised he feels he's seen enough testing to be confident with the new system.

[Eluvatar]

We'll probably need testing for Stage Two around Wednesday or Thursday.

Edit: Stage Two isn't required for Frontiers, but will unlock some of the benefits Sedgistan mentions above.

[Eluvatar]

It's Wednesday/Thursday! Time to test Phase 2.

Telegram me if you don't have access and would like to help out!

[Haku]

Instead of the usual list of WA members, the members API https://www.nationstates2.net/cgi-bin/a ... &q=members currently returns this:

Code: Select all

<WA council="1">
<MEMBERS>ARRAY(0x5566c35a4708)</MEMBERS>
</WA>

[Eluvatar]

Instead of the usual list of WA members, the members API https://www.nationstates2.net/cgi-bin/a ... &q=members currently returns this:

Code: Select all

<WA council="1">
<MEMBERS>ARRAY(0x5566c35a4708)</MEMBERS>
</WA>

Oh heh, I'll fix that shortly

[Bobberino]

Still need a hand?

[Eluvatar]

Still need a hand?

At this point I think additional testers would be best included in Phase 3 testing, a little later on. I'll keep you in mind as a potential volunteer.

[Eluvatar]

I am satisfied with the testing of Phase 2 and have updated the main site with the bugfix I wanted to take care of before releasing Phase 2 here.

Just checking in with other tech admins/mods to make sure things look good and then Phase 2 will be released to nationstates.net shortly.

Edit: Phase 2 is on the main site, and tonight's updaters should see its benefits (and costs) shortly. We may have lost a few telegrams that should've been auto-sent to new / new WA nations, but not many.

[Eluvatar]

I've been made aware that this change is changing the order in which endorsements are displayed on nation pages. Be assured that the underlying order is not lost. I will be correcting the new WA membership validation code to not re-order endorsements now.

Edit: Should be fixed now.

[Fort Concord]

Edit: Should be fixed now.

Sort of?

In the case of Mechanocracy, Fort Handel and Anjan Kloss were the most recently provided endorsement but display mid-way through the list. It's definitely not alphabetical anymore, and from a first glance I don't see an immediate pattern, but it doesn't seem how it typically is.

[The Ambis]

Edit: Should be fixed now.

Sort of?

In the case of Mechanocracy, Fort Handel and Anjan Kloss were the most recently provided endorsement but display mid-way through the list. It's definitely not alphabetical anymore, and from a first glance I don't see an immediate pattern, but it doesn't seem how it typically is.

Has it ever been alphabetical? I thought it was order endorsed

[Fort Concord]

Has it ever been alphabetical? I thought it was order endorsed

It was briefly alphabetical yesterday, which is the problem Eluvatar was referring to above. The normal display is in endorsement order. As of my post you're quoting, neither appeared to be the case to me.

[Eluvatar]

That is very strange. I might not be able to fix it until next week but I will look into it when I can.

[Quebecshire]

Apologies if you've been busy, Elu, but I was wondering if there's been any progress on restoring the normal endorsement display order?

[Eluvatar]

Apologies if you've been busy, Elu, but I was wondering if there's been any progress on restoring the normal endorsement display order?

None yet. There's a solution I could go with that would frustrate me, but I'll try and figure out what's wrong with my fast code and fix it when I can. In the meanwhile the API still shows the correct endorsement order.