-
-
Notifications
You must be signed in to change notification settings - Fork 596
Find/first issue with 3.5 #1614
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for opening this issue!
|
3.5.0 is broken, please see #1600. Can you try 3.5.1-alpha.2 or revert to 3.4.4 |
I'm closing, if the issue still exists on the latest alpha version please let us know and we'll re-open this issue. |
@mtrezza i think we should keep this open until the next stable release. More will come in. The checklist show a check mark for “existing” issues not closed ones |
Yes, let me pin a new issue to the top of the issue list. Our process is that an issue is closed when the PR is merged. This also happens automatically because of the "Closes" tag on GitHub. |
🎉 This change has been released in version 3.5.1-beta.2 |
🎉 This change has been released in version 3.5.1 |
New Issue Checklist
Issue Description
Unable to user Query.first on 3.5
Steps to reproduce
Do a first() query with 3.5 client (the query work well with older versions, at least 3.4.2)
Actual Outcome
giving a collection 'Mission' the query above return an error
outputed error

Expected Outcome
On lower version

the same query work.
Environment
Issue found on 3.5, work on 3.4.2.
Server
5.3.3
Alpine16
AWS
Database
mongo
4.4
ATLAS
Client
3.5
Logs
The text was updated successfully, but these errors were encountered: