Issue Description

What was unclear/insufficient/not covered in the documentation

How to update and increment in one single query

If possible: Provide some suggestion on how we can enhance the docs

Add this to the docs.

Additional context

#7268

Issue Template Checklist

There are two static analyzers in an LLVM project:

• https://clang.llvm.org/extra/clang-tidy/
• https://clang-analyzer.llvm.org/

Would be nice to check tarantool source code with these analyzers, fix warnings and errors and add it in Tarantool CI.

FLUP from internal reference PDS-106493:

It appears that the logline:

Possible bug: Someone rolled back our transaction but our locks were still valid; Atlas code is not allowed to do this, though others can.

Is not very precise, because there are places in the protocol that could legitimately cause this. Specifically, the relevant thing is callers to this method that don't spec

For educative mode it would be nice to understand better what the Bits mean.

Bits = 0x190102B1
Target = 2 ^ ( 8 * ( 0x19 - 3 ) ) * 0x 0102B1 = 0x000000000000000102B100000000000000000000000000000000000000000000

so also split "bits" into its two parts (if I understood that right). Bits = 0x190102B1 = 0x19 0x0102B1.

The current behavior to return true on a dbCollection.updateis making some important tests of ours fail. To give an example:

const numUpdates = MpIndex.update({ _id: mpIndexDoc }, { $addToSet: { cardsIdArray: cardId } }, { tx: true, instant: true }); if (numUpdates === 0) { throw new Error(Something is wrong - No doc was being updated - mpIndex _id: ${mp

Is your feature request related to a problem? Please describe.
The API error messages are rather generic and I think we can improve them - in particular the error 401 API access token missing, invalid, revoked, or expired (link to code line) because users are very likely to encounter this error on their first try of th

Benchmarks and features make it sound promising for our workloads. AWS runs exclusively on Intel hardware, so we'll be able to make use of the CPU-specific optimizations in Clear Linux. We'll need to verify that Pan

See the following SO post for context.

https://stackoverflow.com/questions/22786374/queries-hang-when-using-mongoose-createconnection-vs-mongoose-connect

Essentially for downstream projects, like mine, that use mongoose.createConnection instead of mongoose.connect.. we use all db.model instead of mongoose.model. Currently this package assumes mongoose.model will work in all instances, howe

We using Sentry to collect errors and user feedbacks from the App. (see)

We need to configure Sentry also in the Nuxt app:

• Collect exceptions.
• Create a form to let the user contact us without mail.