-
Notifications
You must be signed in to change notification settings - Fork 23
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
ERROR: Future resolved more than once #23
Comments
Yes, also getting this with recent upgrade to 1.0.1 for my company's Meteor project template. Eek! Any known fix? |
Hey @derek-fong, @etyp and Future Readers, I noticed that the github repo package code appears ahead of what Anyway, unless things change, future readers may want to just git clone and add the package manually to avoid this "future resolved more than once" bug that still seems to exist in the version available on Meteor's packaging (which sounds like is going away anyway). |
I've got the same problem with Future. Anyone fix this ? Thx |
@edsoubsoub Can't remember exactly how I solved this problem but I think what I did was forked this repo into my project and modified
and installed |
If I do that, for some reason it looks as though the api.addFiles calls are not run... |
Any update on this issue ? I have the same problem |
Have you tried the fork at https://github.com/ayselafsar/meteor-accounts-ldap ? If that one works for you, I will merge it into this repo. |
@conrad-dk Was trying to test this package but when I tried to install the package
Suspect package
Tried on to install this package on Windows, MacOS and Linux VM and they all return with the same error - Any ideas? :) |
AD Authentication works fine without
LDAP_DEFAULTS.searchResultsProfileMap
specified but when I try to addprofileProperty
toLDAP_DEFAULTS.searchResultsProfileMap
it throwsHere is my
client
andserver
codeThe text was updated successfully, but these errors were encountered: