| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
【MAKE】修复代码同步编译问题 | 7 个月前 | |
upload source code | 8 个月前 | |
upload source code | 8 个月前 | |
fix(function_proxy): fix codecheck violations and optimize header includes - Replace full #include with forward declarations for LocalSchedSrv, SnapCtrl, TraefikRegistry, and FunctionAgentMgr in instance_ctrl.h, instance_ctrl_actor.h, snap_ctrl.h, and snap_ctrl_actor.h to reduce compilation dependencies - Replace make_shared<IOEventActor> with shared_ptr<IOEventActor>(new ...) to support restricted constructor access in singleton actor pattern - Add static to constexpr local variable killDelayMs in exec_session_actor.cpp per codecheck static constexpr requirement fixture references accordingly Signed-off-by: ChamberlainJI <jichenglin1@huawei.com> | 2 个月前 | |
【MAKE】修复代码同步编译问题 | 7 个月前 | |
fix: master主备导致proxy偶现重启 & faas-frontend和faas-manager pod数量执行可靠性用例后未重新拉起 fix(master): master主备切换后proxy有概率重启 reason: global发生主备切换后，原主master的domain要收到registered消息再和新global建立心跳，但有概率新global在监听原主master的domain发起心跳超时前才将registered消息发出，导致新global误以为原主master的domain心跳建链超时。 solution: 当前将domian逻辑改为发出register消息后立即发起心跳请求，不等收到registered消息后再发起心跳。将主master刷新lease间隔从5s改为3s以减少长稳场景下master主备切换概率。 fix(proxy&litebus): 执行可靠性用例后，faas-frontend和faas-manager pod数量和预期相比偏少 reason:可靠性用例执行完后metastore里的/sn/instance/bussiness/yrk/tenant有2w左右残留，而且键值对的value体过大，proxy查询/sn/instance/bussiness/yrk/tenant前缀的键值对时因为返回体超过最大字节限制导致litebus和metastore断连，proxy就不能根据metastore里的信息重新拉起faas的pod。 solution: fatal状态的instance消息存到metastore时去掉args参数，增大litebus最大消息体字节数。 Signed-off-by: Tianfeng Sun <suntianfeng@huawei.com> | 5 个月前 | |
【MAKE】修复代码同步编译问题 | 7 个月前 | |
【MAKE】修复代码同步编译问题 | 7 个月前 | |
upload source code | 8 个月前 | |
【MAKE】修复代码同步编译问题 | 7 个月前 | |
feat(functionsystem): integrate Bazel build, POSIX APIs, and runtime launcher add Bazel workspace and build targets across core components migrate runtime-related protobuf definitions from proto/inner to proto/posix introduce runtime launcher, quota/snapshot management, and related tests Signed-off-by: ChamberlainJI <jichenglin1@huawei.com> | 2 个月前 | |
fix: link litebus with libutil Litebus calls openpty from exec.cpp, but liblitebus did not record libutil as one of its own shared-library dependencies. C++ function-system links happened to add util at the consumer layer, while Go/cgo only links libcpplibruntime and relies on dependent shared libraries to declare their own closure. Constraint: glibc 2.31 provides openpty from libutil rather than libc Rejected: Add -lutil only to Go CGO_LDFLAGS | keeps the litebus shared-library contract incomplete for other consumers Confidence: high Scope-risk: narrow Directive: Keep system libraries required by litebus symbols on the litebus_shared target, not only on downstream consumers Tested: bash build.sh -t off -j4 in main worktree common/litebus Tested: readelf -d common/litebus/output/lib/liblitebus.so.0.0.1 shows NEEDED libutil.so.1 Tested: LD_LIBRARY_PATH=common/litebus/output/lib ldd -r common/litebus/output/lib/liblitebus.so.0.0.1 reports no undefined symbols Not-tested: Full clean worktree litebus rebuild; clean worktree logs build lacks installed vendor include files Signed-off-by: yuchaow <wangyuchao12@huawei.com> | 1 个月前 | |
【MAKE】修复代码同步编译问题 | 7 个月前 | |
upload source code | 8 个月前 |
Mars landing. New Hasen, the intelligent coordinator of device, edge and cloud computing.