Bug: Default log level too high

[RickP]

No description provided.

[black-puppydog]

Usually you would make sure this kind of project runs on a system that cleanly separates the concerns of the processes so no process can access the memory or resources held by another process (except on very well-defined occasions, but then the end-user would have to be notified and give consent).
In this branch it seems however that the process boundaries have been blurred over time to make debugging easier (for the developers that is).
Ususally a good way would be to revert to a previous (known-to-work) state but since there have been other commits mingled with the faulty/critical ones that might not be a good idea. Anyway, this seems to be an issue to step back and have a look at the overall design of the system.

[jared-hardy]

The Court.FISA authentication dependency in this logging system is completely and irreparably broken. Please rewrite or change to an existing globally accepted Court method.

[dasmb]

Court.FISA does not publish a public API. There is some evidence that a mock version of the court slipped into production, but as this is a protected assembly it is impossible to know what is really implemented. Certainly all public methods throw UnsupportedOperation or AccessDenied exceptions. This is why many developers prefer open systems -- while there is some question of their performance vs. private implementations, this is mostly FUD and the peace of mind provided is often worth the trade off.