Back to Signal Feed
CodeTracked since May 18, 2026

Fix volume metadata date parsing to prevent SDK type errors

PR #537 fixes `get_volume_file_metadata` in `databricks-solutions/ai-dev-kit` by handling `last_modified` values returned as RFC 7231 HTTP-date strings from `files.get_metadata()`, instead of calling `.isoformat()` directly on a string and crashing.

get_volume_file_metadatafiles.get_metadatalast_modifiedemail.utils.parsedate_to_datetime

What Happened

  • PR #537 fixes `get_volume_file_metadata` in `databricks-solutions/ai-dev-kit` by handling `last_modified` values returned as RFC 7231 HTTP-date strings from `files.get_metadata()`, instead of calling `.isoformat()` directly on a string and crashing.
  • PR #537 fixes `get_volume_file_metadata` in `databricks-solutions/ai-dev-kit` by handling `last_modified` values returned as RFC 7231 HTTP-date strings from `files.get_metadata()`, instead of calling `.isoformat()` directly on a string and crashing.
  • 1 evidence item attached for review.

What is Different

Before

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

Now

Introduced a concrete parsing fix for a real SDK type mismatch: `get_volume_file_metadata` now parses RFC 7231 HTTP-date strings with `parsedate_to_datetime` and returns normalized ISO 8601 timestamps, with fallback-to-raw-value handling if parsing fails, eliminating the `AttributeError: 'str' object has no attribute 'isoformat'` path.

Why Track This

Why It Matters

Operators and developers using volume metadata calls can avoid intermittent metadata fetch crashes, so storage automation and sync jobs are less likely to fail when a workspace file returns `last_modified` as a date string instead of a datetime. The returned timestamp format is now aligned with existing `list_volume_files` output, which reduces downstream parsing surprises; monitor for future Databricks SDK changes in `last_modified` shape and any non-HTTP-date formats that increase fallback usage.

Impact

Operators and developers using volume metadata calls can avoid intermittent metadata fetch crashes, so storage automation and sync jobs are less likely to fail when a workspace file returns `last_modified` as a date string instead of a datetime. The returned timestamp format is now aligned with existing `list_volume_files` output, which reduces downstream parsing surprises; monitor for future Databricks SDK changes in `last_modified` shape and any non-HTTP-date formats that increase fallback usage.

What To Watch Next

  • Watch whether get_volume_file_metadata becomes a repeated pattern.
  • Track follow-up changes around Code Repository Intelligence.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: databricks_sdk_last_modified_type_drift, unexpected_last_modified_format.
Open Topic TimelineOpen Technical EventOpen Original Sourcedatabricks_sdk_last_modified_type_drift / unexpected_last_modified_format / downstream_iso_parser_dependency

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

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

The change converts SDK `last_modified` HTTP-date strings to ISO 8601 and adds unit tests for the real string format, `None`, and invalid values.