Back to Signal Feed
CodeTracked since May 18, 2026

Fix volume metadata parsing to prevent `AttributeError`

Updated `get_volume_file_metadata` to handle RFC 7231 HTTP-date strings from `files.get_metadata()` by parsing them to ISO 8601 before returning `last_modified`, with fallback to the raw value when parsing fails, instead of calling `.isoformat()` on a string.

databricks_sdkfiles.get_metadataget_volume_file_metadatavolume_files.py

What Happened

  • Updated `get_volume_file_metadata` to handle RFC 7231 HTTP-date strings from `files.get_metadata()` by parsing them to ISO 8601 before returning `last_modified`, with fallback to the raw value when parsing fails, instead of calling `.isoformat()` on a string.
  • Updated `get_volume_file_metadata` to handle RFC 7231 HTTP-date strings from `files.get_metadata()` by parsing them to ISO 8601 before returning `last_modified`, with fallback to the raw value when parsing fails, instead of calling `.isoformat()` on a string.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Implemented a concrete timestamp-shape fix in `get_volume_file_metadata`: string `last_modified` values are now normalized to ISO 8601 via `parsedate_to_datetime`, aligning output with existing list-file behavior and preventing crashes from API type inconsistency; added unit coverage for real SDK string input, `None`, and invalid strings.

Why Track This

Why It Matters

Operators and developers consuming Databricks volume metadata now avoid unexpected job interruptions when metadata fetches hit SDK string timestamps, so file-syncing, indexing, and automation pipelines are less likely to stop on `AttributeError` during normal runs; the PR also adds defensive handling of unparsable values, and should be watched for future SDK changes in `last_modified` typing or date format that could reintroduce parsing regressions.

Impact

Operators and developers consuming Databricks volume metadata now avoid unexpected job interruptions when metadata fetches hit SDK string timestamps, so file-syncing, indexing, and automation pipelines are less likely to stop on `AttributeError` during normal runs; the PR also adds defensive handling of unparsable values, and should be watched for future SDK changes in `last_modified` typing or date format that could reintroduce parsing regressions.

What To Watch Next

  • Watch whether databricks_sdk becomes a repeated pattern.
  • Track follow-up changes around AI Debugging and Error Localization.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: watch_sdk_last_modified_type_change, watch_http_date_format_variants.
Open Topic TimelineOpen Technical EventOpen Original Sourcewatch_sdk_last_modified_type_change / watch_http_date_format_variants / watch_fallback_path_output_shape_changes

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

databricks-solutions/ai-dev-kit PR #537: fix: handle HTTP-date string in get_volume_file_metadata

A real workspace replay showed `files.get_metadata()` returning `last_modified` as an HTTP-date string, which previously caused `AttributeError: 'str' object has no attribute 'isoformat'`; the PR adds parsing and tests that confirm the crash path is fixed.