NullVoxPopuli

from discord: https://discord.com/channels/480462759797063690/1358891936450215966/1358896696675012820

> or work with the @ember/test-waiters maintainers to try to devise some other easy way to wrap ember-concurrency tasks. It's not `@ember/test-waiters`'s responsibility to integrate with ecosystem libraries -- that's...

note that the repro is called `ember-resources-bug` but [ember-resources](https://github.com/NullVoxPopuli/ember-resources/blob/main/docs/docs/README.md) isn't used here :sweat_smile: it's using [ember-could-get-used-to-this](https://github.com/tracked-tools/ember-could-get-used-to-this/tree/v1.0.1), which uses a side-effecting callbacks on a class as part of the Helper lifecycle....

do you have a more minimal reproduction that doesn't use ember-could-get-used-to-this?

as for async stuff, we also kind of have some simpler abstractions now (resources are fairly low-level (something I'm hoping to touch on at emberfest!)), such as - https://reactive.nullvoxpopuli.com/functions/get-promise-state.getPromiseState.html -...

implementation-wise, it may be tricky to do, because lazy-initialization during render is something we (neededly) allow. 🤞 something better is achievable tho -- we def need better error-driven guidance

How do you configure it tho? do all devs still share the same secret-key for access? (this is dangerous)

so, in order to contact a cache server, turbo needs a `TURBO_TOKEN` to authenticate with the server. Exposing that _to all employees_ gives folks the chance to try to poison...

last compatible turbo version is 1.12.0, for me/us

Is there a discord or something, I don't want to spam everyone while I debug. I saw a request body too large error at one point -- while I was...