Skip to content

Update dependency ReactiveUI.WPF to v23 #8775

Update dependency ReactiveUI.WPF to v23

Update dependency ReactiveUI.WPF to v23 #8775

Triggered via pull request May 4, 2026 21:38
Status Failure
Total duration 10m 59s
Artifacts 3

ci.yml

on: pull_request
Matrix: containers / containers
db-container  /  db-container
51s
db-container / db-container
windows-installers  /  build
3m 22s
windows-installers / build
Matrix: build
Matrix: container-test / container-test
Fit to window
Zoom out
Zoom in

Annotations

105 errors and 10 warnings
windows-installers / build
Process completed with exit code 1.
windows-installers / build: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
windows-installers / build: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
windows-installers / build: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
windows-installers / build: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Linux-PrimaryRavenAcceptance
Process completed with exit code 1.
Linux-PrimaryRavenAcceptance: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Linux-PrimaryRavenAcceptance: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Linux-PrimaryRavenAcceptance: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Linux-PrimaryRavenAcceptance: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Linux-IBMMQ
Process completed with exit code 1.
Linux-IBMMQ: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Linux-IBMMQ: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Linux-IBMMQ: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Linux-IBMMQ: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Windows-SqlServer
Process completed with exit code 1.
Windows-SqlServer: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Windows-SqlServer: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Windows-SqlServer: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Windows-SqlServer: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Windows-SQS
Process completed with exit code 1.
Windows-SQS: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Windows-SQS: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Windows-SQS: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Windows-SQS: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Linux-Default
Process completed with exit code 1.
Linux-Default: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Linux-Default: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Linux-Default: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Linux-Default: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Linux-AzureStorageQueues
Process completed with exit code 1.
Linux-AzureStorageQueues: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Linux-AzureStorageQueues: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Linux-AzureStorageQueues: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Linux-AzureStorageQueues: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Windows-AzureServiceBus
Process completed with exit code 1.
Windows-AzureServiceBus: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Windows-AzureServiceBus: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Windows-AzureServiceBus: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Windows-AzureServiceBus: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Linux-AzureServiceBus
Process completed with exit code 1.
Linux-AzureServiceBus: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Linux-AzureServiceBus: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Linux-AzureServiceBus: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Linux-AzureServiceBus: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Linux-PostgreSQL
Process completed with exit code 1.
Linux-PostgreSQL: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Linux-PostgreSQL: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Linux-PostgreSQL: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Linux-PostgreSQL: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Windows-MSMQ
Process completed with exit code 1.
Windows-MSMQ: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Windows-MSMQ: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Windows-MSMQ: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Windows-MSMQ: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Windows-AzureStorageQueues
Process completed with exit code 1.
Windows-AzureStorageQueues: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Windows-AzureStorageQueues: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Windows-AzureStorageQueues: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Windows-AzureStorageQueues: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Windows-PostgreSQL
Process completed with exit code 1.
Windows-PostgreSQL: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Windows-PostgreSQL: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Windows-PostgreSQL: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Windows-PostgreSQL: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Linux-PrimaryRavenPersistence
Process completed with exit code 1.
Linux-PrimaryRavenPersistence: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Linux-PrimaryRavenPersistence: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Linux-PrimaryRavenPersistence: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Linux-PrimaryRavenPersistence: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Linux-RabbitMQ
Process completed with exit code 1.
Linux-RabbitMQ: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Linux-RabbitMQ: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Linux-RabbitMQ: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Linux-RabbitMQ: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Linux-SQS
Process completed with exit code 1.
Linux-SQS: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Linux-SQS: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Linux-SQS: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Linux-SQS: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Linux-SqlServer
Process completed with exit code 1.
Linux-SqlServer: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Linux-SqlServer: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Linux-SqlServer: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Linux-SqlServer: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Windows-PrimaryRavenPersistence
Process completed with exit code 1.
Windows-PrimaryRavenPersistence: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Windows-PrimaryRavenPersistence: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Windows-PrimaryRavenPersistence: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Windows-PrimaryRavenPersistence: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Windows-Default
Process completed with exit code 1.
Windows-Default: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Windows-Default: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Windows-Default: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Windows-Default: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Windows-RabbitMQ
Process completed with exit code 1.
Windows-RabbitMQ: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Windows-RabbitMQ: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Windows-RabbitMQ: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Windows-RabbitMQ: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Windows-PrimaryRavenAcceptance
Process completed with exit code 1.
Windows-PrimaryRavenAcceptance: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Windows-PrimaryRavenAcceptance: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
Windows-PrimaryRavenAcceptance: src/ServiceControl.Config/AppBootstrapper.cs#L48
The name 'RxApp' does not exist in the current context
Windows-PrimaryRavenAcceptance: src/ServiceControl.Config/AppBootstrapper.cs#L46
The name 'RxApp' does not exist in the current context
db-container / db-container
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
containers / servicecontrol
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
containers / servicecontrol-monitoring
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
containers / servicecontrol-audit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
container-test / mssql
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/login-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
container-test / sqs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/login-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
container-test / postgresql
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/login-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
container-test / rabbit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/login-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
container-test / asq
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/login-action@v3.7.0, Particular/setup-azurestorage-action@v2.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
container-test / asb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/login-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
Particular~ServiceControl~4NW129.dockerbuild
92.4 KB
sha256:752c24ac16cc8d63416871b029cb329902074f4938909bf683852030f584ed79
Particular~ServiceControl~IOT0X2.dockerbuild
93.1 KB
sha256:ace07ae533edd77906e81b0523adc8e7aed319f71140fb02288130fe30600a76
Particular~ServiceControl~O67ML7.dockerbuild
94.1 KB
sha256:329ee01cf44f1891542fedf9868610a24832971f607089ac4802b495c987f646