-
-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with performCount
on Ember v3.15
#337
Comments
Seems to be triggered by this: ember-concurrency/addon/-scheduler.js Line 54 in a863f41
Mind giving this branch a try: #338 ? |
I been seeing this issue too. |
That branch fixes it, I have to use it now or can't release. |
I'm having issues with the test for the fix for it on earlier Ember versions in the CI matrix, but I'll try to fix that up tonight and tag a release. I do not recommend using a branch in production. |
@maxfierke it might be possible to remove the test file from the broccoli tree depending on the ember version, but I have to admit that I'm not sure how exactly to do that either 😅 |
I mean.. I can't not use the branch it literally breaks everything. |
that double negation is hard to parse 😅 |
It's on "numQueued". Versions:
code: export default class FindModalSplit extends Helper {
/**
* Task that wraps async call to get modal-split record from store
*/
@task *findModalSplitTask(geoid) {
return yield [
this.readonlyStore.find('ACS-modal-split', geoid),
this.readonlyStore.find('CTPP-modal-split', geoid),
];
}
/**
* Main helper 'compute' function
*/
compute(params) {
const [geoid] = params;
if (!geoid) return null;
return this.findModalSplitTask.perform(geoid);
}
} |
@allthesignals can you confirm there are no addons depending on earlier versions of ember-concurrency that might be getting used instead? |
@maxfierke that was totally it! time to add https://github.com/salsify/ember-cli-dependency-lint to this project... appreciate it :) |
We tried to update our app to Ember 3.15 this morning and the test suite of one of our apps uncovered the following issue:
I haven't been able to come up with a reproduction yet, but I'll update this issue if I can provide one.
The text was updated successfully, but these errors were encountered: