dev January 2022

dev@openharmony.io

17 participants
33 discussions

欢迎参加OpenHarmony Driver-SIG例会，2022/01/05 15:00-16:00(GMT+08:00) 中国标准时间 - 北京, 每两周 (周三)

by liufeihu (kevin)

OpenHarmony Driver SIG例会会议时间： 01月05日（周三）15:00-16:00 会议主题： OpenHarmony Driver SIG例会会议议题 1、Media的codec驱动能力开发进展。时间：15:00-15:20 汇报人：张国荣 2、camera模块新增1个HDI接口评审。时间：15:20-15:35 汇报人：言银 3、Audio模块新增HDI接口评审. 时间：15:35-15:50 汇报人：张云虎欢迎大家申报会议议题： https://etherpad.openharmony.cn/p/SIG-Driver 会议接入：会议链接：https://welink.zhumu.com/j/178828985 加入会议(External)<https://welink.zhumu.com/j/178828985> 会议ID 0178828985

2 years, 3 months

Re：部分仓在 OpenHarmony GitHub镜像上未公开，导致代码获取失败 | Certain repos are not public on OpenHarmony Github mirror, casuing code fetch failure

by Goldenboy

请明帅协助看看是什么原因 Original From:"Jianyu Liu via dev"< dev(a)openharmony.io >; Date:2022/1/3 22:33 To:"dev"< dev(a)openharmony.io >; CC:"community(a)openharmony.io"< community(a)openharmony.io >; Subject:[Dev] 部分仓在 OpenHarmony GitHub镜像上未公开，导致代码获取失败 | Certain repos are not public on OpenHarmony Github mirror, casuing code fetch failure 各位新年好，参照获取源码.md中的获取方式4 - 方式二，从OpenHarmony GitHub镜像仓获取代码时，下载会卡在 95% （ Fetching: 95% (264/276) vendor_ohemu）。后会显示错误代码： fatal: Authentication failed for 'https://github.com/openharmony/third_party_egl/' fatal: Authentication failed for 'https://github.com/openharmony/third_party_opengles/' fatal: Authentication failed for 'https://github.com/openharmony-sig/third_party_tinyalsa/' 以上三个仓在Gitee上是开源仓，但在GitHub上则需授权访问。这个问题已有同事在oschina 开源中国的仓下反馈（Issue链接）。因为不确定该在OpenHarmony Gitee的哪个仓下反馈，所以在dev 邮件列表反馈。希望可以尽快修复。谢谢。祝好，刘建宇 Hello guys, happy new year. Followingsourcecode-acquire.md Method 4 – Method 2, to acquire source code from OpenHarmony GitHub mirror, it constantly stuck at 95% (Fetching: 95% (264/276) vendor_ohemu ). Based on the error info: fatal: Authentication failed for 'https://github.com/openharmony/third_party_egl/' fatal: Authentication failed for 'https://github.com/openharmony/third_party_opengles/' fatal: Authentication failed for 'https://github.com/openharmony-sig/third_party_tinyalsa/' It seems like those 3 repos are not public and require access authentication. Yet those same 3 repos are public accessable on OpenHarmony Gitee. This issues is already reported by others under oschina Gitee (Issue link ). Since I’m not sure which OpenHarmony repo this issue should be reported to, hence dev mailing list. Looking forward for the fix. Thanks. Best, Jianyu Liu

2 years, 3 months

部分仓在 OpenHarmony GitHub镜像上未公开，导致代码获取失败 | Certain repos are not public on OpenHarmony Github mirror, casuing code fetch failure

by Jianyu Liu

各位新年好，参照获取源码.md<https://gitee.com/openharmony/docs/blob/master/zh-cn/device-dev/get-code/so…> 中的获取方式4 - 方式二，从OpenHarmony GitHub 镜像仓获取代码时，下载会卡在 95% （ Fetching: 95% (264/276) vendor_ohemu ）。后会显示错误代码： fatal: Authentication failed for 'https://github.com/openharmony/third_party_egl/' fatal: Authentication failed for 'https://github.com/openharmony/third_party_opengles/' fatal: Authentication failed for 'https://github.com/openharmony-sig/third_party_tinyalsa/' 以上三个仓在Gitee上是开源仓，但在GitHub上则需授权访问。这个问题已有同事在 oschina 开源中国的仓下反馈（Issue链接<https://gitee.com/oschina/git-osc/issues/I4P4QE>）。因为不确定该在OpenHarmony Gitee的哪个仓下反馈，所以在 dev 邮件列表反馈。希望可以尽快修复。谢谢。祝好，刘建宇 ________________________________ Hello guys, happy new year. Following sourcecode-acquire.md<https://gitee.com/openharmony/docs/blob/master/en/device-dev/get-code/sourc…> Method 4 – Method 2, to acquire source code from OpenHarmony GitHub mirror, it constantly stuck at 95% ( Fetching: 95% (264/276) vendor_ohemu ). Based on the error info: fatal: Authentication failed for 'https://github.com/openharmony/third_party_egl/' fatal: Authentication failed for 'https://github.com/openharmony/third_party_opengles/' fatal: Authentication failed for 'https://github.com/openharmony-sig/third_party_tinyalsa/' It seems like those 3 repos are not public and require access authentication. Yet those same 3 repos are public accessable on OpenHarmony Gitee. This issues is already reported by others under oschina Gitee ( Issue link<https://gitee.com/oschina/git-osc/issues/I4P4QE> ). Since I’m not sure which OpenHarmony repo this issue should be reported to, hence dev mailing list. Looking forward for the fix. Thanks. Best, Jianyu Liu

2 years, 3 months

2024

2023

2022

2021

2020

dev January 2022