Usdk-e2e status check; testapp honors redisKeyPrefix - #100
Merged
Conversation
Posts an sdk-e2e commit status: pending on update-wasm-v* bump branches until the schematic-api SDK E2E run reports back, success on every other PR, so sdk-e2e can be a required check without blocking normal PRs. The testapp passes redisKeyPrefix through so the E2E replicator-docs mode runs the README configuration.
The sample app passed the bare replicator URL as the health URL. That is a 404, the SDK read it as not ready, and every replicator-mode flag check fell back to the REST API; the E2E replicator job passed on REST values. The strict replicator E2E mode (SchematicHQ/actions#565) caught it.
Contributor
|
❌ SDK E2E failure for
The |
Contributor
|
❌ SDK E2E failure for
The |
Same fix as the other testapps: the short flag-check TTL on the entity caches expired the replicator-owned company entry after the SDK wrote it back on track, and every later check missed the company.
Contributor
|
✅ SDK E2E success for
The |
schematic-bot
approved these changes
Sep 6, 2026
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
2 participants
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.
For the SDK E2E suite (SchematicHQ/actions#565):
sdk-e2e-status.ymlposts ansdk-e2ecommit status on every PR:pendingonupdate-wasm-v*bump branches until the schematic-api E2E run reports back,successimmediately on anything else. This letssdk-e2ebecome a required check without blocking ordinary PRs.The testapp honors
redisKeyPrefixso the newreplicator-docsE2E mode can run the README configuration.Sample app fix:
withReplicatorMode(replicatorUrl)passed the bare base URL as the health URL. That is a 404, the SDK read it as not ready, and every replicator-mode check fell back to the REST API, so the Java replicator E2E job has only ever tested REST. NowreplicatorUrl + "/ready"like the other testapps. Found by the strict replicator mode in actions#565.Sample app fix: entity caches now keep the SDK default TTL (the other testapps made the same change). The short flag-check TTL on the datastream caches expired the replicator-owned company entry after
trackwrote it back, and every later check loggedCompany not found in cache.Sample app logs the SDK at debug so the E2E job's test app log shows fallbacks and replicator health.