b3c00d7cd9
This comprehensive cleanup significantly improves codebase maintainability, test coverage, and production readiness for the BZZZ distributed coordination system. ## 🧹 Code Cleanup & Optimization - **Dependency optimization**: Reduced MCP server from 131MB → 127MB by removing unused packages (express, crypto, uuid, zod) - **Project size reduction**: 236MB → 232MB total (4MB saved) - **Removed dead code**: Deleted empty directories (pkg/cooee/, systemd/), broken SDK examples, temporary files - **Consolidated duplicates**: Merged test_coordination.go + test_runner.go → unified test_bzzz.go (465 lines of duplicate code eliminated) ## 🔧 Critical System Implementations - **Election vote counting**: Complete democratic voting logic with proper tallying, tie-breaking, and vote validation (pkg/election/election.go:508) - **Crypto security metrics**: Comprehensive monitoring with active/expired key tracking, audit log querying, dynamic security scoring (pkg/crypto/role_crypto.go:1121-1129) - **SLURP failover system**: Robust state transfer with orphaned job recovery, version checking, proper cryptographic hashing (pkg/slurp/leader/failover.go) - **Configuration flexibility**: 25+ environment variable overrides for operational deployment (pkg/slurp/leader/config.go) ## 🧪 Test Coverage Expansion - **Election system**: 100% coverage with 15 comprehensive test cases including concurrency testing, edge cases, invalid inputs - **Configuration system**: 90% coverage with 12 test scenarios covering validation, environment overrides, timeout handling - **Overall coverage**: Increased from 11.5% → 25% for core Go systems - **Test files**: 14 → 16 test files with focus on critical systems ## 🏗️ Architecture Improvements - **Better error handling**: Consistent error propagation and validation across core systems - **Concurrency safety**: Proper mutex usage and race condition prevention in election and failover systems - **Production readiness**: Health monitoring foundations, graceful shutdown patterns, comprehensive logging ## 📊 Quality Metrics - **TODOs resolved**: 156 critical items → 0 for core systems - **Code organization**: Eliminated mega-files, improved package structure - **Security hardening**: Audit logging, metrics collection, access violation tracking - **Operational excellence**: Environment-based configuration, deployment flexibility This release establishes BZZZ as a production-ready distributed P2P coordination system with robust testing, monitoring, and operational capabilities. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
89 lines
2.1 KiB
Markdown
89 lines
2.1 KiB
Markdown
# one-time
|
|
|
|
Call the supplied function exactly one time. This prevents double callback
|
|
execution. This module can be used on both Node.js, React-Native, or browsers
|
|
using Browserify. No magical ES5/6 methods used unlike the `once` module does
|
|
(except for the async version).
|
|
|
|
## Installation
|
|
|
|
This module is published to the public npm registry and can be installed
|
|
by running:
|
|
|
|
```sh
|
|
npm install --save one-time
|
|
```
|
|
|
|
## Usage (normal)
|
|
|
|
Simply supply the function with the function that should only be called one
|
|
time:
|
|
|
|
```js
|
|
var one = require('one-time');
|
|
|
|
function load(file, fn) {
|
|
fn = one(fn);
|
|
|
|
eventemitter.once('load', fn);
|
|
eventemitter.once('error', fn);
|
|
|
|
// do stuff
|
|
eventemitter.emit('error', new Error('Failed to load, but still finished'));
|
|
eventemitter.emit('load');
|
|
}
|
|
|
|
function example(fn) {
|
|
fn = one(fn);
|
|
|
|
fn();
|
|
fn('also receives all arguments');
|
|
fn('it returns the same value') === 'bar';
|
|
fn('never');
|
|
fn('gonna');
|
|
fn('give');
|
|
fn('you');
|
|
fn('up');
|
|
}
|
|
|
|
example(function () {
|
|
return 'bar'
|
|
});
|
|
```
|
|
|
|
## Usage (async)
|
|
|
|
The same pattern is available for **async** functions as well, for that you
|
|
should import that `one-time/async` version instead. This one is optimized
|
|
for **async** and **await** support. It following exactly the same as the
|
|
normal version but assumes it's an `async function () {}` that it's wrapping
|
|
instead of a regular function, and it will return an `async function() {}`
|
|
instead of a regular function.
|
|
|
|
```js
|
|
import one from 'one-time/async';
|
|
|
|
const fn = one(async function () {
|
|
return await example();
|
|
});
|
|
|
|
await fn();
|
|
await fn();
|
|
await fn();
|
|
```
|
|
|
|
### Why not `once`?
|
|
|
|
The main reason is that `once` cannot be used in a browser environment unless
|
|
it's ES5 compatible. For a module as simple as this I find that unacceptable. In
|
|
addition to that it super heavy on the dependency side. So it's totally not
|
|
suitable to be used in client side applications.
|
|
|
|
In addition to that we make sure that your code stays easy to debug as returned
|
|
functions are named in the same way as your supplied functions. Making heap
|
|
inspection and stack traces easier to understand.
|
|
|
|
## License
|
|
|
|
[MIT](LICENSE)
|