Skip to content

feat(app): Fix well known did config error handling #2262

feat(app): Fix well known did config error handling

feat(app): Fix well known did config error handling #2262

Triggered via pull request November 6, 2023 16:55
Status Failure
Total duration 58m 51s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

build.yml

on: pull_request
Semantic Pull Request Check
4s
Semantic Pull Request Check
iOSFlutterIntegrationTest
33m 6s
iOSFlutterIntegrationTest
AndroidFlutterIntegrationTest
47m 38s
AndroidFlutterIntegrationTest
GenerateVersion
0s
GenerateVersion
PublishJSSDKSnapshot
0s
PublishJSSDKSnapshot
PublishIosSDKSnapshot
0s
PublishIosSDKSnapshot
PublishAndroidSDKSnapshot
0s
PublishAndroidSDKSnapshot
PublishDemoAppSnapshot
0s
PublishDemoAppSnapshot
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 2 warnings
Semantic Pull Request Check
No release type found in pull request title "Fix well known did config error handling ". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/ Available types: - feat: A new feature - fix: A bug fix - docs: Documentation only changes - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) - refactor: A code change that neither fixes a bug nor adds a feature - perf: A code change that improves performance - test: Adding missing tests or correcting existing tests - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm) - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs) - chore: Other changes that don't modify src or test files - revert: Reverts a previous commit
AndroidFlutterIntegrationTest
The hosted runner: GitHub Actions 13 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Semantic Pull Request Check
The following actions uses node12 which is deprecated and will be forced to run on node16: amannn/action-semantic-pull-request@v4. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Semantic Pull Request Check
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/