Skip to content
Node.js CI

[FIX] reactivity: don't react when we set the same object #1906

Sign in to view logs

[FIX] reactivity: don't react when we set the same object

[FIX] reactivity: don't react when we set the same object #1906

Triggered via pull request October 13, 2023 12:15
@FrancoisGeFrancoisGe
synchronize #1541
master-fix-object-fge
Status Failure
Total duration 1m 33s
Artifacts –

deploy.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
build (14.x)
Process completed with exit code 1.
build (12.x)
Process completed with exit code 1.
build (16.x)
The operation was canceled.
build (14.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (12.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (16.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/