September 28, 2025: This Week in OpenDAL

[github-actions[bot]]

This weekly update is generated by LLMs. You're welcome to join our Discord for in-depth discussions.

---

Overall Activity Summary

The past week saw a mix of bug fixes, new feature proposals, and ongoing improvements to the apache/opendal repository. Contributions spanned across areas like WebAssembly (WASM) support, Azure Blob Storage enhancements, and Ruby bindings. Discussions around API design and metadata handling also gained traction.

---

Key Ongoing Projects

• WASM Support Expansion:

  • Work continues to improve support for the wasm32-unknown-unknown target, enabling OpenDAL to run in web browsers. Notable contributions include feat(services/opfs): add delete/stat support for OPFS #6564 by @crwen, which adds read/write/delete/list support for OPFS.
  • Tracking progress is centralized in Tracking issues of OpenDAL wasm32-unknown-unknown target support #3803, which outlines tasks for adding support to various services and testing WASM compatibility.

• Azure Blob Storage Enhancements:

  • fix: use local spawn on wasm targets #6597 by @HoKim98 addresses compatibility with WASM by using local spawn for wasm32 targets.
  • fix(azblob): don't call AzureStorageConfig::from_env on wasm #6594 by @bonsairobo fixes a panic issue in the Azure Blob backend when attempting to access environment variables in WASM.

• Ruby Bindings:

  • The Ruby binding for OpenDAL has been published, as seen in feat(bindings/ruby): publish ruby binding #6539 by @erickguan. This marks a significant milestone in expanding language support.

• Improved Metadata Handling:

  • new feature: Add "last access time" to Metadata #6587 by @bonsairobo proposes adding "last access time" to metadata, which could benefit file caching and garbage collection strategies.

---

Priority Items

• Critical Bug Fixes:

  • bug: Azblob backend error displays (sensitive) SAS token in plaintext #6599 by @bonsairobo highlights a security issue where Azure Blob Storage errors expose sensitive SAS tokens in plaintext. This needs immediate attention to ensure user data is protected.
  • bug: encounter "writer has not been closed or aborted, must be a bug"  #5101 by @hzxa21 addresses a persistent bug where writers are not properly closed or aborted, leading to potential data inconsistencies.

• Open PRs Requiring Review:

  • fix: use local spawn on wasm targets #6597 by @HoKim98 (WASM spawn fix) and fix(azblob): don't call AzureStorageConfig::from_env on wasm #6594 by @bonsairobo (Azure Blob WASM panic fix) are crucial for improving WASM support and need prompt reviews.

---

Notable Discussions

• API Design for Paths (Should there be a `Path` type for object paths? #6582): @bonsairobo initiated a discussion on introducing a Path type for object paths to reduce errors and improve validation. This could lead to significant API improvements.
• Switching from chrono to jiff (Switch from chrono into jiff #6584): @Xuanwo proposed migrating to jiff for time handling, citing performance and feature benefits. This could simplify dependencies and improve efficiency.

---

Emerging Trends

• Increased Focus on WASM: Several PRs and issues highlight the community's push to make OpenDAL fully compatible with WebAssembly, enabling browser-based use cases.
• Enhanced Metadata Support: There is a growing emphasis on improving metadata handling, such as adding "last access time" and extracting metadata from write responses.
• Language Bindings Expansion: The successful release of Ruby bindings signals a broader effort to make OpenDAL accessible to more programming languages.

---

Good First Issues

• WASM Support Tasks (Tracking issues of OpenDAL wasm32-unknown-unknown target support #3803): This issue tracks various tasks for adding WASM compatibility to different services. It's a great entry point for contributors interested in WebAssembly.
• Implement Write Returns Metadata (Implement Write Returns Metadata for all services #5693): Contributors can help extend metadata extraction for write responses across services. This is a straightforward task for those familiar with Rust.
• Configure Assume Role Tags in S3 (new feature: Allow s3 service to configure assume role's tags #4975): This enhancement involves adding support for configuring tags in S3 assume-role operations. It's a manageable task for those with AWS experience.
• Fix Vercel Artifacts Test Cases (servcices/vercel_artifacts: Tracking issues of not passed test cases #2198): Addressing failing test cases for the Vercel Artifacts service is a good way to get familiar with OpenDAL's testing framework.

---

Thank you to all contributors for your efforts this week! Let's keep the momentum going. 🚀