March 4

[cubxxw]

今天

已过期

• 学习 go-rod 并且完成实践(2月24日)
• 完成 config 的優化部分(2月24日)
• 继续完成 Kubernetes 的前置测试任务(2月24日)
• 继续完成 OpenIM 数据流图(2月24日)
• 繼續學習 GPT 圖解(2月24日)
• 完成副本的集群环境验证，测试，检验(2月23日, 16:00 - 2月25日, 16:30)
  • 调研优秀的开源项目如何做到最优的集群选择（IM 项目）
  • 配置一个集群环境
  • 设置 OpenIM 的集群环境中的高可用部署策略
  • 包括单节点的部署方式
  • 包括集群服务的部署方式
• PB 的修改，配置(2月23日, 16:00 - 2月25日, 16:30)
  • 调研以前的 PB 策略，以及对应的代码和文档
  • 设定 PB 的修复策略，文档和代码修改，提 issue 
  • 完成 PB 的修复
• API 中的 hash 的处理以及优化(2月23日, 18:00 - 2月25日, 18:30)
• 完成 SoraEase 的 基础文档和 CICD 建设(2月25日)
  • 完成中文提示词的 CICD 建设
  • 完成英文提示词的 CICD 建设
  • 完成中文的 README 结构化完善
  • 完成英文的 README 结构化完善
• 对社区人员的引流的方法思考(2月25日)
  对各种社区的人员的引流：

• 开发者
• Sora 的使用者

Sora 未发布各个人群的引流计划：

• 开发者
• Sora 的使用者

• 宣传方面(2月25日)
  我们需要一定的文章/视频来给我们的项目引流，提高Star数
  详细看宣传的方式 ~
  • 项目介绍文章(2月25日)
    针对我们的项目，给予相对应的项目介绍，功能介绍，优势等方面，做出宣传
  • 项目宣传视频(2月25日)
    针对我们的项目，给予相对应的项目介绍，功能介绍，优势等方面，做出宣传
  • 多平台推广(2月25日)
    在多个不同平台如：推特，抖音，B站等平台，发布视频和专栏，向感兴趣的人们推广我们的项目
• 一个专门用 sora 做视频的网站(2月25日)
  https://sora-videos.co/
• awesome-sora 仓库(2月25日)
  awesome-sora 提供 sora 的 awesome 精彩项目收集

• https://github.com/awesome-sora

• 缺少人手和生产行动力(2月25日)
  目前我们的项目中，严重缺少人手和行动力，需要尽快解决
• 制作 Sora 社群(2月25日)
  soraease.com是我们的社区域名
  • 开发者模块(2月25日)
  • 短视频创作者
• 需要学习自动化测试(2月24日 - 2月25日)
  需要编写和学习自动化测试，然后实践在项目中
• 完成 openim 的数据流图的设计(2月23日 - 2月25日)
• 学习极客时间的黑客与画家并且总结笔记 (2月23日 - 2月25日)
• 完成 SoraEase 仓库的 sora-prompt 建设(2月25日 - 2月27日)
  参考 https://github.com/f/awesome-chatgpt-prompts
  出一份中文版的仓库(sora-prompt-zh)，和一份英文版的仓库(sora-prompt)

• 中文仓库的 Sora-Prompt 的建设：https://github.com/SoraEase/sora-prompt-zh
• 英文仓库的 Sora-Prompt：https://github.com/SoraEase/sora-prompt

中文的提示词仓库参考：https://github.com/PlexPt/awesome-chatgpt-prompts-zh

• 完成 SoraEase 仓库的 UI 开发(2月25日 - 2月27日)
  项目地址： https://github.com/SoraEase/Sora-Next-Web

UI 的开发平台： https://app.appsmith.com/app/soraease-next-web/page1-65d9ae8ee22d663e2f9686b3

• 参考的项目：https://github.com/ChatGPTNextWeb/ChatGPT-Next-Web
• 可以用到的低代码平台的项目：https://github.com/appsmithorg/appsmith

实现基础组件即可，前期做好 UI

或许可以用低代码和 ChatGpt ，前端部分边学边做

• 实现 SoraEase 的抖音和快手的基础能力(2月25日 - 2月28日)
  视频上传快捷通道，打通（API/SDK）

像 bilibili 没有 API 的话，可以参考一些开源项目的实现

或者是爬虫实现

• 完成毕业设计，关注格子达(2月25日, 18:00 - 2月29日, 18:30)
• 需要将 OpenIM 的 Readme 更新一下 可以和数据流图一起更新(2月26日 - 2月29日)
• 解決 git cherry-pick 的問題(3月2日)
  git cherry-pick

这个错误发生在尝试将提交通过git cherry-pick命令应用到受保护的分支并推送到GitHub时。GitHub的受保护分支策略阻止了直接推送，要求所有的更改都必须通过Pull Request（PR）来进行。这是一种常见的做法，用于确保分支的稳定性，特别是在多人协作的项目中。

具体错误信息如下：

remote: error: GH006: Protected branch update failed for refs/heads/release-v3.5.
remote: error: Changes must be made through a pull request.

这表明你尝试直接推送到release-v3.5分支，但是这个分支是受保护的，GitHub不允许这样做。解决方案通常是创建一个新的分支，将更改应用到这个新分支上，然后通过创建一个新的Pull Request来合并这些更改到目标分支。这里是一个简化的流程：

1. 创建并切换到一个新分支：

   git checkout -b new-branch-name

2. 应用你的更改（例如，使用git cherry-pick）。

3. 推送新分支到远程仓库：

   git push origin new-branch-name

4. 在GitHub上创建一个新的Pull Request，将你的新分支合并到release-v3.5分支。

这种方法遵循GitHub的最佳实践，确保所有更改都经过审查并通过CI/CD流水线，增加了代码质量和项目稳定性的保障。

最后，操作日志显示了自动化脚本（可能是GitHub Action）在操作失败时尝试评论PR #1833，这是自动化CI/CD流程中常见的一种反馈机制，用于通知参与者存在问题。

• 完成和关小姐的新加坡线上会议交流(3月2日)
  • AI 创业相关

• 结合她的心理咨询
• 思考未来的一些 AI 发展方向

为了更好地了解关小姐在新加坡创业、技术移民要求及就业环境的最新情况，我建议设定一个会议草稿，专注于以下几个关键领域：

会议主题: 探索新加坡创业及技术移民机会

会议议程:

1. 欢迎致辞 (5分钟)

   • 主持人简短开场，介绍会议目的和参与者。

2. 关小姐的创业经历分享 (15分钟)

   • 关小姐分享在新加坡创业的经验，包括挑战、成功案例和学习经验。

3. 新加坡技术移民要求更新 (20分钟)

   • 由技术移民专家介绍最新的技术移民政策、程序和要求。
   • 讨论技术移民对于创业者的可能影响。
   • 本地人的优势
   • 各种身份

4. 新加坡就业市场现状 (20分钟)

   • 就业市场分析师提供新加坡就业市场的最新趋势、需求领域和挑战。
   • 分析如何利用现有市场趋势促进个人和企业成长。
   • 新加坡的创业氛围如何

5. 开放讨论：抓住新加坡的创业与就业机会 (30分钟)

   • 与会者讨论如何结合创业和技术移民优势，在新加坡寻找和创造机会。
   • 探讨潜在的合作机会和资源共享。

6. 会议总结与下一步行动计划 (10分钟)

   • 概括会议要点和讨论结果。
   • 规划后续行动步骤，包括可能的跟进会议或工作小组。

会议备忘:

• 请所有参会者提前10分钟加入会议，确保技术设备无误。
• 会议期间请保持麦克风静音，除非发言。
• 会议结束后，会提供会议记录和行动计划。

联系方式:

• [组织者邮箱]
• [组织者电话]
• 实现 OpenIM 的 Sealos 部署(2月28日, 16:00 - 3月3日, 16:30)

今天

• 完成毕业设计代码编写的一个核心模块(3月4日, 09:00 - 12:00)
• 整理已有的毕业设计材料和代码(3月4日, 09:00 - 12:00)
• 着手开发毕业设计的核心功能(3月4日, 14:00 - 17:00)
• 开始撰写论文的引言部分(3月4日, 19:00 - 21:00)
• 思考，DIDA 自動 sync 到 github issue (3月4日)
  • 滴答清单的开发者平台(3月4日)
    OpenAPI 的官方文档： https://developer.dida365.com/docs#/openapi

开发者中心，管理后台：https://developer.dida365.com/manage

Client ID

C2ZsxRj5zxR902RXyv

Client Secret

6N5KtC2Gvozudm9d+@J3(#gfV_5_8hGG

• 完成和优化 OpenKF 的项目(3月4日, 16:00 - 3月7日, 16:30)
  https://github.com/openimsdk/openkf
• 完成毕业设计初步开发和论文草稿撰写(3月4日 - 3月6日)

习惯

• [已打卡] Morning Run(3月4日)

已完成

• 閱讀學習 Prometheus 的文檔(2月24日)
  https://yunlzheng.gitbook.io/
• 思考一下，推薦系統是如何做的(2月24日)
  推荐系统的原理： https://zhuanlan.zhihu.com/p/451418761
• 检查并修复已知的代码问题(3月4日, 14:00 - 17:00)
• 每日记录(3月4日)
  今天是回来的第一天，今天想做的两件事情分别是：

• 去掉 gosimple, errcheck
• 完成 make lint 的错误处理
• 快速完成一些错误的包裹，完成 PR 的合并

今天上班的节奏很不错，任务都完成了，只为全力的去准备明天的工作 ~

• 完成 OpenIM 的错误码处理 (3月4日)
  完成 OpenIM 的错误码处理需要的几个步骤：

1. 解决 Tim 出现的没有错误返回值的问题
2. 解决 OpenIM 的一些错误出现的问题
3. 提升到 OpenIM 的错误处理的经过

ChatGpt 的提示词：
| 帮我优化 OpenIM 代码样式和错误处理，并且适当的关键部分添加英文注释。
在错误处理上，我希望如果错误是函数自己产生的，那么就用 Wrap 包裹，使用：

errs.Wrap(err, "prometheus start err", httpServer.Addr)

的方式包裹，并且适当携带上下文的变量信息
其中自己定义的 errs.Wrap 中 Wrap 函数为：

func Wrap(err error, msg ...string) error {
	if err == nil {
		return nil
	}
	if len(msg) == 0 {
		return errors.WithStack(err)
	}
	return errors.Wrap(err, strings.Join(msg, ", "))
}

如果错误不是自己产生的，如果是调用第三方包产生的，且第三方包没有很好的 Wrap 处理，那么你调用这个包也要做 Wrap 处理。
如果第三方包有 Wrap 处理，或者是你调用的是自己仓库的底层函数，那么就直接在最底层函数中用 Wrap ，你直接使用return err 返回 即可。
对于函数来说，如果函数需要做错误处理，但是没有错误处理，且没有返回错误的话，需要你优化函数，补充错误处理和返回。我会给你原始代码
请你尽可能的回复核心的代码，以及步骤。

来自滴答清单:
www.dida365.com

[kubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

today

expired

• Learn go-rod and complete the practice (February 24)
• Complete the optimization part of config (February 24)
• Continue to complete the pre-testing tasks of Kubernetes (February 24)
• Continue to complete the OpenIM data flow diagram (February 24)
• Continue to learn GPT diagrams (February 24)
• Complete the cluster environment verification, testing, and inspection of the copy (February 23, 16:00 - February 25, 16:30)
  • Investigate how excellent open source projects achieve optimal cluster selection (IM project)
  • Configure a cluster environment
  • Set up a high-availability deployment strategy for OpenIM in a clustered environment
  • Including single-node deployment methods
  • Including how cluster services are deployed
• Modification and configuration of PB (February 23, 16:00 - February 25, 16:30)
  • Research previous PB strategies, as well as corresponding code and documentation
  • Set PB repair strategy, document and code modifications, and issue issues
  • Completed repair of PB
• Processing and optimization of hash in API (February 23, 18:00 - February 25, 18:30)
• Complete SoraEase's basic documentation and CICD construction (February 25)
  • Completed CICD construction of Chinese prompt words
  • Completed CICD construction of English prompt words
  • Complete the structural improvement of the Chinese README
  • Complete the structured English README
• Thoughts on ways to attract community members (February 25)
  Draining people from various communities:

• developer
• Sora users

Sora has not released the traffic diversion plan for each group of people:

• developer
• Sora users

• Publicity (February 25)
  We need certain articles/videos to attract traffic to our project and increase the number of Stars
  See the promotion method in detail ~
  • Project introduction article (February 25)
    For our projects, give corresponding project introductions, function introductions, advantages, etc., and make publicity
  • Project promotional video (February 25)
    For our projects, give corresponding project introductions, function introductions, advantages, etc., and make publicity
  • Multi-platform promotion (February 25)
    Publish videos and columns on multiple different platforms such as Twitter, Douyin, Bilibili, etc. to promote our projects to interested people.
• A website dedicated to making videos using sora (February 25)
  https://sora-videos.co/
• awesome-sora repository (February 25)
  awesome-sora provides a collection of awesome awesome projects from sora

• https://github.com/awesome-sora

• Lack of manpower and production capacity (February 25)
  We currently have a serious shortage of manpower and action in our projects, which needs to be resolved as soon as possible.
• Making Sora Community (February 25)
  soraease.com is our community domain name
  • Developer Module (February 25)
  • Short video creator
• Need to learn automated testing (February 24 - February 25)
  Need to write and learn automated tests, and then practice them in projects
• Complete the design of openim's data flow diagram (February 23 - February 25)
• Learn the hackers and painters of geek time and summarize the notes (February 23 - February 25)
• Complete the sora-prompt construction of the SoraEase warehouse (February 25 - February 27)
  Reference https://github.com/f/awesome-chatgpt-prompts
  Publish a Chinese version of the warehouse (sora-prompt-zh) and an English version of the warehouse (sora-prompt)

• Construction of Sora-Prompt for Chinese warehouse: https://github.com/SoraEase/sora-prompt-zh
• Sora-Prompt for English repository: https://github.com/SoraEase/sora-prompt

Chinese prompt word warehouse reference: https://github.com/PlexPt/awesome-chatgpt-prompts-zh

• Complete the UI development of SoraEase warehouse (February 25 - February 27)
  Project address: https://github.com/SoraEase/Sora-Next-Web

UI development platform: https://app.appsmith.com/app/soraease-next-web/page1-65d9ae8ee22d663e2f9686b3

• Referenced project: https://github.com/ChatGPTNextWeb/ChatGPT-Next-Web
• Low-code platform projects that can be used: https://github.com/appsmithorg/appsmith

Just implement the basic components and prepare the UI in the early stage

Maybe you can use low code and ChatGpt and learn the front-end part while doing it.

• Implement the basic capabilities of SoraEase’s Douyin and Kuaishou (February 25 - February 28)
  Video upload shortcut channel, open (API/SDK)

If bilibili does not have an API, you can refer to the implementation of some open source projects.

Or crawler implementation

• Complete the graduation project and follow Gezida (February 25, 18:00 - February 29, 18:30)
• OpenIM's Readme needs to be updated and can be updated together with the data flow diagram (February 26 - February 29)
• Solve the problem of git cherry-pick (March 2)
  git cherry-pick

This error occurs when trying to apply commits to a protected branch via the git cherry-pick command and push to GitHub. GitHub's protected branch policy prevents direct pushes and requires all changes to be made through a Pull Request (PR). This is a common practice used to ensure the stability of a branch, especially in projects where multiple people are collaborating.

The specific error message is as follows:

remote: error: GH006: Protected branch update failed for refs/heads/release-v3.5.
remote: error: Changes must be made through a pull request.

This indicates that you tried to push directly to the release-v3.5 branch, but this branch is protected and GitHub does not allow this. The solution is usually to create a new branch, apply the changes to this new branch, and then merge the changes into the target branch by creating a new Pull Request. Here is a simplified process:

1. Create and switch to a new branch:

   git checkout -b new-branch-name

2. Apply your changes (for example, using git cherry-pick).

3. Push the new branch to the remote warehouse:

   git push origin new-branch-name

4. Create a new Pull Request on GitHub and merge your new branch into the release-v3.5 branch.

This approach follows GitHub's best practices and ensures that all changes are reviewed and passed through the CI/CD pipeline, increasing code quality and project stability.

Finally, the action log shows an automated script (possibly a GitHub Action) trying to comment PR #1833 when the action failed, a common feedback mechanism in automated CI/CD processes to notify participants of a problem.

• Completed the Singapore online meeting exchange with Ms. Guan (March 2)
  • AI entrepreneurship related

• Combined with her psychological counseling
• Thinking about some future AI development directions

In order to better understand the latest situation of Ms. Kwan's entrepreneurship, skilled immigration requirements and employment environment in Singapore, I suggest setting up a draft meeting to focus on the following key areas:

Conference Topic: Exploring Entrepreneurship and Skilled Immigration Opportunities in Singapore

Agenda:

1. Welcome Speech (5 minutes)

   • The host makes a brief opening to introduce the purpose of the meeting and participants.

2. Ms. Guan’s entrepreneurial experience sharing (15 minutes)

   • Ms. Kwan shares her experience of starting a business in Singapore, including challenges, success stories and learning experiences.

3. Singapore Skilled Migration Requirements Update (20 minutes)

   • An introduction to the latest skilled immigration policies, procedures and requirements by skilled immigration experts.
   • Discuss the possible impact of skilled immigration on entrepreneurs.
   • Advantages of locals
   • Various identities

4. Current Situation of Singapore’s Job Market (20 minutes)

   • Job market analysts provide the latest trends, demand areas and challenges in the Singapore job market.
   • Analyze how to leverage existing market trends for personal and business growth.
   • What is the entrepreneurial atmosphere in Singapore?

5. Open Discussion: Seizing Entrepreneurship and Employment Opportunities in Singapore (30 minutes)

   • Participants discussed how to combine the advantages of entrepreneurship and skilled immigration to find and create opportunities in Singapore.
   • Explore potential collaboration opportunities and resource sharing.

6. Meeting summary and next action plan (10 minutes)

   • Summarize the main points of the meeting and the results of the discussion.
   • Plan next action steps, including possible follow-up meetings or working groups.

Meeting notes:

• All participants are requested to join the meeting 10 minutes in advance to ensure that the technical equipment is correct.
• Please keep your microphone muted during the meeting unless speaking.
• After the meeting, minutes and an action plan will be provided.

Contact information:

• [Organizer’s email]
• [organizer’s phone number]
• Implementing Sealos deployment of OpenIM (February 28, 16:00 - March 3, 16:30)

today

• Complete a core module of graduation project code writing (March 4, 09:00 - 12:00)
• Organize existing graduation project materials and codes (March 4, 09:00 - 12:00)
• Start developing the core functions of the graduation project (March 4, 14:00 - 17:00)
• Start writing the introduction of the paper (March 4, 19:00 - 21:00)
• Thinking, DIDA automatically syncs to github issue (March 4)
  • Tick-Tock List’s Developer Platform (March 4)
    OpenAPI official documentation: https://developer.dida365.com/docs#/openapi

Developer center, management background: https://developer.dida365.com/manage

Client ID

C2ZsxRj5zxR902RXyv

Client Secret

6N5KtC2Gvozudm9d+@J3(#gfV_5_8hGG

• Complete and optimize OpenKF projects (March 4, 16:00 - March 7, 16:30)
  https://github.com/openimsdk/openkf
• Complete the preliminary development of graduation project and writing of thesis draft (March 4 - March 6)

Habit

• [Checked in] Morning Run (March 4)

completed

• Read and learn the documentation of Prometheus (February 24)
  https://yunlzheng.gitbook.io/
• Think about how recommendation systems work (February 24)
  Principle of recommendation system: https://zhuanlan.zhihu.com/p/451418761
• Check and fix known code issues (March 4, 14:00 - 17:00)
• Daily Record (March 4th)
  Today is the first day back. The two things I want to do today are:

• Remove gosimple, errcheck
• Complete error handling of make lint
• Quickly complete some wrong packages and complete the merge of PR

The rhythm of work today is very good. All tasks are completed. I just want to prepare for tomorrow's work with all my strength ~

• Completed OpenIM error code processing (March 4)
  Several steps are required to complete OpenIM error code processing:

1. Solve the problem that Tim has no error return value
2. Solve some errors in OpenIM
3. The process of upgrading error handling to OpenIM

ChatGpt prompt word:
| Help me optimize OpenIM code style and error handling, and add English comments to appropriate key sections.
In terms of error handling, I hope that if the error is generated by the function itself, then it can be wrapped with Wrap, using:

errs.Wrap(err, "prometheus start err", httpServer.Addr)

Wrapped in a way and appropriately carry the context variable information
The Wrap function in the self-defined errs.Wrap is:

func Wrap(err error, msg ...string) error {
if err == nil {
return nil
}
if len(msg) == 0 {
return errors.WithStack(err)
}
return errors.Wrap(err, strings.Join(msg, ", "))
}

If the error is not caused by yourself, if it is caused by calling a third-party package, and the third-party package does not have good wrapping processing, then you must also wrap it when you call this package.
If the third-party package has Wrap processing, or you are calling the bottom function of your own warehouse, then use Wrap directly in the bottom function, and you can directly use return err to return.
For functions, if the function needs to do error handling, but there is no error handling and no error is returned, you need to optimize the function and supplement error handling and return. I'll give you the original code
Please reply with the core code and steps as much as possible.

From the tick list:
www.dida365.com