fix: Send chained exceptions in the correct order

Author: untitaker

sentry_sdk/utils.py

@@ -569,6 +569,9 @@ def exceptions_from_error_tuple(
                 exc_type, exc_value, tb, client_options, mechanism
             )
         )
+
+    rv.reverse()
+
     return rv
 
 

tests/test_client.py

@@ -419,15 +419,21 @@ def test_chained_exceptions(sentry_init, capture_events):
 
     try:
         try:
-            1 / 0
+            raise ValueError()
         except Exception:
             1 / 0
     except Exception:
         capture_exception()
 
     event, = events
 
-    assert len(event["exception"]["values"]) == 2
+    e1, e2 = event["exception"]["values"]
+
+    # This is the order all other SDKs send chained exceptions in. Including
+    # Raven-Python.
+
+    assert e1["type"] == "ValueError"
+    assert e2["type"] == "ZeroDivisionError"
 
 
 @pytest.mark.tests_internal_exceptions