Repository navigation
Conversation
… unit first
Matches the Java and Android release docs: any merge after the HIL run
moves master to a commit with no result. And in the HIL README: the API
looks a BLE unit up by its address, so after a power cycle every BLE item
failed at once ("Windows knows no BLE device") until Windows had scanned
for the unit again.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Docs only, two notes that keep the C# release docs in line with Java and Android:
AGENTS.md, release step 1: run the HIL after the last merge. Any later merge, docs or test code included, movesmasterto a commit with nocsharp-hilresult. The Java and AndroidAGENTS.mdnow say the same (DEV-1393: put the Java HIL first in the release steps Shimmer-Java-Android-API#342, DEV-1393: add a Releasing section that starts with the Android HIL ShimmerAndroidAPI#145).tools/hil/README.md, Setup: BLE needs no pairing, but Windows must have seen the unit advertise. The API looks a BLE unit up by its address, so after a unit is power-cycled every BLE item fails at once withWindows knows no BLE device <mac>until Windows scans again.That was verified with a Windows BLE discovery (
DeviceInformation.FindAllAsyncfor BLE association endpoints), after which the unit connected and streamed. The README suggests the Settings > Add device > Bluetooth search, which I haven't tried on the bench. Making the API scan for the unit itself is tracked separately.Opened after the v1.4.1 release, so merging it doesn't move the commit that release was gated on.
🤖 Generated with Claude Code