[CXX-2147] mongocxx::v_noabi::bulk_write_exception Created: 05/Jan/21 Updated: 27/Oct/23 Resolved: 16/Feb/21 |
|
| Status: | Closed |
| Project: | C++ Driver |
| Component/s: | Build |
| Affects Version/s: | 3.6.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Code Bau | Assignee: | Kevin Albertson |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 10 x64, Visual Studio 2019 |
||
| Backwards Compatibility: | Fully Compatible |
| Description |
|
Hi, I set up the latest drivers for C ++ (mongo-c-driver-1.17.3, mongo-cxx-driver-r3.6.2) After following these steps: http://mongoc.org/libmongoc/current/installing.html
Finally i get:
Before that, I used vcpkg with: C - 1.16.1 # 3, C ++ - 3.4.0-5 # 1
And i get:
and,
This code works fine on old Lenovo G570 15.6 inch Laptop (Core i3-2310M, RAM 4GB, HDD 500GB, DVDRW, Windows 7 with VIsual Studio 2019. |
| Comments |
| Comment by Backlog - Core Eng Program Management Team [ 16/Feb/21 ] | ||||||||||||
|
There hasn't been any recent activity on this ticket, so we're resolving it. Thanks for reaching out! Please feel free to comment on this if you're able to provide more information. | ||||||||||||
| Comment by Kevin Albertson [ 02/Feb/21 ] | ||||||||||||
|
Hi codebaudata@gmail.com. Apologies for the delayed response. I attempted to reproduce using the snippet you included and the mongo-cxx-driver vcpkg. It was able to build, run, and insert without issue. The contents of the exception may give more information to the source of the error. Can you wrap the insert_one operation with a try/catch to print out the contents of the bulk_write_exception and query_exception? To do so, add the following includes:
And wrap the insert_one as follows:
That may help us debug the issue. Sincerely, | ||||||||||||
| Comment by Kevin Albertson [ 05/Jan/21 ] | ||||||||||||
|
Hi codebaudata@gmail.com, thank you for the detailed bug report! We will look into this soon. |