enableScheduling causes simple solid router examples to crash
Hi, I was going to file this as a bug, but wasn't sure if I should direct it at the router repo or the main solidjs repo.
In short, I enabled scheduling with
enableScheduling in an App I've been playing around with, in the hopes that it could help a bit with some perf issues. It didn't make too much of a difference, but I forgot to turn enableScheduling back off. When I added Router, I got weird errors that I eventually traced back to enableScheduling. Repro here: https://stackblitz.com/edit/solidjs-templates-gttqb3?file=src%2FApp.tsx,src%2Findex.tsx
If this is expected behavior, I'd be curious to understand more 🙂6 Replies
I've yet to see a realworld scenario where this makes a big difference but now we can do cool demos too and start testing it.https://github.com/solidjs/solid/releases/tag/v1.1.0 How can you see this and not immediately lose interest? If this is related to competing with React's time-slicing, there was an ongoing debate whether that made any sense for Solid and the answer never really moved off of: "no"; and if so I wouldn't be surprised if this will fall victim to Solid's impending 2.0 reactivity revamp. But perhaps I'm confusing things.
GitHub
Release V1.1.0 - Interrupting Cow · solidjs/solid
Expanding Solid's concurrency to include interruptible scheduling. Bug fixes around Types and around reactive execution order guarantees.
New Features
createUniqueId
A universal id generator th...
Oh, I did lose interest, which is part of why I forgot I had enabled it in the first place 😅
I'm not interested in fixing this bug so I can keep it enabled, I'm just reporting it in case anyone cares to fix it.
I was just trying to manage expectations.
Reporting it in the solid-js repo (making clear you are just reporting it and not viewing it as a deal breaker/show stopper) would give it good visibility for others looking for problems involving
enableScheduling().
And given enough time you may hear what the future holds for enableScheduling()
with some perf issues.Managed to address those yet?
Reporting it in the solid-js repoFiled here: https://github.com/solidjs/solid/issues/2176
Managed to address those yet?Mostly. Working on a simulation with low millions of entities as a toy/demo project, so any inefficiencies become glaring very quickly. It's my first project in Solid (coming from React), so a lot of the code I wrote at first was a bit at odds with Solid patterns. I feel like I'm getting a feel for things now though, thanks in part to community help 🙂
GitHub
Using enableScheduling in a simple solidjs-router project throws er...
Describe the bug Using enableScheduling in a simple solidjs-router project throws errors when changing pages, saying that the results of createMemo are undefined. (To be clear, this isn't a blo...
Wow, you already have a response.
with low millions of entities as a toy/demo projectSounds like the kind of thing that Erlang (well, right now Gleam is the new hotness in BEAM-land) would be great at for back end processing given how dirt-cheap it is to have tons of processes that aren't doing anything in particular right at this moment. https://youtu.be/_fgaPGLGZI0
Gleam
The Gleam programming language
Erlang Solutions
YouTube
Lambda Days 2015 - Torben Hoffmann - Thinking like an Erlanger
Torben Hoffmann
CTO @ Erlang Solutions
Torben Hoffmann is CTO for Erlang Solutions. He has been active in the Erlang community for several years and has spoken at conferences world-wide. His first big Erlang related project was the introduction of Erlang as a technology to write a gateway in for Motorola Solutions in Denmark. Torben studied Eng...
GitHub
Using enableScheduling in a simple solidjs-router project throws er...
Describe the bug Using enableScheduling in a simple solidjs-router project throws errors when changing pages, saying that the results of createMemo are undefined. (To be clear, this isn't a blo...
Wow, you already have a response.Yea! I was surprised too; very responsive!
Sounds like the kind of thing that Erlang (well, right now Gleam is the new hotness in BEAM-land)Right now it's just very prototype-y and scaling so far, but if it goes beyond that, Erlang/BEAM-land would be interesting to look into... Thanks for the pointers 🙂