alamb commented on issue #8813:
URL: https://github.com/apache/arrow-rs/issues/8813#issuecomment-3508832184

   I see recent failures on the C++ repo also show failues, for example:
   
   https://github.com/apache/arrow/actions/runs/19208648378/job/54907555826
   
   ```
    ################# FAILURES #################
     FAILED TEST: flight_sql:extension C++ producing,  Go consuming
     <class 'RuntimeError'>: Command failed: 
/root/go/bin/arrow-flight-integration-client -host localhost -port=40325 
-scenario flight_sql:extension
     With output:
     --------------
     panic: expected: schema:
          fields: 1
            - pkey: type=int32, nullable
              metadata: ["ARROW:FLIGHT:SQL:TABLE_NAME": "test", 
"ARROW:FLIGHT:SQL:IS_AUTO_INCREMENT": "1", 
"ARROW:FLIGHT:SQL:IS_CASE_SENSITIVE": "0", "ARROW:FLIGHT:SQL:TYPE_NAME": 
"type_test", "ARROW:FLIGHT:SQL:SCHEMA_NAME": "schema_test", 
"ARROW:FLIGHT:SQL:IS_SEARCHABLE": "1", "ARROW:FLIGHT:SQL:CATALOG_NAME": 
"catalog_test", "ARROW:FLIGHT:SQL:REMARKS": "test column", 
"ARROW:FLIGHT:SQL:PRECISION": "100"], got: schema:
          fields: 1
            - pkey: type=int32, nullable
              metadata: ["ARROW:FLIGHT:SQL:TABLE_NAME": "test", 
"ARROW:FLIGHT:SQL:IS_AUTO_INCREMENT": "1", 
"ARROW:FLIGHT:SQL:IS_CASE_SENSITIVE": "0", "ARROW:FLIGHT:SQL:TYPE_NAME": 
"type_test", "ARROW:FLIGHT:SQL:SCHEMA_NAME": "schema_test", 
"ARROW:FLIGHT:SQL:IS_SEARCHABLE": "1", "ARROW:FLIGHT:SQL:CATALOG_NAME": 
"catalog_test", "ARROW:FLIGHT:SQL:PRECISION": "100", 
"ARROW:FLIGHT:SQL:REMARKS": "test column"]
     
     goroutine 1 [running]:
     main.main()
        
/arrow/go/arrow/internal/flight_integration/cmd/arrow-flight-integration-client/main.go:52
 +0x277
   ```
   
   Given Go is implicated in both, maybe there is something related to Go...


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to