Repository navigation
feat(internal): stdout transport - #2213
Merged
Merged
Conversation
|
jpnurmi
added this pull request to stack #2214
October 16, 2026 16:37
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## v1 #2213 +/- ##
==========================================
- Coverage 75.47% 75.25% -0.23%
==========================================
Files 104 105 +1
Lines 29637 29655 +18
Branches 5481 5482 +1
==========================================
- Hits 22369 22316 -53
- Misses 5844 5928 +84
+ Partials 1424 1411 -13 🚀 New features to boost your workflow:
|
The inproc-based Android NDK uses `SENTRY_TRANSPORT=none` and installs a JNI function transport that writes to `outbox/`, leaving HTTP delivery to Java. Tests substitute it with an stdout callback to inspect envelopes without Java or HTTP. However, the Native daemon in #1725 cannot use the function transport from the separate daemon process. Provide (an internal) built-in stdout transport (`SENTRY_TRANSPORT=stdout`) that both the SDK and daemon can instantiate. This is mostly for out own integration testing purposes, but it's also super handy for quick experiments: ```sh $ make build SENTRY_BACKEND=inproc SENTRY_TRANSPORT=stdout ... $ ./build/sentry_example_crash ... [sentry] DEBUG sending envelope {"event_id":"0e1d5355-5ba8-42cb-9e96-c6610d4ee9c1",...} {"type":"event","length":2823} {"event_id":"0e1d5355-5ba8-42cb-9e96-c6610d4ee9c1","timestamp":"2026-10-16T16:19:26.968633Z","platform":"native","level":"fatal","exception":...} [sentry] INFO entering signal handler ... ```
jpnurmi
force-pushed
the
jpnurmi/feat/stdout-transport
branch
from
October 19, 2026 06:47
c5068b8 to
6906c63
Compare
JoshuaMoelans
approved these changes
Oct 19, 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
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.
The inproc-based Android NDK uses
SENTRY_TRANSPORT=noneand installs a JNI function transport that writes tooutbox/, leaving HTTP delivery to Java. Tests substitute it with astdoutcallback to inspect envelopes without Java or HTTP.The Native daemon in #1725, however, cannot use the function transport from a separate daemon process. Provide (an internal) built-in
stdouttransport (SENTRY_TRANSPORT=stdout) that both the SDK and daemon can instantiate. This allows runningtest_integration_stdout.pyfor Native/Android in #1725.The undocumented
stdouttransport is mostly intended for our own integration testing purposes, but it's also handy for quick experiments:#skip-changelog (internal)