GitHub user github-actions[bot] created a discussion: August 17, 2025: 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 has seen active contributions over the past week, focusing on feature additions, bug fixes, and improvements to bindings and CI workflows. Key areas of activity include enhancements to the C++ and Node.js bindings, backend integrations (e.g., OSS and S3), and CI pipeline updates to address long-term maintenance concerns. --- ## Key Ongoing Projects - **Aliyun OSS Enhancements** - #6511 by @cavivie introduces support for security tokens in Aliyun OSS, improving access control flexibility. - #6504 by @howardlau1999 allows users to specify endpoint addressing styles for OSS, enabling custom CNAME and reverse proxy configurations. - **Object Store Backend Integration** - #6283 by @flaneur2020 enables using `object_store` as OpenDAL's backend, unlocking advanced features like parallel fetching and caching. - **C++ Binding Improvements** - #6503 by @KinomotoMio implements user-configurable features for storage services, reducing binary size and improving build times. - #6505 (related issue) addresses memory leaks in the C++ binding CI pipeline, ensuring stability. - **Node.js Binding Fixes** - #6506 by @kingsword09 updates the `expires` parameter in presign methods to use `bigint`, improving precision. - #6502 by @kingsword09 fixes the prefetch option in `ReaderOptions` to align with expected behavior. - **CI Pipeline Modernization** - #6435 by @kingsword09 migrates CI images for etcd, memcached, and Redis to new sources, addressing Bitnami's upcoming restrictions on free image access. --- ## Priority Items - **Critical Bug Fixes** - #6505 by @KinomotoMio addresses memory leaks in the C++ binding CI pipeline, requiring immediate attention to ensure CI stability. - #6500 by @kenwoodjw fixes base64 validation for Azure Blob Storage, resolving a long-standing issue (#4108). - **Pending Reviews** - #6511 by @cavivie for Aliyun OSS security token support is a key feature awaiting review. - #6283 by @flaneur2020 for object_store backend integration needs final approval to unlock advanced storage capabilities. --- ## Notable Discussions - **Migrating Bitnami Images and Long-term Maintenance Strategies** - #6510: @kingsword09 initiated a discussion on alternatives to legacy Bitnami images for CI, inviting community input on sustainable solutions. - **C++ Binding Memory Leaks** - #6505: @KinomotoMio raised concerns about memory leaks detected in CI tests, with ongoing efforts to resolve the issue. --- ## Emerging Trends - **Focus on Backend Flexibility**: Multiple PRs (e.g., #6511, #6504, #6283) aim to enhance backend configurability, reflecting a trend toward more user-centric storage solutions. - **Improved Language Bindings**: Significant updates to C++ and Node.js bindings indicate a push to make OpenDAL accessible across diverse programming ecosystems. - **CI Pipeline Sustainability**: Efforts like #6435 highlight the community's focus on long-term CI stability and compatibility with external dependencies. --- ## Good First Issues - #4975: Add support for assume-role tags in S3. This task is a great way to get familiar with the S3 backend and its configuration. - #5693: Implement `Write Returns Metadata` for all services. Contributors can start with simpler services like `fs` to extend metadata extraction. - #6250: Enable feature selection for C++ bindings. Ideal for those familiar with C++ build systems, this task simplifies user-configurable builds. - #6198: Publish source and lock files for binaries. This task is approachable for contributors interested in improving the build and release process. - #5480: Refactor services to use the `backend.rs` and `core.rs` convention. A good entry point for contributors looking to improve code organization. --- We encourage new contributors to explore these issues and join the community in shaping the future of OpenDAL! GitHub link: https://github.com/apache/opendal/discussions/6512 ---- This is an automatically sent email for dev@opendal.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@opendal.apache.org
