solid / start : createAsync/createResource mixes results when run server side, when component has "unstable" execution. due to secondary rerun of the suspended component. #2517
Description
Describe the bug
createAsync/createResource mixes results when run server side, when component has "unstable" execution. due to secondary rerun of the suspended component. and incorrect mapping.
Your Example Website or App
Steps to Reproduce the Bug or Issue
- go directly to the
/aboutin the browser not via the link - observe the logs
Expected behavior
if (shouldRedirect()) {
console.log('LATER');
console.log('A:', aAsy()); // expected "A: a" actual "A: b"
console.log('B:', bAsy()); // expected "B: b" actual "B: a"
} else {
console.log('INITIAL');
console.log('A:', aAsy()); // should be undefined
console.log('B:', bAsy()); // should be undefined
}Screenshots or Videos
msedge_QeCu93gKAj.mp4
Platform
online playground
Additional context
if (shouldRedirect()) {
// later
// if we flip back the order it will become stable again
aAsy = createAsync(() => a());
bAsy = createAsync(() => b());
// bAsy = createAsync(() => b());
// aAsy = createAsync(() => a());
} else {
// initial
bAsy = createAsync(() => b());
aAsy = createAsync(() => a());
}solid re runs the suspended component
on the 2nd run it tries to match the results based on the original (initial)
order of requests.
because we flip the createAsync order on the "later" phase
the results are matched incorrectly.