Everything was working…then I shutdown my Windows 10 PC and head out. When I came back, I started the PC and started meteor as usual, but on page reload, all my publications where not showing anymore. I don’t use the imports folder. I prefer eager loading them for now. I am using Meteor 1.4.3.1. Publications no longer show. All my template data don’t receive data from collection. User login possible when checked the Mongol tool. I am having serious issues with Meteor 1.4.3.1 and my launch date is tomorrow. Please Help. Thanks
PS: First I thought it was blaze, mongo…I completely uninstall meteor and reinstalling now…but this time version 1.4.3.2
Can you look at your db and confirm that the data is there? Do you have a repo to share or sample app?
Here is what I got when I tried updating meteor.
C:\Users\MartinDev\AppData\Local.meteor\packages\meteor-tool\1.4.2_7\mt-os.windows.x86_32\dev_bundle\lib\node_modules\meteor-promise\promise_server.js:190
throw error;
^
Error: No metadata files found for isopack at: /C/Users/MartinDev/AppData/Local/.meteor/packages/coffeescript/1.0.17
at Isopack.loadUnibuildsFromPath (C:\tools\isobuild\isopack.js:900:13)
at C:\tools\packaging\tropohouse.js:521:21
at Array.forEach (native)
at Function..each._.forEach (C:\Users\MartinDev\AppData\Local.meteor\packages\meteor-tool\1.4.2_7\mt-os.windows.x86_32\dev_bundle\lib\node_modules\underscore\underscore.js:79:11)
at C:\tools\packaging\tropohouse.js:520:13
at C:\tools\utils\buildmessage.js:359:18
at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:352:34
at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:350:23
at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
at Object.enterJob (C:\tools\utils\buildmessage.js:324:26)
at C:\tools\packaging\tropohouse.js:515:22
at C:\tools\utils\buildmessage.js:359:18
at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:352:34
at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:350:23
at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
at Object.enterJob (C:\tools\utils\buildmessage.js:324:26)
at Object.download (C:\tools\packaging\tropohouse.js:427:20)
at C:\tools\packaging\tropohouse.js:613:18
at C:\tools\utils\buildmessage.js:572:21
at C:\Users\MartinDev\AppData\Local.meteor\packages\meteor-tool\1.4.2_7\mt-os.windows.x86_32\dev_bundle\lib\node_modules\meteor-promise\fiber_pool.js:32:39
=> awaited here:
at Promise.await (C:\Users\MartinDev\AppData\Local.meteor\packages\meteor-tool\1.4.2_7\mt-os.windows.x86_32\dev_bundle\lib\node_modules\meteor-promise\promise_server.js:39:12)
at Object.forkJoin (C:\tools\utils\buildmessage.js:604:6)
at [object Object].downloadPackagesMissingFromMap (C:\tools\packaging\tropohouse.js:609:18)
at C:\tools\project-context.js:776:25
at C:\tools\utils\buildmessage.js:359:18
at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:352:34
at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:350:23
at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
at Object.enterJob (C:\tools\utils\buildmessage.js:324:26)
at C:\tools\project-context.js:775:20
at C:\tools\packaging\catalog\catalog.js:100:5
at C:\tools\utils\buildmessage.js:271:13
at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:264:29
at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:262:18
at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:253:23
at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
at Object.capture (C:\tools\utils\buildmessage.js:252:19)
at Object.catalog.runAndRetryWithRefreshIfHelpful (C:\tools\packaging\catalog\catalog.js:99:31)
at ProjectContext._downloadMissingPackages (C:\tools\project-context.js:774:13)
at C:\tools\project-context.js:268:9
at C:\tools\utils\buildmessage.js:359:18
at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:352:34
at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:350:23
at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
at Object.enterJob (C:\tools\utils\buildmessage.js:324:26)
at ProjectContext._completeStagesThrough (C:\tools\project-context.js:258:18)
at C:\tools\project-context.js:250:12
at Function.run (C:\tools\tool-env\profile.js:490:12)
at ProjectContext.prepareProjectForBuild (C:\tools\project-context.js:249:13)
at C:\tools\runners\run-app.js:549:29
at C:\tools\utils\buildmessage.js:271:13
at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:264:29
at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:262:18
at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:253:23
at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
at Object.capture (C:\tools\utils\buildmessage.js:252:19)
at bundleApp (C:\tools\runners\run-app.js:548:31)
at AppRunner._runOnce (C:\tools\runners\run-app.js:617:35)
at AppRunner._fiber (C:\tools\runners\run-app.js:876:28)
at C:\tools\runners\run-app.js:403:12
I guess this has to do with the package cache. How do I clear this error?? I am on Windows 10 x64. Thanks
Seems like a few separate issues here. I’m not on Windows, so can’t really help there. I’d probably create a separate post for not being able to update.
1 Like
Just checked. My data are in the DB, using the mongo shell.
Suddenly all my publication stopped working. Though I can see the user signed-in using Mongol. Checked all my publication codes, nothing seems wrong. It all started after I hibernated Windows and when I loggedin again and refreshed the app, my blaze conditionals stopped working…that’s when I noticed data were not being published to the client anymore. It’s very frustrating, with my deadline and launch data so close.
I updated successfully and this particular issue went away. Thanks
I used msavin:mongol to check if the collection is subscribed to on client, no data, but the collections are there.
Without the code or a sample of the live app, it’s going to be tough for anyone to help, I think.
Fixed! I was finally able to resolve the issue after several hours of trying, including uninstalling and reinstalling Meteor. It turns out a template was causing the whole issues. I am now on Meteor 1.4.3.2. I don’t think this update fixed it. I missed an ‘s’ while defining one of my Helpers.
Thanks for following all along. Appreciated.
1 Like
Sorry to hear that… live and learn I guess.
1 Like