If you're using this package along with Atlas Mongo 5.0, your project will not run on production environment

[fidelsam1992]

No description provided.

[fidelsam1992]

Since the forceful upgrade happened yesterday, if you are app is failing, try to remove this package

[jankapunkt]

@StorytellerCZ @fidelsam1992 what needs to be done to make it run with Mongo 5 ?

[nick-preda]

no solution found yet?

[jankapunkt]

@StorytellerCZ is there some action to be taken here? I am not using the package but I could take a look at it, depends on how severe the mongo 5 issue is.

[StorytellerCZ]

@jankapunkt if you could take a look that would be great. I'm unable to allocate any time for this till at least mid-May.

[wreiske]

I've actually attempted twice in the last week to get this on the latest version of meteor. For some reason every time I try to meteor update it says it fails and to check windows proxy settings... I might have to try on my mac to see if it's just a windows thing.

[jankapunkt]

@StorytellerCZ is there a reason for connection being explicitly set to null here: https://github.com/Meteor-Community-Packages/meteor-user-status/blob/master/server/status.js#L15

[wreiske]

@StorytellerCZ is there a reason for connection being explicitly set to null here: https://github.com/Meteor-Community-Packages/meteor-user-status/blob/master/server/status.js#L15

I double-checked and made sure it wasn't something I changed during the decaffeination. It looks like it was null while it was still caffinated:

meteor-user-status/status.coffee

Line 8 in b628f79

UserConnections = new Mongo.Collection("user_status_sessions", { connection: null })

From the docs:
https://docs.meteor.com/api/collections.html#Mongo-Collection

Pass null to specify no connection.

Prior to that, this line showed:
https://github.com/Meteor-Community-Packages/meteor-user-status/blame/a5312c58281d852f7932967872d0fbfff981fa76/status.coffee#L8

[jankapunkt]

Can someone please clone this package into your local packages folder and change that line to

 UserConnections = new Mongo.Collection("user_status_sessions") 

and then rebuild?

[wreiske]

If you go to the main branch of this repo, type "." and it will bring up an editor in the browser. You can edit it directly in github and then submit a PR. I believe the unit tests will run on the PR automatically. I have some time blocked tomorrow to look at this.

[jankapunkt]

thanks @wreiske I would avoid a PR until we find a solution that we can confirm to work

[wreiske]

TBH every time I go to update meteor this is always painful to dig through

C:\prj\meteor-user-status\demo>meteor update
This project is already at Meteor 2.7.1, the latest release.
=> Errors while upgrading packages:

While selecting package versions:
error: Conflict: Constraint [email protected] is not satisfied by accounts-base 2.2.2.
Constraints on package "accounts-base":
* accounts-base@~2.2.2 <- top level
* [email protected] <- mizzao:accounts-testing 0.1.0
* [email protected] <- service-configuration 1.3.0 <- accounts-base 2.2.2 <- accounts-ui 1.4.2 <- mizzao:accounts-testing 0.1.0
* [email protected] <- service-configuration 1.3.0 <- accounts-base 2.2.2 <- mizzao:accounts-testing 0.1.0
* [email protected] <- accounts-ui 1.4.2 <- mizzao:accounts-testing 0.1.0
* [email protected] <- accounts-ui-unstyled 1.7.0 <- accounts-ui 1.4.2 <- mizzao:accounts-testing 0.1.0
* [email protected] || 2.2.2 <- mizzao:user-status 1.0.2

I wish this could be easier!

Looks like we need to also update mizzao:accounts-testing

[wreiske]

Ok, made some progress today but I'm out of time #157