publication exception after upgrade to 0.8.1

[elie222]

(STDERR) error caught on publication: players : Match error: Failed Match.OneOf or Match.Optional validation

Didn't have this problem on Meteor 0.8. Not sure what's causing it. Difficult to debug

[avital]

Can you please share a small repro?

[avital]

That code snippet isn't enough to diagnose the issue (amongst other things, there's no call to Meteor.subscribe so the publish function will never run).

Please file a repro in the form of an app in a GitHub repository we can clone and run. https://github.com/meteor/meteor/wiki/Contributing-to-Meteor#reporting-a-bug-in-meteor

[vsivsi]

I'm seeing this exact error in code that programmatically passed undefined options to collection.findOne()

This works in 0.8.0.1, but fails in 0.8.1.0:

result = collection.findOne({},{ sort: undefined, skip: undefined });

The error is:

W20140430-12:14:43.930(-7)? (STDERR) Error: Match error: Failed Match.OneOf or Match.Optional validation
W20140430-12:14:43.930(-7)? (STDERR)     at checkSubtree (packages/check/match.js:200)
W20140430-12:14:43.931(-7)? (STDERR)     at check (packages/check/match.js:14)

[mizzao]

I'm also seeing errors with find selectors using sort and limit in Meteor 0.8.1 that worked in 0.8.0. Will try to make a repro.

[vsivsi]

@mizzao It looks like they already found/fixed this bug in this commit on the release-0.8.1.1 branch:
673a285

[mizzao]

I think I'm having a different issue, actually. I have some publications that worked in 0.8 but the data completely disappears in 0.8.1. with some silent failure in the publish function; no error thrown. I'm trying to diagnose it right now...

Is there some "preserve subscriptions over hot code reload" logic that got added recently? I'm seeing some very strange behavior, including publications not getting re-run after HCR.

[vsivsi]

@mizzao Hmm I haven't seen anything like that, but it wouldn't surprise me, a bunch of stuff seems to have changed/broke in 0.8.1, unrelated to the OAuth fixes.

[elie222]

My problem was fixed in the 0.8.1.1 update. Thanks

[datacarl]

I also ran into this error message when upgrading. On 0.8.0 you could pass a string to sort without getting an error, but now it throws an error. Seems to be working as expected now.

[glasser]

@datacarl I mean, yes, we added this to make it more clear that passing a string to sort was incorrect.

[datacarl]

👍