GitHub user github-actions[bot] created a discussion: February 08, 2026: This 
Week in OpenDAL

*This weekly update is generated by LLMs. You're welcome to join our 
[Discord](https://opendal.apache.org/discord/) for in-depth discussions.*

---

## Overall Activity Summary
The `apache/opendal` repository saw significant activity this week, with 
contributions focused on feature enhancements, bug fixes, and refactoring 
efforts. Key areas of focus included the development of new APIs (e.g., 
`undelete` and timeout handling), improvements to Python bindings, and updates 
to Azure Blob Storage capabilities. Several contributors actively participated 
in discussions and PRs, showcasing the vibrant and collaborative nature of the 
community.

---

## Key Ongoing Projects
- **`undelete` API for Azure Blob Storage**:
  - #7178 by @NikitaMatskevich introduces the `undelete` operation for Azure 
Blob Storage, enabling the restoration of soft-deleted files. This is part of 
the broader object versioning initiative (#4321).
  
- **Timeout Handling Refactor**:
  - #7179 by @dheeraj12347 refactors the timeout logic to be internal to the 
`TimeoutLayer`, improving encapsulation and reducing core dependencies.
  
- **Python Bindings Enhancements**:
  - #7180 by @frostming improves typing discovery and resolves issues with the 
`__version__` attribute in the Python package.
  - #7181 by @chitralverma refactors Python bindings, simplifying APIs and 
preparing for future reorganization.

- **Soft Delete Listing in Azure Blob Storage**:
  - #7151 by @NikitaMatskevich implements the `list_with_deleted` operation for 
Azure Blob Storage, allowing users to list soft-deleted blobs.

---

## Priority Items
- **Review and Merge Open PRs**:
  - #7178 by @NikitaMatskevich: Implements the `undelete` operation for Azure 
Blob Storage.
  - #7181 by @chitralverma: Refactors Python bindings for better 
maintainability and prepares for future changes.
  - #7179 by @dheeraj12347: Refactors timeout logic to improve architecture.

- **Discussion on AI Usage Guidelines**:
  - #6795 by @Xuanwo: Establishing guidelines for responsible AI usage in the 
project.

---

## Notable Discussions
- **Object Versioning and `undelete` API**:
  - #4321 by @Xuanwo: Discusses the design and implementation of the `undelete` 
API, which is critical for restoring deleted files in cloud storage services.

- **Per-Operation Timeout**:
  - #7168 by @dentiny: Explores the feasibility of implementing per-operation 
timeout settings to provide more granular control over operation durations.

- **AI Usage Guidelines**:
  - #6795 by @Xuanwo: Proposes guidelines for using AI tools in contributions 
to ensure quality and maintainability.

---

## Emerging Trends
- **Focus on Azure Blob Storage Enhancements**: Multiple PRs and issues are 
centered around improving Azure Blob Storage support, including `undelete` and 
soft delete listing capabilities.
- **Increased Use of AI in Development**: Discussions and contributions 
indicate a growing reliance on AI tools for code generation and issue 
resolution, prompting the need for clear guidelines.
- **Python Bindings Maturity**: Significant efforts are being made to enhance 
Python bindings, indicating a push to improve usability and adoption for Python 
developers.

---

## Good First Issues
- **#4976**: Allow S3 service to configure assume role's `duration-seconds`. 
This issue involves adding support for configuring the duration of assume role 
sessions in the S3 service. It’s a good entry point for contributors familiar 
with AWS and Rust.
- **#4975**: Allow S3 service to configure assume role's tags. Similar to 
#4976, this issue focuses on enabling tag configuration for assume roles in S3.
- **#6829**: Tracking issues for RFC-6828: Core. This involves splitting 
services and layers into separate crates, which is a great way to get familiar 
with the codebase structure.
- **#5693**: Implement `Write Returns Metadata` for all services. Contributors 
can work on extracting metadata from write responses for specific services, a 
straightforward task with clear guidelines.
- **#2611**: Tracking issues of RFC: Object Versioning. This involves 
implementing object versioning for various services, a critical feature for 
data safety and recovery.

--- 

New contributors are encouraged to tackle these approachable issues to 
familiarize themselves with the project and make meaningful contributions.

GitHub link: https://github.com/apache/opendal/discussions/7183

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to