Integrate BACKBEAT SDK and resolve KACHING license validation
Major integrations and fixes: - Added BACKBEAT SDK integration for P2P operation timing - Implemented beat-aware status tracking for distributed operations - Added Docker secrets support for secure license management - Resolved KACHING license validation via HTTPS/TLS - Updated docker-compose configuration for clean stack deployment - Disabled rollback policies to prevent deployment failures - Added license credential storage (CHORUS-DEV-MULTI-001) Technical improvements: - BACKBEAT P2P operation tracking with phase management - Enhanced configuration system with file-based secrets - Improved error handling for license validation - Clean separation of KACHING and CHORUS deployment stacks 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
19
vendor/github.com/ipfs/go-datastore/autobatch/README.md
generated
vendored
Normal file
19
vendor/github.com/ipfs/go-datastore/autobatch/README.md
generated
vendored
Normal file
@@ -0,0 +1,19 @@
|
||||
# autobatch
|
||||
|
||||
Autobatch is an implementation of
|
||||
[go-datastore](https://github.com/ipfs/go-datastore) that automatically batches
|
||||
together writes by holding puts in memory until a certain threshold is met.
|
||||
This can improve disk performance at the cost of memory in certain situations.
|
||||
|
||||
## Usage
|
||||
|
||||
Simply wrap your existing datastore in an autobatching layer like so:
|
||||
|
||||
```go
|
||||
bds := NewAutoBatching(basedstore, 128)
|
||||
```
|
||||
|
||||
And make all future calls to the autobatching object.
|
||||
|
||||
## License
|
||||
MIT
|
||||
Reference in New Issue
Block a user