Skip to content
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

Future resolved more than once on a brand new project #4711

Closed
johanalkstal opened this issue Jul 9, 2015 · 2 comments
Closed

Future resolved more than once on a brand new project #4711

johanalkstal opened this issue Jul 9, 2015 · 2 comments

Comments

@johanalkstal
Copy link

@johanalkstal johanalkstal commented Jul 9, 2015

Meteor 1.1.0.2

Doing the following on my Windows 8.1 machine causes an error.

meteor create my-project

cd my-project

meteor

then opening another console in /my-project and running meteor mongo

returns

C:\Users\alkstal\AppData\Local\.meteor\packages\meteor-tool\1.1.3\mt-os.windows.x86_32\dev_bundle\lib\node_modu
les\fibers\future.js:226                                                                                       
                        throw new Error('Future resolved more than once');                                     
                              ^                                                                                
Error: Future resolved more than once                                                                          
    at Object.Future.return (C:\Users\alkstal\AppData\Local\.meteor\packages\meteor-tool\1.1.3\mt-os.windows.x8
6_32\dev_bundle\lib\node_modules\fibers\future.js:226:10)                                                      
    at Socket.<anonymous> (C:\Users\alkstal\AppData\Local\.meteor\packages\meteor-tool\1.1.3\mt-os.windows.x86_
32\tools\run-mongo.js:221:36)                                                                                  
    at Socket.emit (events.js:95:17)                                                                           
    at net.js:441:14                                                                                           
    at process._tickCallback (node.js:442:13)                                                                  

Why and what can I do to solve this?

@johanalkstal johanalkstal changed the title Future resolved more than once on a brand new project on Win 8.1 Future resolved more than once on a brand new project Jul 9, 2015
@glasser
Copy link
Member

@glasser glasser commented Jul 14, 2015

Hmm. This looks like an issue in the Windows-specific findMongoPort code. I guess this happens if the client gets an error after successfully connecting. Let's see if this fixes it.

@glasser glasser closed this Jul 14, 2015
glasser added a commit that referenced this issue Jul 14, 2015
@ninjasun
Copy link

@ninjasun ninjasun commented Jul 30, 2015

how can i use the plugin?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants