https://github.com/FAForever/website/pull/540

should be fixed now, we still have issues with cache not getting purged (5min ttl), but it's working

we will likely release to prod tomorrow, so you can invite members during the WE.
let me know if there are any issues if you do so.

@immortal-d said in Clan Management still down?:

Lastly, some feature requests. I would like to see others members able to create an invitation link, possibly setup roles that mirror my Discord server. Having separate text blocks for rules-about-links would also help fill out the page and keep it organized.

there is already a ticket for that, but this will not be implemented fast https://github.com/FAForever/website/issues/372

@immortal-d said in Clan Management still down?:

The 'update/description' menu does not work. I'm kicked back with 'Error! Please add a description for your clan

The message is misleading... did you go over 1k characters? i'll create ticket to update the message

@immortal-d said in Clan Management still down?:

Having separate text blocks for rules-about-links would also help fill out the page and keep it organized.

would you provide a simple scribble for that? how should it look and work etc.
You can always create a new ticket for features here: https://github.com/FAForever/website/issues

PS: transfer leadership is not implemented

@Immortal-D released a test-version for the new clan management on https://www.faforever.xyz/
you and your friends could test it there (usernames are the same and PW for all accounts is "foo")
would be nice if you could give me some feedback and maybe find bugs.

Update: Lists and View are working again
https://faforever.com/clans

Update:
the "new" way to communicate to the server is done, in other terms: we can start fixing the clan-pages
first will be "show all clans" and "show single clan", after that is released we take a break and look if the other pages are even worth to "fix" or just refactor them completely.

Example:

1. Clan invitations are invalidated on server restart (that will happen often in the next time)
2. The code is not testable, so we have to check it manually every time, or miss if something breaks.
3. complicated to maintain due old code that can't be understand easily
4. error-management -> some errors are not show to the user (invite did not work etc.)
5. some feature wishes that would help the clan experience

this is a hard decision, but i think "refactoring" so it can be used and maintained is better than "just" quick-fix it.
If there is someone, who is willing to quick-fix it, pull-request on the repository are welcome (you can also ping me in discord if you need help)

Looking at the current situation, i think clan invite/kick will be available in about 7 days, but don't hate me if not.

takes longer than expected, i can't really give you a date, but updates will be shown here: https://github.com/FAForever/website
if there is any nodejs dev here, i could use a hand

How often did i had to decide between tmm and custom, but in reality i just wanna start a game regardless of the map/type, maybe i had a favorite, but was also willing to play another map during non-peak-hours.

What if we open up the possibility to create one-time queue-able customs to all players?

Simplified flow:

1. Select a name, map, mods, restrictions, rating-range, min game quality etc.
2. Publish the game to the server/other players
3. You can join multiple lobbies, but only "host" one or two?
4. Lobby will be active till started or empty
5. Rating could be applied to global

@DGun you could just open up that 1v1 with all your desired configs and still be in queue.

Would love to get your opinion about that

Since this issue pops up every now and then:
https://github.com/FAForever/faf-user-service/pull/185

found a feature that would close this issue, but don't know the state.
https://github.com/FAForever/downlords-faf-client/issues/1783
https://github.com/FAForever/server/issues/607

Since this is already ongoing for 3 years, i doubt it would be implemented fast.

When i stop searching for a game, sometimes it will start a game without the faf-client says i am in queue.
Is this already known?
Could be related to https://github.com/FAForever/downlords-faf-client/issues/2830

Thx for the Post Mortem!

What i would suggest:

1. Make "critical" changes when you guys have time to monitor/support, even if that means ppl cannot play (once a week to balance it out?)
   -- There is always something that needs attentions after an update

2. It would be nice if we got any info about the current state (Discord), some players could start games where others could not and nobody was saying "we know about issues and we are on it, we will post an update in x hours"

3. Give the http-client a lil love, it's creating so many issues if the server is not responding/behaving as expected.

• noticed that when the replay server was not available, it crashed the client bc. of an unhandled exception.

PS: You guys still looking for support to migrate?

Happened again that the faf-client was exhausting the 150GB virtual memory.
How should i proceed with this? i can't reproduce this reliable , but it happens every 1-3 days.
Can also create a new post, since op is not replying and i don't know if he also got this virtual memory issue

@Eternal munch munch 150GB

Hello,

also got this symptom that the faf-client often gets unresponsive (nothing is clickable or getting black if scaled), and also crashing my PC mid-game.
When i managed to start a game, the errors shown in the game-log often include something with:

warning: c:\work\rts\main\code\src\libs\gpggal\DeviceD3D9.cpp(937) Device lost

This is also only a symptom imo, because it's not always the case. Memory-issues always producing wild errors, therefore i would not focus on that.

A quick analysis from windows-log showing:

Windows hat diagnostiziert, dass der virtuelle Speicher unzureichend ist. Die folgenden Programme belegten den meisten virtuellen Speicher: faf-client.exe (10364) belegt 151689928704 Bytes, ForgedAlliance.exe (6160) belegt 935206912 Bytes und explorer.exe (6980) belegt 438464512 Bytes.

Translation: windows has no virtual memory left bc. faf-client is using 150 GB virtual memory after ~45min.

Unresponsive faf-client and the memory-leak could be unrelated, but i doubt that.
Before i make any other assumptions that are misleading, here the logs:

client.log
game_18296619.log
game_18287975.log

Thanks for your help.