sailsbot
commented
3 years ago @mactyr Thanks for posting! We'll take a look as soon as possible.
In the mean time, there are a few ways you can help speed things along:
- look for a workaround. (Even if it's just temporary, sharing your solution can save someone else a lot of time and effort.)
- tell us why this issue is important to you and your team. What are you trying to accomplish? (Submissions with a little bit of human context tend to be easier to understand and faster to resolve.)
- make sure you've provided clear instructions on how to reproduce the bug from a clean install.
- double-check that you've provided all of the requested version and dependency information. (Some of this info might seem irrelevant at first, like which database adapter you're using, but we ask that you include it anyway. Oftentimes an issue is caused by a confluence of unexpected factors, and it can save everybody a ton of time to know all the details up front.)
- read the code of conduct.
- if appropriate, ask your business to sponsor your issue. (Open source is our passion, and our core maintainers volunteer many of their nights and weekends working on Sails. But you only get so many nights and weekends in life, and stuff gets done a lot faster when you can work on it during normal daylight hours.)
- let us know if you are using a 3rd party plugin; whether that's a database adapter, a non-standard view engine, or any other dependency maintained by someone other than our core team. (Besides the name of the 3rd party package, it helps to include the exact version you're using. If you're unsure, check out this list of all the core packages we maintain.)
Please remember: never post in a public forum if you believe you've found a genuine security vulnerability. Instead, disclose it responsibly.
For help with questions about Sails, click here.
lfelipeqn
mactyr
eashaw
designbymind
DmitrKulagin
Node version: 14.16.0 Sails version (sails): 1.4.2 ORM hook version (sails-hook-orm): 3.0.2 Sockets hook version (sails-hook-sockets): N/A Organics hook version (sails-hook-organics): N/A Grunt hook version (sails-hook-grunt): N/A Uploads hook version (sails-hook-uploads): N/A DB adapter & version (e.g. sails-mysql@5.55.5): sails-mongo@1.2.0 Skipper adapter & version (e.g. skipper-s3@5.55.5): N/A
I have a sails application I am trying to update from mongodb 3.4 (which is past end-of-life) to the current stable, 4.4, or as near as possible.
The latest released version of sails-mongo in npm appears to be 1.2.0, and the readme says it's been tested with MongoDB 3.4 and 3.6. sails-mongo 1.2.0 requires node mongodb driver version 2.2.25, which based on this compatibility chart appears to be officially only compatible with MongoDB up to 3.4.
The sails-mongo repo readme says "This version of the adapter has been tested with MongoDB versions 3.6, 4.0, and 4.2. It uses MongoDB 3.5.x connection options." and its package.json lists mongodb driver 3.5.9 as a dependency, which according to the compatibility chart should support up to MongoDB 4.2 (though not 4.4).
I see that a sails-mongo 2.0.0-0 pre-release (which would presumably be compatible up to MongoDB 4.2) was tagged in Nov 2020, but it doesn't look like there's been any further activity since that month.
My questions are: