Manuel:viewmodel broken with latest updates?

help
9

Unfortunately it’s a Meteor issue which has to go through the normal (read: slow) fix and release process.

1 Like
10

Thanks for the response.

Any idea how I could temporarily get observe-sequence reverted? It seems attempting to with 1.0.14 is not working (as pasted above).

11

Dunno, my recommendation is to not update the Meteor version of the app until the fix gets out.

12

@hluz - If you could share how you reverted your package it would be greatly appreciated! Stuck with this issue right now and as pasted above, I am not able to get a revert to work.

13

In your project’s .meteor/versions file, set the line observe-sequence@1.0.15 to observe-sequence@1.0.14. Save.

14

Performed this and no luck… still getting

Error: {{#each}} currently only accepts arrays, cursors or falsey values.
    at badSequenceError (observe-sequence.js?hash=14ae414…:174)
    at observe-sequence.js?hash=14ae414…:139
    at Object.Tracker.nonreactive (tracker.js?hash=9f8a0ce…:631)
    at observe-sequence.js?hash=14ae414…:116
    at Tracker.Computation._compute (tracker.js?hash=9f8a0ce…:339)
    at new Tracker.Computation (tracker.js?hash=9f8a0ce…:229)
    at Object.Tracker.autorun (tracker.js?hash=9f8a0ce…:604)
    at Object.observe (observe-sequence.js?hash=14ae414…:113)
    at Blaze.View.<anonymous> (blaze.js?hash=813922c…:2819)
    at fireCallbacks (blaze.js?hash=813922c…:2013)

This page worked perfectly prior to 1.4 update… and we need 1.4 for newer node version to support a NPM package that we require in our project…

Any assistance on this issue would be appreciated!

(Edit: It seems it is automaticallly updating the version?

I noticed after editing it multiple times it is going back to version 15, and I see this in console:

Changes to your project's package version selections:

observe-sequence  upgraded from 1.0.14 to 1.0.15

Any ideas?

15

Specify the version like this: observe-sequence@=1.0.14

17

If you mean in the versions file, this throws an error if I use @=.

If you mean when attempting a Meteor add, or if I add the line you posted to packages file, the result is:

meteor add observe-sequence@=1.0.14
 => Errors while adding packages:

While selecting package versions:
error: No version of observe-sequence satisfies all constraints: @=1.0.14, @1.0.15
Constraints on package "observe-sequence":
* observe-sequence@=1.0.14 <- top level
* observe-sequence@1.0.15 <- top level
* observe-sequence@1.0.12 <- blaze 2.1.8 <- accounts-base 1.2.14 <- accounts-password 1.3.4
* observe-sequence@1.0.12 <- blaze 2.1.8 <- blaze-html-templates 1.0.1-anubhav.0
* observe-sequence@1.0.12 <- spacebars 1.0.12

Very frustrating…

18

@Spyridon, you appear to have some contradicting references to versions of the package… could you please check that you check for duplicate references… ensure that you:

  • Have no line for observe-sequence in .local/packages
  • Have only one line in .local/versions specifying 1.0.14
  • Don’t do a meteor update after changing the versions file

I have projects running 1.4.2.3 with observe-sequence@1.0.14 without any issues…

1 Like
19

Thanks again for the response.

  1. Just one line in packages.

Also, during removal I ensured there was none at all.

  1. Yes, same in versions file.

  2. Have not been doing meteor update after changing. It seems as soon as I start my application, the line about “Changes to your project’s package version selections” appears.

Not sure why the package version keeps automatically updating.

Here is the output from attempting to update versions file and starting server again:

=> Started proxy.
=> Started MongoDB.

Changes to your project's package version selections:

observe-sequence  upgraded from 1.0.14 to 1.0.15

=> Started your app.

=> App running at: http://localhost:3000/
20

You got me stumped…

There should be no need to mention the package at all in the packages file… (no need to do meteor add observe-sequence) and versions file should have observe-sequence@1.0.14

what Meteor release are you at? Are you using any local packages?

1 Like
21

Release: Meteor 1.4.3.1

No local packages, just some atmosphere/npm (pretty standard ones).

Based upon your input just now, I removed observe-sequence. At that point, it was no longer in packages file, and observe-sequence@1.0.15 was still in there.

So I updated to 1.0.14. When I start server, same exact thing happens:

observe-sequence upgraded from 1.0.14 to 1.0.15

Any ideas what is automatically upgrading the package??

22

Sorry… beats me. But there must be something…

1 Like
23

Yeah, it’s strange… but thanks a lot for trying to help out!

24

Latest beta has a fix for it:
meteor update --release 1.4.3.2-beta.0

1 Like
25

Waiting for 1.4.3.2, i solved it like this :

Template.registerHelper(‘asArray’,function(obj){
return obj && obj.array();
});

{{#each asArray yourreactiveArray}}
{{/each}}

26

Wasn’t 1.4.3.2 released 2 days ago?

1 Like
27

Hi!
Meteor updated to 1.4.3.2 (with observe-sequence@1.0.16) gives me following:

Uncaught TypeError: bindArg.element.addEventListener is not a function
at Object.bind (modules.js?hash=fa16d8f…:44518)
at Function.bindSingle (modules.js?hash=fa16d8f…:42337)
at modules.js?hash=fa16d8f…:42324
at attachRef (modules.js?hash=fa16d8f…:27735)
at Object.ReactRef.attachRefs (modules.js?hash=fa16d8f…:27757)
at ReactCompositeComponentWrapper.attachRefs (modules.js?hash=fa16d8f…:27561)
at CallbackQueue.notifyAll (modules.js?hash=fa16d8f…:27455)
at ReactReconcileTransaction.close (modules.js?hash=fa16d8f…:37729)
at ReactReconcileTransaction.closeAll (modules.js?hash=fa16d8f…:28614)
at ReactReconcileTransaction.perform (modules.js?hash=fa16d8f…:28561)

28

Please make a repro.

29

here is the repo
https://bitbucket.org/nchudnovets/kriya_temp