Bytes test expansion, safer diagnostics, and doc anchors — with realistic JaCoCo gates #713
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



This change lands a focused batch of new tests, a living log/backlog for continuing coverage work, clearer diagnostics when elastic growth fails, and minor documentation/Javadoc clean-ups. It also aligns the
sonarprofile with realistic JaCoCo gates and setsverifyas the default goal there to make reports reproducible.Why
Mapped*and elastic/native paths without churning hot code.verify.What changed
New files
NEW_TESTS.md: brief, running log of tests added this pass (kept in step withTESTS_TODO.md).TESTS_TODO.md: Bytes-specific backlog with commands, completed items, and next batches (safe-page defaults,OS.pageAlignconsumers, etc.).Tests added/extended
MappedFileTest.insideHonoursSafeLimitWhenPageSizeDiffers— validatesMappedBytesStore#insidevssafeLimit()under enlarged page sizes.MappedBytesTest.zeroOutRespectsCustomPageSize— ensureszeroOutclears all bytes when mapping page size > OS default.TempDirectoryIntegrationTest— end-to-endIOTools.createTempDirectoryunderOS.getTarget()with cleanup.ReferenceTracingLeakTest— intentional leak provescreatedHere()is carried into diagnostics and surfaces viaassertReferencesReleased().DecoratedBufferOverflowExceptionTest— documents null-cause semantics (null ≡ no cause).NativeBytesOverflowTest#overflowWithoutTracingKeepsCauseNull— when tracing is off, DBOE keepscause == null.BytesLifecycleTest,BytesCopyMatrixTest,UncheckedBytesBehaviourTest#uncheckedModeAllowsWritePastLimit.Code & diagnostics
NativeBytes.newDBOE(..)now attaches the allocation stack (createdHere()) when available; falls back to a plain message if tracing is disabled. Improves triage without changing hot-path behaviour.NativeBytes#resize: raise the “large allocation” signal to MiB granularity (less noise; clearer human output).Docs
memory-management.adoc: explains howcreatedHere()feedsDecoratedBufferOverflowException(ties toCB-NF-O-006), and the safe fallback when tracing is disabled.project-requirements.adoc: adds stable anchors ([[ID]]) for all CB IDs and a newCB-NF-MP-006(dual-JDK matrix: legacy JDK 8 and latest/EA e.g. JDK 25).architecture-overview.adoc: referencesCB-NF-MP-006.Javadoc/style hygiene (no behavioural change)
@Overrideplacement across several classes (MappedBytesStore,StreamingOutputStream,UncheckedBytes*,SingleMappedFile,CommonMappedBytes,NoBytesStore,Unmapper,UnsafeText, etc.) to satisfy style/Checkstyle and keep docs crisp.Build & quality gates
pom.xml(sonarprofile):defaultGoaltoverifyfor predictable report generation.