Repository navigation
Conversation
…/http/coroutine_federated_start_http.hpp)
…/http/coroutine_federated_start_http.cpp)
…p/CMakeLists.txt)
…(src/gateway/gateway.cppm)
…(src/gateway/gateway.cpp)
…(tests/gateway/gateway_test.cpp)
…omic session issue
…src/authentication/http/CMakeLists.txt)
…apps/opp/main.cpp)
…nd replay rejection
…llbacks (apps/opp/main.cpp)
…llbacks (docs/CONFIGURATION.md)
…llbacks (src/authentication/http/coroutine_federated_callback_http.cpp)
…llbacks (tests/authentication/coroutine_service_test.cpp)
…rsions under GCC16
…te execution symbols
…for account coroutine TU
…rprise coroutine test
….JSON implementation
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.
Scope (feature branch targeting Coroutine migration)
AuthenticationService::beginAsync/completeAsync, PostgreSQL-backed native transaction finalizer andCoroutineReplacingSessionIssuerfor atomic browser session issue/replacement.OPENPROOF_FARCASTER_TRUSTED_LOOPBACK_RPC=1with a literalhttps://127.0.0.1:<port>/and a separately configured CA file permits loopback for the Farcaster RPC. Domain names and other private IP addresses remain forbidden; wallet and other HTTP clients remain public-only.Current evidence (20 November 2026)
e9ecc8353c0df899db18a50911df582b85b46af9: successfully built and linkedopenproof_account_coroutine_http_tests,openproof_enterprise_coroutine_http_tests, andopenproof_authentication_coroutine_tests. Ranctest -R '^(NativeAccountSession|NativeEnterpriseLdapHttp|TrustedAsyncAuth)' --output-on-failure --parallel 1: 30/30 PASS, including real TCP Federated Start→Callback→Session tests, replay rejection and fail-closed tests. Ran seven focused concurrency/federation tests withctest --repeat until-fail:30: 210/210 successful executions; ran both auth contract/security JS suites: 11/11 PASS and checked E2E JavaScript syntax.git diff --checkandpython3 scripts/check-protocol-neutrality.pypass.src/account/http/boost_json.cpptranslation unit to that test target ine9ecc83. The local focused build and 30 tests above confirm that linker fix. CI #203 is pending, and full CI CTest has not yet passed.oppexecutable and passed the disposable PostgreSQL/Farcaster HTTPS fixture E2E; however, this does not demonstrate native federated callback + real-provider + PostgreSQL E2E, since the native flags are disabled by default. Full end-to-end release acceptance remains outstanding.mainnor production was changed. No production deployment or release approval is permitted based on these tests.