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:
		
							
								
								
									
										27
									
								
								vendor/go.etcd.io/bbolt/internal/common/unsafe.go
									
									
									
										generated
									
									
										vendored
									
									
										Normal file
									
								
							
							
						
						
									
										27
									
								
								vendor/go.etcd.io/bbolt/internal/common/unsafe.go
									
									
									
										generated
									
									
										vendored
									
									
										Normal file
									
								
							| @@ -0,0 +1,27 @@ | ||||
| package common | ||||
|  | ||||
| import ( | ||||
| 	"unsafe" | ||||
| ) | ||||
|  | ||||
| func UnsafeAdd(base unsafe.Pointer, offset uintptr) unsafe.Pointer { | ||||
| 	return unsafe.Pointer(uintptr(base) + offset) | ||||
| } | ||||
|  | ||||
| func UnsafeIndex(base unsafe.Pointer, offset uintptr, elemsz uintptr, n int) unsafe.Pointer { | ||||
| 	return unsafe.Pointer(uintptr(base) + offset + uintptr(n)*elemsz) | ||||
| } | ||||
|  | ||||
| func UnsafeByteSlice(base unsafe.Pointer, offset uintptr, i, j int) []byte { | ||||
| 	// See: https://github.com/golang/go/wiki/cgo#turning-c-arrays-into-go-slices | ||||
| 	// | ||||
| 	// This memory is not allocated from C, but it is unmanaged by Go's | ||||
| 	// garbage collector and should behave similarly, and the compiler | ||||
| 	// should produce similar code.  Note that this conversion allows a | ||||
| 	// subslice to begin after the base address, with an optional offset, | ||||
| 	// while the URL above does not cover this case and only slices from | ||||
| 	// index 0.  However, the wiki never says that the address must be to | ||||
| 	// the beginning of a C allocation (or even that malloc was used at | ||||
| 	// all), so this is believed to be correct. | ||||
| 	return (*[pageMaxAllocSize]byte)(UnsafeAdd(base, offset))[i:j:j] | ||||
| } | ||||
		Reference in New Issue
	
	Block a user
	 anthonyrawlins
					anthonyrawlins