Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Build in LXC hit and miss

未关闭
#11 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
docker, go

调研方向

从 Makefile、go.mod 和 Docker 构建环境开始,对比简单构建与 Docker 构建。在独立的 Go 程序中复现 websocket 故障以及 gin-gonic/gin 依赖的行为。完成的标准是插件能够在不过度消耗资源的情况下构建,并且其 websocket 连接能够稳定工作。

由索引模型根据 Issue 内容生成。

描述

I am trying to rebuild a plugin from source. Gotify works perfectly fine in the LXC. I tried to use the gotify2telegram plugin but it is out of date, so I managed to build it from source but then it failed trying to make the websocket connection. I built it using the Makefile with the docker environment. It maxed out 2GB of RAM for over 10 minutes.

I started from the ground up to rebuild the plugin first testing it as a standalone go program. One step at a time I confirmed everything was working, but it seemed a little temperamental depending on what imports I had. If I tried importing gin-gonic/gin then it would crash similarly to when I try to build it. Turned out I didn't need that so removed it again.

When I ran a simple build then it succeeds, when I run the docker build then it also succeeds but takes much much longer. Finally, I get an error that a different version of github.com/gorilla/websockets was used but I've checked and it is v1.5.3

Secondly, during my testing, I think what causes the instability is when gin-gonic/gin is used. I'm not currently using it but if it does end up in go.mod then suddenly the program seems to stop working. Can you help troubleshoot?

主要语言
Makefile
星标
27
派生
19
PR 合并指标
30 天内没有已合并 PR

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

相似的 Issue

更多 Build System Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。