Summary

Adds defensive error handling inDeviceProperties._get_attribute() to gracefully handle cases wherecuDeviceGetAttribute returnsCUDA_ERROR_INVALID_VALUE for unsupported attributes.

Changes

• Modified_get_attribute in_device.pyx to check forCUDA_ERROR_INVALID_VALUE before raising an exception
• When the driver returns this error, the method now returns0 as a conservative default
  • For boolean attributes (e.g.,vulkan_cig_supported),0 meansFalse
  • For integer attributes,0 indicates "not supported" or "disabled"

Rationale

This addresses two scenarios:

1. Version mismatch: When cuda-core is compiled against a newer CUDA toolkit (e.g., 12.9) but runs on an older driver (e.g., 12.8), newer attribute IDs may not be recognized by the driver
2. Driver bugs: Cases like nvbug5605010 where the driver advertises CUDA 12.9 capability but incorrectly rejects attribute 138 (CU_DEVICE_ATTRIBUTE_VULKAN_CIG_SUPPORTED) withCUDA_ERROR_INVALID_VALUE

Previously, these scenarios would causeDeviceProperties properties to raiseCUDAError exceptions, breaking tests and user code. With this change, unsupported attributes return sensible defaults (0/False) instead of raising exceptions.

Test Coverage

• Existing tests should continue to pass
• Tests that previously failed withCUDA_ERROR_INVALID_VALUE (e.g.,test_device.py) will now pass by returning0
• No new tests added (defensive handling preserves existing behavior for supported attributes)

Related Work

• Addresses nvbug5605010 (driver 575.66 incorrectly rejecting attribute 138)
• Handles version mismatches observed on luna-prod (CUDA 12.8 driver rejecting attributes 138, 141, 142)