[SERVER-64639] Stitch SDK hits invariant initializing ThreadContext Created: 18/Mar/22  Updated: 29/Oct/23  Resolved: 04/May/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Nathan Blinn Assignee: Billy Donahue
Resolution: Fixed Votes: 0
Labels: 6.1-targeted
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-63852 getThreadName() should not crash Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Service Arch 2022-05-02, Service Arch 2022-05-16
Participants:

 Description   

Newer versions of the Stitch SDK lead to a critical assertion error, which will block development on certain machines.

Invariants that stdx::this_thread::get_id() == kMainThreadId

Context: if you run initializers in any other thread than the "main thread" (a concept that Stitch doesn't necessarily have), then it would break. This is currently incorrect for dynamically-loaded library implementations.

AC: Fix the invariant: investigate what goes wrong is this invariant isn't met, and then fix the invariant to reflect the totally-correct world.



 Comments   
Comment by Githook User [ 03/May/22 ]

Author:

{'name': 'Billy Donahue', 'email': 'billy.donahue@mongodb.com', 'username': 'BillyDonahue'}

Message: SERVER-64639 ThreadContext remove invariant on main thread check
Branch: master
https://github.com/mongodb/mongo/commit/245760b3ade83cea0d70432f0716ce9afd3687d6

Comment by Devika Pisharoty [ 22/Apr/22 ]

Any updates on this? Who should the Realm team reach out to?

Comment by Kyle Suarez [ 22/Mar/22 ]

Given that the related ticket is in Service Architecture, Query Execution thinks that team will be better equipped to look at this problem.

Generated at Thu Feb 08 06:00:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.