whitehouse / fortyfour Goto Github PK

I recommend replacing it completely. At first I was thinking it might be a bug in the database not properly storing all records, but the total shutdown issue sounds more like a hardware issue. The system appears to be not storing data and repeating past problems that clearly should be stored. With all these bugs, i suggest replacing the hardware first before we spend too much time trying to fix all these individual issues. We might waste a lot of time trying to hunt down bugs that can't be fixed with the current system.

The following following states cost more than they contribute, and continue to elect representatives who are dangerously unqualified for the job. They are obsolete and should be removed from the union.

1. Virginia
2. Alaska
3. Kentucky
4. New Mexico

Where can I download SixteenHundredNav, which is a dependency of this theme?

I found the coding error. It’s an infinite loop. Funny does not matter what party is in charge we always lose.

Government.Local.Start();
Government.State.Start();

switch(Congress){
case Majority.Republican:
while(Obama.HealthCare.Pending){
Obama.HealthCare.Stall();
}
break;
case Majority.Democrate:
while(FederalReserve.Lend) < -- resharper states this is always true!!! WTF.{
Government.Debt.Raise += 1,000,000,000,000;
}
break;
}

Government.Federal.Budget.Pass();
Government.Federal.Start();

Replace switch with

Government.Replace(IQ.GreaterThan.Eighty);

This should clear things up.

Copied from usds/website#45

Is this the spot to report layout issues on whitehouse.gov/contact/presidential-greetings-request?

.textcaptcha-challenge-description needs background-position: left set for Challenge Question star:

(Aside: captcha text reads kind of strange in some cases.)

The sales team are really mad. They were trying to sell this system of government to the rest of the world but now it looks like this bug will make customers look elsewhere for a working version.

Not only does our ElectionChoices enum have only 2 elements, but they also both evaluate to 0, which I'm certain leads to many other bugs that have been observed. It also makes them very hard to fix. If we added some additional choices into the enum, and ones that were actually different from each other we can at least have a chance at debugging it.

Child process running out of control need to be reaped.

I noticed a bug over the past week or so and it seems reproducible:

1. Go to U.S. Government.
2. U.S. Government is shut down.

Expected results: Government should be working.

I'm unable to debug or propose a fix since there's not an open, transparent stack trace. Conflicting error messages are being thrown as well.

Hope you can resolve this soon. It would seem that the U.S. Government would value 100% uptime in order to be a reliable and trustworthy source for the rest of the world.

Thanks! Love this project and would like to continue using it.

The geospatial shard keys for house districts are poorly distributed and causing indirect performance problems throughout the app. There's one particular "hot spot" server right now where you can observe the delay.

Members of the House and Senate classes are too private. I suggest making them public so other classes can access and change them if needed. Furthermore, their deconstructor method should also be made public.

As a bonus improvement, since both classes above break the Singleton pattern by extending their parent Congress, the Congress class should no longer be a Singleton.

Willing to fork project, but don't have the time to commit. Will still contribute to it by placing votes.

Due to recent flood of issues a recommend that the core team would drop everything and start from scratch building this "app".

BlackHouse website when