Skip to content

fix: address scenario where we would crash when replacing a matched vnode with null #1317

fix: address scenario where we would crash when replacing a matched vnode with null

fix: address scenario where we would crash when replacing a matched vnode with null #1317

Triggered via pull request February 16, 2024 08:32
Status Failure
Total duration 55s
Artifacts

benchmarks.yml

on: pull_request
Build & Test  /  Build & Test
40s
Build & Test / Build & Test
Prepare environment
0s
Prepare environment
Bench 02_replace1k  /  run_bench
Bench 02_replace1k / run_bench
Bench 03_update10th1k_x16  /  run_bench
Bench 03_update10th1k_x16 / run_bench
Bench 07_create10k  /  run_bench
Bench 07_create10k / run_bench
Bench filter_list  /  run_bench
Bench filter_list / run_bench
Bench hydrate1k  /  run_bench
Bench hydrate1k / run_bench
Bench many_updates  /  run_bench
Bench many_updates / run_bench
Bench text_update  /  run_bench
Bench text_update / run_bench
Bench todo  /  run_bench
Bench todo / run_bench
Fit to window
Zoom out
Zoom in

Annotations

2 errors
Build & Test / Build & Test: src/diff/children.js#L237
The left-hand side of an arithmetic operation must be of type 'any', 'number', 'bigint' or an enum type.
Build & Test / Build & Test
Process completed with exit code 1.