Adding support for builtin providers and deferring builtin logging to the OTP host #592
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.
Feature or Problem
Version 0.62 does not currently emit any information when actors log using the builtin capability provider. This adds that support back in a way that is compatible with previous hosts.
Related Issues
This supercedes @rvolosatovs 's PR #591 because, in all honesty, I couldn't figure out how to make a PR off of his PR and didn't have rights to force push to his PR
Release Information
0.62
Consumer Impact
All deployments of wasmCloud relying on actor log emissions with or without structured host logging.
Testing
There is an explicit actor test for performing logging and random number generation to exercise the builtins
Built on platform(s)
Tested on platform(s)
Unit Test(s)
test/host_core/actors_test.exs:639
is the test that exercises builtins (including logging). This test passes and produces the expected output in stdout.Acceptance or Integration
Manual Verification
Manually verified this works as well as unit tested using the "rando logger" actor.
Log emissions look as follows: