Migrate PANDA app runtime to Node 22 with validated compatibility boundaries#1
Open
argahsuknesib wants to merge 2 commits intomainfrom
Open
Migrate PANDA app runtime to Node 22 with validated compatibility boundaries#1argahsuknesib wants to merge 2 commits intomainfrom
argahsuknesib wants to merge 2 commits intomainfrom
Conversation
- Introduced a new script `webhook_latency_benchmark.js` to measure and log the latency of webhook responses. - The script supports configuration via environment variables for flexibility in testing different endpoints and parameters. feat: create temporary query registration script - Added `tmp-register-query.js` to register a sample query with the WebSocket server. - This script facilitates testing of query registration functionality. feat: add exact test commands for UMA authorization - Created `EXACT_TEST_COMMANDS.sh` to provide validated curl commands for testing derived resource authorization. - The script includes steps for creating ODRL policies and testing access without tokens. feat: implement live test for derived resource authorization - Added `LIVE_TEST_DERIVED_RESOURCE.sh` to validate the authorization flow for derived resources. - The script checks server availability, creates policies, and verifies access control. feat: add smoke test for UMA authorization - Introduced `smoke.js` to perform a basic smoke test for UMA authorization flows. - The script checks resource accessibility and handles UMA challenges. feat: create TypeScript test for derived policy - Added `test-derived-policy.ts` to automate the creation and validation of ODRL policies for derived resources. - The script fetches UMA configuration and checks for proper policy creation. feat: add derived resource authorization test script - Created `test-derived-resource-authorization.sh` to validate the full authorization flow for derived resources. - The script includes steps for policy creation, ticket extraction, and token exchange. fix: add default UMA claim configuration - Introduced `UmaClaim.ts` to manage default UMA claim token and format. - This ensures consistent claim handling across the application. feat: implement notification topic resolver - Added `NotificationTopicResolver.ts` to resolve notification topics from webhook data. - The function normalizes URLs and extracts relevant topics for processing.
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
1 participant
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.
Migrated PANDA to Node 22 by removing the Node-22-incompatible RDF fetch dependency chain, updating runtime pinning and container config, and restoring a green build on Node 22.
Comparative test runs on Node 20.20.2 and 22.22.2 show the major failing suites are pre-existing and not specific to Node 22.
The PANDA Node 22 migration is complete at the app level, but the ecosystem around it is not fully Node-22-clean.
More precisely:
@solid/community-server -> oidc-provider.Remaining cleanup is therefore not a PANDA app migration issue; it is a larger dependency-stack migration for the Solid/CSS auth layer if we want a fully clean Node 22 story with no warnings and fewer legacy compatibility risks.
Out of scope for this PR: