 b3c00d7cd9
			
		
	
	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>
		
			
				
	
	
		
			172 lines
		
	
	
		
			4.8 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
			
		
		
	
	
			172 lines
		
	
	
		
			4.8 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
| # @nodelib/fs.scandir
 | |
| 
 | |
| > List files and directories inside the specified directory.
 | |
| 
 | |
| ## :bulb: Highlights
 | |
| 
 | |
| The package is aimed at obtaining information about entries in the directory.
 | |
| 
 | |
| * :moneybag: Returns useful information: `name`, `path`, `dirent` and `stats` (optional).
 | |
| * :gear: On Node.js 10.10+ uses the mechanism without additional calls to determine the entry type. See [`old` and `modern` mode](#old-and-modern-mode).
 | |
| * :link: Can safely work with broken symbolic links.
 | |
| 
 | |
| ## Install
 | |
| 
 | |
| ```console
 | |
| npm install @nodelib/fs.scandir
 | |
| ```
 | |
| 
 | |
| ## Usage
 | |
| 
 | |
| ```ts
 | |
| import * as fsScandir from '@nodelib/fs.scandir';
 | |
| 
 | |
| fsScandir.scandir('path', (error, stats) => { /* … */ });
 | |
| ```
 | |
| 
 | |
| ## API
 | |
| 
 | |
| ### .scandir(path, [optionsOrSettings], callback)
 | |
| 
 | |
| Returns an array of plain objects ([`Entry`](#entry)) with information about entry for provided path with standard callback-style.
 | |
| 
 | |
| ```ts
 | |
| fsScandir.scandir('path', (error, entries) => { /* … */ });
 | |
| fsScandir.scandir('path', {}, (error, entries) => { /* … */ });
 | |
| fsScandir.scandir('path', new fsScandir.Settings(), (error, entries) => { /* … */ });
 | |
| ```
 | |
| 
 | |
| ### .scandirSync(path, [optionsOrSettings])
 | |
| 
 | |
| Returns an array of plain objects ([`Entry`](#entry)) with information about entry for provided path.
 | |
| 
 | |
| ```ts
 | |
| const entries = fsScandir.scandirSync('path');
 | |
| const entries = fsScandir.scandirSync('path', {});
 | |
| const entries = fsScandir.scandirSync(('path', new fsScandir.Settings());
 | |
| ```
 | |
| 
 | |
| #### path
 | |
| 
 | |
| * Required: `true`
 | |
| * Type: `string | Buffer | URL`
 | |
| 
 | |
| A path to a file. If a URL is provided, it must use the `file:` protocol.
 | |
| 
 | |
| #### optionsOrSettings
 | |
| 
 | |
| * Required: `false`
 | |
| * Type: `Options | Settings`
 | |
| * Default: An instance of `Settings` class
 | |
| 
 | |
| An [`Options`](#options) object or an instance of [`Settings`](#settingsoptions) class.
 | |
| 
 | |
| > :book: When you pass a plain object, an instance of the `Settings` class will be created automatically. If you plan to call the method frequently, use a pre-created instance of the `Settings` class.
 | |
| 
 | |
| ### Settings([options])
 | |
| 
 | |
| A class of full settings of the package.
 | |
| 
 | |
| ```ts
 | |
| const settings = new fsScandir.Settings({ followSymbolicLinks: false });
 | |
| 
 | |
| const entries = fsScandir.scandirSync('path', settings);
 | |
| ```
 | |
| 
 | |
| ## Entry
 | |
| 
 | |
| * `name` — The name of the entry (`unknown.txt`).
 | |
| * `path` — The path of the entry relative to call directory (`root/unknown.txt`).
 | |
| * `dirent` — An instance of [`fs.Dirent`](./src/types/index.ts) class. On Node.js below 10.10 will be emulated by [`DirentFromStats`](./src/utils/fs.ts) class.
 | |
| * `stats` (optional) — An instance of `fs.Stats` class.
 | |
| 
 | |
| For example, the `scandir` call for `tools` directory with one directory inside:
 | |
| 
 | |
| ```ts
 | |
| {
 | |
| 	dirent: Dirent { name: 'typedoc', /* … */ },
 | |
| 	name: 'typedoc',
 | |
| 	path: 'tools/typedoc'
 | |
| }
 | |
| ```
 | |
| 
 | |
| ## Options
 | |
| 
 | |
| ### stats
 | |
| 
 | |
| * Type: `boolean`
 | |
| * Default: `false`
 | |
| 
 | |
| Adds an instance of `fs.Stats` class to the [`Entry`](#entry).
 | |
| 
 | |
| > :book: Always use `fs.readdir` without the `withFileTypes` option. ??TODO??
 | |
| 
 | |
| ### followSymbolicLinks
 | |
| 
 | |
| * Type: `boolean`
 | |
| * Default: `false`
 | |
| 
 | |
| Follow symbolic links or not. Call `fs.stat` on symbolic link if `true`.
 | |
| 
 | |
| ### `throwErrorOnBrokenSymbolicLink`
 | |
| 
 | |
| * Type: `boolean`
 | |
| * Default: `true`
 | |
| 
 | |
| Throw an error when symbolic link is broken if `true` or safely use `lstat` call if `false`.
 | |
| 
 | |
| ### `pathSegmentSeparator`
 | |
| 
 | |
| * Type: `string`
 | |
| * Default: `path.sep`
 | |
| 
 | |
| By default, this package uses the correct path separator for your OS (`\` on Windows, `/` on Unix-like systems). But you can set this option to any separator character(s) that you want to use instead.
 | |
| 
 | |
| ### `fs`
 | |
| 
 | |
| * Type: [`FileSystemAdapter`](./src/adapters/fs.ts)
 | |
| * Default: A default FS methods
 | |
| 
 | |
| By default, the built-in Node.js module (`fs`) is used to work with the file system. You can replace any method with your own.
 | |
| 
 | |
| ```ts
 | |
| interface FileSystemAdapter {
 | |
| 	lstat?: typeof fs.lstat;
 | |
| 	stat?: typeof fs.stat;
 | |
| 	lstatSync?: typeof fs.lstatSync;
 | |
| 	statSync?: typeof fs.statSync;
 | |
| 	readdir?: typeof fs.readdir;
 | |
| 	readdirSync?: typeof fs.readdirSync;
 | |
| }
 | |
| 
 | |
| const settings = new fsScandir.Settings({
 | |
| 	fs: { lstat: fakeLstat }
 | |
| });
 | |
| ```
 | |
| 
 | |
| ## `old` and `modern` mode
 | |
| 
 | |
| This package has two modes that are used depending on the environment and parameters of use.
 | |
| 
 | |
| ### old
 | |
| 
 | |
| * Node.js below `10.10` or when the `stats` option is enabled
 | |
| 
 | |
| When working in the old mode, the directory is read first (`fs.readdir`), then the type of entries is determined (`fs.lstat` and/or `fs.stat` for symbolic links).
 | |
| 
 | |
| ### modern
 | |
| 
 | |
| * Node.js 10.10+ and the `stats` option is disabled
 | |
| 
 | |
| In the modern mode, reading the directory (`fs.readdir` with the `withFileTypes` option) is combined with obtaining information about its entries. An additional call for symbolic links (`fs.stat`) is still present.
 | |
| 
 | |
| This mode makes fewer calls to the file system. It's faster.
 | |
| 
 | |
| ## Changelog
 | |
| 
 | |
| See the [Releases section of our GitHub project](https://github.com/nodelib/nodelib/releases) for changelog for each release version.
 | |
| 
 | |
| ## License
 | |
| 
 | |
| This software is released under the terms of the MIT license.
 |