Team1

This is caused by the fact that you declare in your config that you need a JobCompletionNotificationListener in following lines:

You can average the points for the 3 prior sprints like this:

if u want to apply diff style on the card depend on the teamId you can achieve that by using ngClass and SCSS

first, on your card add the ngclass

One method uses left join and group by with a having clause:

In C#:

Any time you find yourself writing variables like xxx1 = ... / xxx2 = ... / xxx3 = ..., that can almost always be handled better as a list.

Good news/Bad news...

There is still a little meat left on the bone there that you could trim. You have several loops that are generating redundant elements. The bad news is that the solver usually can detect these and will weed them out, so you may not get much acceleration by trimming them.

3 things...

1. Your constraint that a player must have n_games is redundant because your next constraint forces them to have a game in each round
2. When you are creating your player - pplayer constraints, you are creating many duplicates because you are implicitly ordering p and pp. If the set P has 16 players, then the nested loop will create p*(p-1) constraints of each type, when ignoring p=pp. However, note that there are only C(16,2) logical constraints which is p*(p-1)/2.
3. You are doing similar thing when creating your set of legal games because you are implicitly ordering the legal teams.

Below is a tweaked version of your program.... It is still churning on my machine, so I don't know if any time will be saved. Your other "easy" options are to tinker with an optimality gap or a timeout.

I'll stew on this a bit more... but I'm not sure if there is another novel approach to this.

If the same component is used as the child of multiple s at the same point in the component tree, React will see this as the same component instance and the component’s state will be preserved between route changes. If this isn’t desired, a unique key prop added to each route component will cause React to recreate the component instance when the route changes.

https://reactrouter.com/web/api/Route

You can add the teamName as a key prop on the component, which will tell React to unmount/mount the component when the key value changes.

Your validation logic validates the team after adding the wrong member and then corrects this error. Using this logic, you should always append the new member to the team before performing any validations: