Errong Leng | Faith & Code — Reflections on Scripture and Software

GitHub Copilot MCP 服务器 OAuth 认证问题 - 完美解决！ 问题描述 如果你在 VS Code 中看到这个错误： ● MCP Server: github-mcp-server Type: http URL: https://api.individual.githubcopilot.com/mcp/readonly Status: ✗ Failed Error: OAuth authentication failed for github-mcp-server 你不是一个人。这个令人沮丧的错误会导致 Copilot 的高级功能不可用，即使你已经登录了 VS Code。 根本原因 这个问题源于你的 ~/.copilot/mcp-config.json 文件。如果你手动创建或编辑过这个配置文件，但没有包含 OAuth 令牌，MCP 服务器将无法进行身份验证。 以下是一个有问题的配置示例： { "mcpServers": { "github-mcp-server": { "type": "http", "url": "https://api.individual.githubcopilot.com/mcp/readonly" } } } 看到缺失的身份验证凭据了吗？那就是罪魁祸首。 最简单的解决方案（推荐） 只需删除 mcp-config.json 文件： rm ~/.copilot/mcp-config.json 然后： 打开 VS Code 如果还没有登录，请登录 GitHub Copilot 关闭并重新打开 VS Code，或重新加载窗口 就这样！当你登录时，VS Code 会自动使用正确的 OAuth 身份验证创建正确的配置。 做完这些后，你应该会看到： ...

GitHub Copilot MCP Server OAuth Authentication Issue - Solved! The Problem If you're seeing this error in VS Code: ● MCP Server: github-mcp-server Type: http URL: https://api.individual.githubcopilot.com/mcp/readonly Status: ✗ Failed Error: OAuth authentication failed for github-mcp-server You're not alone. This frustrating error can make Copilot's advanced features unavailable, even though you're signed into VS Code. Root Cause The issue stems from your ~/.copilot/mcp-config.json file. If you have manually created or edited this configuration file without including the OAuth token, the MCP server will fail to authenticate. Here's what a problematic config looks like: { "mcpServers": { "github-mcp-server": { "type": "http", "url": "https://api.individual.githubcopilot.com/mcp/readonly" } } } Notice the ...

我如何修复了 macOS 上的 GitHub Copilot CLI 连接问题 问题描述 我遇到了一个令人沮丧的问题。GitHub Copilot 在 VS Code 的聊天窗口中运行良好，但是 gh copilot CLI 命令会无限期地挂起，没有任何输出。所有命令，如 gh copilot -p "what is 2+2" 都会冻结，使 CLI 无法使用。 初始症状 ✅ GitHub Copilot 在 VS Code 中聊天功能工作正常 ✅ GitHub CLI ( gh ) 已安装并已通过身份验证 ✅ 令牌具有正确的 copilot 作用域 ❌ 任何 gh copilot 命令都会挂起并超时 ❌ 命令似乎连接但从不返回结果 诊断过程 步骤1：验证身份验证 首先，我检查了 GitHub CLI 是否已正确通过身份验证： gh auth status 输出显示我已使用 copilot 作用域登录： github.com ✓ 已登录账户 qzl-dev (keyring) - 令牌作用域：'admin:public_key', 'copilot', 'gist', 'read:org', 'repo' 身份验证不是问题。 步骤2：检查 Copilot CLI 安装 gh copilot --version CLI 已安装（版本 0.0.422），所以这也不是问题。 步骤3：查看日志 这是我发现问题的地方。我检查了 Copilot CLI 日志： cat ~/.copilot/logs/*.log | tail -50 日志显示了真正的问题： [ERROR] 发出 GitHub API 请求时出错：Error: unable to get issuer certificate; if the root CA is installed locally, try running Node.js with --use-system-ca [ERROR] 无法启动远程服务器 github-mcp-server 的 MCP 客户端: TypeError: fetch ...

How I Fixed GitHub Copilot CLI Connection Issues on macOS The Problem I encountered a frustrating issue where GitHub Copilot worked perfectly in VS Code's chat window, but the gh copilot CLI command would hang indefinitely without producing any output. All commands like gh copilot -p "what is 2+2" would just freeze, making the CLI unusable. Initial Symptoms ✅ GitHub Copilot chat in VS Code worked fine ✅ GitHub CLI ( gh ) was installed and authenticated ✅ Token had the correct copilot scope ❌ Any gh copilot command would hang and timeout ❌ Commands appeared to connect but never returned results Diagnostic Process Step 1: Verify Authentication First, I checked that my GitHub CLI was properly authenticated: gh auth status Output showed I was logged in with the copilot scope included: github.com ✓ Logged in to github.com account qzl-dev (keyring) - Token scopes: 'admin:public_key', 'copilot', 'gist', 'read:org...

Spring Boot 4 Upgrade Pitfalls Guide: Java 21, Jakarta, Jackson 3, and Copilot Automation Spring Boot 4 introduces major ecosystem changes and many teams are planning to upgrade their applications to Java 21 and Spring Boot 4.0.x . However, real-world upgrades often reveal multiple compatibility issues such as: Jakarta package migration breaking compilation Jackson 3 JSON behavior changes Spring Cloud Gateway configuration updates Test framework migration issues Micrometer / Observability runtime errors This article summarizes a production-ready upgrade strategy and demonstrates how to use GitHub Copilot Agent to automate much of the migration work. Table of Contents Why Upgrade to Spring Boot 4 Recommended Upgrade Strategy Using GitHub Copilot for Automated Migration Java 21 Upgrade Spring Boot 4 Upgrade Jakarta Migration Jackson 3 Changes Spring Cloud Gateway Changes Common Upgrade Pitfalls Upgrade Verification Checklist Why Upgrade to Spring...

Spring Boot 4 升级踩坑指南：Java 21、Jakarta、Jackson 3 和 Copilot 自动升级 Spring Boot 4 已经发布，很多团队开始计划将系统升级到 Java 21 与 Spring Boot 4.0.3 。 然而在实际升级过程中，开发者会遇到很多问题，例如： Jakarta 包迁移导致编译失败 Jackson 3 导致 JSON 反序列化变化 Spring Cloud Gateway 配置结构变化 测试依赖和注解迁移 Observability / Micrometer 监控异常 本文总结了一套 企业级 Spring Boot 4 升级流程 ， 并介绍如何使用 GitHub Copilot Agent 自动生成升级 PR。 目录 为什么升级 Spring Boot 4 升级总体策略 使用 Copilot 自动升级 Java 21 升级 Spring Boot 4 升级 Jakarta 迁移 Jackson 3 变化 Spring Cloud Gateway 配置变化 常见踩坑 升级验证 Checklist 为什么升级 Spring Boot 4 Spring Boot 4 带来了多个重要变化： 默认支持 Java 21 Jakarta API 全面替换 javax Jackson 3 JSON 生态升级 Micrometer Observability 改进 Spring Security 现代 DSL 对于长期维护的系统来说，升级可以获得： 更好的性能 更安全的依赖 更好的云原生支持 升级总体策略 升级应该按阶段进行： 升级 Java 升级 Spring Boot 进行 Jakarta 迁移 依赖版本对齐 修复配置变化 修复测试 验证运行 每一步都必须 编译 + 测试 + 启动验证 。 使用 Copilot 自动升级 对于大型代码库，手动升级非常耗时。 GitHub Copilot Agent 可以自动分析项目结构， 并生成完整升级 Pull Request。 推荐 Prompt Goal: Upgrade this project ...

Spring Boot 4 升级指南（使用 GitHub Copilot Agent） 将系统升级到 Java 21 和 Spring Boot 4.0.3 并不仅仅是简单地修改依赖版本， 而是需要一个结构化的迁移策略，以确保系统行为保持稳定，并与新的生态系统兼容。 本文提供一个适用于企业级 Spring 服务的升级流程， 结合官方迁移指南与 GitHub Copilot Agent 自动化能力， 帮助团队安全、高效地完成框架升级。 升级目标 升级至 Java 21 升级至 Spring Boot 4.0.3 对齐兼容的 Spring Cloud 版本 保持现有业务逻辑不变 继续使用 Maven 构建 确保项目可编译、测试通过并能够正常启动 升级原则 保持系统原有行为 不要删除业务逻辑 只做必要且正确的修改 遵循官方迁移指南 分阶段升级并逐步验证 官方迁移参考 所有升级操作应参考 Spring 官方迁移指南： Spring Boot 4.0 Migration Guide 使用 GitHub Copilot Agent 自动升级 对于大型代码库，使用 GitHub Copilot Agent 可以自动生成结构化的升级 Pull Request， 显著减少人工升级的复杂度。 推荐在 Agent Session 中使用高级模型（例如 Claude Opus）以获得更稳定的升级结果。 标准升级 Prompt Goal: Upgrade this service to Java 21 and Spring Boot 4.0.3. Constraints: - Preserve behavior - Keep Maven build - Do NOT remove business logic - Ensure build and tests pass Tasks: 1. Upgrade Java 2. Upgrade Spring Boot 3. Perform Jakarta migration 4. Align dependencies 5. Update configuration 6. Fix tests 7. Verify build an...

Spring Boot 4 Upgrade Guide (Using GitHub Copilot Agent) Upgrading to Java 21 and Spring Boot 4.0.3 is not just a dependency bump — it requires a structured migration strategy that preserves behavior, maintains stability, and ensures compatibility across the ecosystem. This guide outlines a production-ready upgrade framework designed for enterprise Spring services. It integrates phased migration, official Spring guidance, and GitHub Copilot Agent automation to produce clean, reviewable upgrade pull requests. Upgrade Objectives Upgrade to Java 21 Upgrade to Spring Boot 4.0.3 Align with compatible Spring Cloud version Preserve business logic Maintain Maven build Ensure compilation, tests, and successful startup Upgrade Principles Preserve existing behaviour Do NOT remove business logic Make minimal but correct changes Follow official Spring migration guidance Upgrade incrementally with validation after each phase Official Migration Reference All...

The Call of Faith: The Fig Tree, the Cleansing of the Temple, and the Power of Prayer Today afternoon’s sermon really made me reflect. I have always pictured Jesus as gentle and kind, a comforting Saviour. But I was reminded that He also challenges us, confronts hypocrisy, and calls us to real faith. The cursed fig tree made me think deeply — it’s not really about the tree, but about us. Faith can look good outwardly, but if it bears no fruit, what does it really mean? Love, kindness, patience, joy — am I living them out, or just going through the motions? The cleansing of the temple also challenged me. Worship is not about routine or appearances; it is about honouring God sincerely. Jesus saw the temple defiled by commerce and noise and acted decisively to restore it. This makes me reflect: is my worship focused on God, or distracted by habit, entertainment, or worldly concerns? The power of prayer was another key point. Jesus calls us to pray with faith, to trust that God ...

信仰的呼唤：无花果树、洁净圣殿与祷告的力量 今天下午的讲道让我深受触动。过去我总以为耶稣温和、仁慈，是我们可以依靠的安慰者。但这次我被提醒，祂也会挑战我们，面对虚伪，并呼召我们拥有真正的信仰。 被诅咒的无花果树 让我省思——这不仅仅是关于树，而是关于我自己。外表看似虔诚的信仰，如果没有结出果子，又有什么意义呢？爱、善良、耐心、喜乐，我是否真正在生活中活出来，还是只停留在表面形式？ 洁净圣殿 的故事同样提醒我，敬拜不是例行公事或表面功夫，而是要真心尊崇神。耶稣看到圣殿被商业和嘈杂玷污，祂采取行动，驱赶商人，使圣殿恢复其敬拜的本意。这让我反思，我的敬拜是否专注在神，还是被习惯、娱乐或外界干扰所取代？ 祷告的力量 也是讲道中的重点。耶稣呼召我们要以信心祷告，相信神会回应，并以宽恕的心来生活。真实的信心不是消极等待，而是大胆信靠、怀抱盼望，并从心里结出果子。 这次讲道提醒我，信仰不仅是外在的形式，而是需要真心、果效与生命的改变。我希望自己能够结出真正的属灵果子，活出一颗敬畏神、顺服神、与祂同行的心。

以温柔挽回人 今天早上的信息提醒我，与罪的争战从来不是一个人单独面对的。虽然基督已经打破了罪的权势，但罪的根仍然存在，而我常常在自己的生命中真实地感受到这种张力。有时我轻看自己的问题，有时忽视它们，有时又感到无力挣脱。听到神赐下弟兄姐妹，与我们一同面对这场争战，让我深受安慰。 我也被“温柔挽回”他人的呼召深深触动。真正属灵的关怀不是出于优越感，而是出于谦卑——承认自己的软弱，承认自己同样需要恩典。挽回不是严厉的指责，而是耐心的修补，就像修复一件受损却宝贵的事物。 我也看见自己常常因为犹豫或惧怕而沉默，本该出于爱说话的时候却没有说。爱确实遮盖许多的罪，但有时爱也会为着医治与成长而提出提醒。 最让我得安慰的是基督的心。当我们陷在罪中时，祂不是远离，而是亲近并要恢复我们。我的祷告是，愿神使我既有谦卑的心接受提醒，也有温柔的心去关怀他人。

Gently Restoring One Another This morning’s message reminded me that the struggle against sin is not meant to be fought alone. Though Christ has broken sin’s rule, its roots still remain, and I often feel that tension in my own life. Too easily I downplay my struggles, ignore them, or feel defeated by them. It was comforting to be reminded that God gives us fellow believers to walk alongside us in this battle. I was especially challenged by the call to gently restore others. True spiritual care doesn’t come from superiority, but from humility — recognizing my own weakness and my need for grace. Restoration is not harsh correction, but patient mending, like repairing something precious that has been damaged. I also saw how often fear or hesitation keeps me silent when love should speak. Love does cover many sins, but sometimes love also confronts, for the sake of healing and growth. Most encouraging of all is the heart of Christ. When we are caught in sin, He is not repelled — H...

清楚看见人性 刚刚过去的主日下午的一篇讲道，真的让我停下来好好想想什么是“人”。牧师说我们是“活生生的矛盾体”，我觉得太贴切了。一方面，人类能做惊人的事情——探索太空、进行复杂手术、创造美丽的音乐和艺术。另一方面……我们也会伤害别人，打战争，对亲近的人不友善。真的很乱。 讲道中提到，上帝按照自己的形象创造了我们——原本是好的，能够认识祂、爱祂，并与祂同住。亚当和夏娃在伊甸园里与上帝同行，享受祂的同在。上帝的形象在我们身上，就像一幅原本完美的画，现在有了裂痕。虽然罪败了我们，但这形象依然存在。 我想到了身边的人——邻居、朋友，甚至陌生人。有时我们很容易看到他们的缺点、自私、破碎。但通过上帝的眼睛来看，即使在缺陷中，他们身上仍然有祂的形象。这让我很受触动。 希望是什么？讲道提醒我，上帝还没有放弃我们。祂修复、更新，呼召我们回到与祂的关系里。即使我们觉得自己渺小、软弱或凌乱，上帝仍然看见我们反映祂荣耀的潜力。 听完之后，我心里充满了敬畏和谦卑。敬畏人类在反映上帝时的美好，谦卑面对自己的缺点。但也有希望——因为上帝的恩典能够触及我们每一个人。

Seeing Humanity Clearly I just finished listening to the past Sunday afternoon sermon that really made me pause and think about what it means to be human. The preacher said we are a “living paradox,” and I couldn’t agree more. On one hand, humans do amazing things — explore space, perform complex surgeries, create beautiful music and art. On the other hand… we hurt each other, fight wars, and can be unkind to those closest to us. It’s messy. The sermon talked about how God made us in His image — created good, meant to know Him, love Him, and live with Him. Adam and Eve walked with God in the garden, enjoying His presence. God’s image in us is like a perfect painting that has developed cracks over time. Sin has marred us, but the image is still there. I thought about the people around me — neighbors, friends, even strangers. Sometimes it’s easy to see their flaws, selfishness, and brokenness. But through God’s eyes, even in their imperfections,...

选择忠心，而不是捷径 这篇讲道让我重新思考一件事：当目标看起来是好的时候，“走容易的路”是多么有吸引力。 关于耶稣受试探的信息提醒我，并不是每一个看起来有意义、有价值的机会都应该被接受。 最触动我的是主耶稣那简单却坚定的回应：单单敬拜神。 没有妥协，没有讨价还价，没有通往荣耀的捷径。 祂信靠天父的道路，即使那条路不是立刻得胜，而是先经过苦难。 作为一个普通的基督徒，我常常发现自己想要没有代价的结果—— 想要成长却不愿等待，想要影响力却缺少谦卑，想要安逸却不愿交托。 这篇讲道提醒我，神的国不是靠快速成功建立的，而是建立在忠心与敬拜之上。 忠心也许看起来安静而缓慢，但绝不会徒然。 前面的道路仍然很清楚：敬拜神，信靠祂的时间，并且拒绝那些捷径。

Choosing Faithfulness Over Shortcuts This sermon made me reflect on how tempting the “easy way” can feel — especially when the goal itself seems good. The message about the temptation of Jesus Christ reminded me that not every opportunity is meant to be taken, even when it looks meaningful or impressive. What struck me most was how simple His response was: worship God alone. No negotiation, no compromise, no shortcuts to glory. He trusted the Father’s way, even when that path led through suffering instead of immediate victory. As a regular Christian trying to live faithfully, I see how often I want results without the cost — growth without patience, influence without humility, comfort without surrender. This sermon reminded me that God’s kingdom isn’t built on quick wins. It’s built on devotion. Faithfulness may look quiet and slow, but it is never wasted. The way forward is still the same: worship God, trust His ti...

Righteousness in Christ How often do we try to earn God’s approval with our own goodness? Helping others, going to church, trying to live a “good life”—all of these efforts, though well-intentioned, cannot make us righteous before a perfectly holy God. The Bible tells us that righteousness is not something we can achieve on our own. Abraham, the father of faith, was counted righteous because of his trust in God, not because of his flawless life. Paul, with all his discipline and religious accomplishments, realized that without Christ, all his efforts were worthless in God’s eyes. The good news is this: Christ Himself becomes our righteousness. Salvation is not about personal goodness; it’s about trusting in Jesus, who covers our sins and makes us right before God. Faith is the instrument through which we receive this gift—it’s the hand that reaches out to Christ, not the source of righteousness itself. Once we believe, we are fully accepted in Christ. This freedom allows u...

基督里的义 我们常常尝试靠自己的善行赢得上帝的认可：帮助别人、去教会、努力过“好”的生活——这些努力虽然出于好意，但都无法让我们在完全圣洁的上帝面前称义。 圣经告诉我们，义不是我们自己能达到的。信心之父亚伯拉罕因相信上帝而被算为义，并不是因为他过着完美的生活。保罗拥有极高的纪律和宗教成就，却意识到，没有基督，他的一切努力在上帝眼中都是无价值的。 好消息是： 基督自己成为我们的义 。救恩不是靠个人的善行，而是信靠耶稣，他为我们担当罪，使我们在上帝面前称义。信心是我们接受这一恩典的工具——是伸出的手，而不是义本身的来源。 一旦我们相信，我们就在基督里完全被接纳。这自由让我们顺服上帝，不是为了赢得认可，而是出于爱与感恩。每一件善行、每一次服事，都是源于我们已经在基督里得到的义，而不是为了争取称义。 要点总结： 义唯有基督而来。 信心是接受义的途径，而非义的来源。 人的努力无法在上帝面前称义。 在基督里生活带来自由、爱与荣耀上帝的渴望。 今天，让我们安息在这个真理里：我们在上帝眼中的接纳，不取决于我们做了什么，而是基于基督已经为我们成就的一切。

When Warning Is Love The sermon began with a strong declaration from the book of Jude: “Woe to them.” The message unfolded around one central truth—our spiritual direction matters, and the path we walk ultimately reveals where we are headed. Through examples from history, images from nature, and references to ancient writings, the sermon kept returning to the same point: what appears appealing, easy, or harmless is not always life-giving. Discernment is necessary, even in places that feel familiar and safe. One idea that stayed with me was the warning about hidden danger. Not every influence that feels encouraging or comfortable actually leads toward spiritual growth. Some voices sound pleasant but gradually shift our focus away from what is true. This raised simple but honest questions for reflection: Is faith in my life a habit or a living reality? Do I welcome correction, or only affirmation? Am I growing, or merely maintaining appearances? The sermon also used viv...

当警告也是一种爱 这次讲道从犹大书的一句严肃宣告开始：“他们有祸了。”整段信息围绕一个核心展开——人所走的道路，最终都会显明方向与结局。 讲员从历史人物、自然图像和古代文献三个角度，一次次回到同一个重点：远离神的生命，看起来可能吸引人、轻松甚至合理，但最终是空的，也是危险的。 让我印象最深的是关于“隐藏危险”的提醒。那些看起来没有问题、甚至让人感觉舒服的声音，并不一定真正带来生命。有些影响不会立刻显出破坏力，却会慢慢让人偏离方向。 这让我开始反思：信仰对我来说，是习惯，还是生命？是外在参与，还是内在真实？我是否愿意接受提醒，还是只愿听让人轻松的话？ 讲道也用了许多自然界的比喻：没有雨的云、不结果子的树、漂流不定的星。这些画面都指向一个共同点——外表存在，却没有真正的生命供应。听到这里，很难不问自己：我的生命有没有带来一点真实的果子？ 关于审判的信息听起来不轻松，但整篇信息给我的感受不是压迫，而是认真。真正关心人的提醒，不只是安慰，也包含警醒。因为如果方向错了，再轻松的路也不会带到正确的地方。 这次听道留下的一个简单祷告是：愿意被提醒，愿意被修正，也愿意继续走在正确的方向上。 信仰不是一次决定，而是每天的道路。

一次数据清理引发的教训：缺失外键索引导致 DELETE 性能问题 最近在做一次数据清理（data purge）时，我遇到了一个之前没有预料到的问题。 从业务逻辑上看，这只是一个很普通的 DELETE 操作，根据条件删除历史数据而已。 但实际执行时， DELETE 语句几乎卡住了 。 没有报错，看起来也在运行，但迟迟没有完成。 问题出在哪里？ 在 DBA 的帮助下，我们开始从数据库层面分析这个问题。 最终发现，真正的原因是： 部分外键（Foreign Key）字段缺少对应的索引。 在 Oracle 中，当对父表执行 DELETE 操作时，数据库需要检查子表中是否存在 引用该记录的外键数据。 如果外键列没有索引，Oracle 就只能对子表做全表扫描。 当数据量变大时，这种全表扫描会极大地拖慢 DELETE 操作， 甚至导致长时间锁表，看起来就像 SQL “卡住”了一样。 解决方案 在确认问题后，我们为所有缺失的外键字段补充了索引（涉及多个关联表）。 效果非常明显： DELETE 操作执行速度大幅提升 锁定时间明显缩短 数据库整体负载显著下降 SQL 没变，数据没变，只是补了索引，结果却完全不同。 如何定位缺失的外键索引 DBA 使用下面的 SQL 来检查哪些外键约束没有对应的索引。 以下示例中，schema 名、表名和索引名均已做匿名处理。 WITH fk_constraints AS ( SELECT c.table_name, c.constraint_name AS fk_name, LISTAGG(c.column_name, ', ') WITHIN GROUP (ORDER BY c.position) AS fk_columns FROM dba_cons_columns c JOIN dba_constraints k ON k.constraint_name = c.constraint_name WHERE k...

A Lesson Learned: Slow DELETE Caused by Missing FK Indexes Recently, I was working on a data purge task. The logic itself was simple: delete old records based on certain conditions. I had done similar work before, so I did not expect any major issues. However, this time the DELETE operation got stuck . No errors were reported, but the SQL just kept running without making progress. What Happened? With help from our DBA, we started investigating the issue at the database level. After some analysis, we identified the root cause: Several foreign key (FK) columns were missing supporting indexes. Because of this, every DELETE on a parent table forced Oracle to perform full table scans on related child tables to validate referential integrity. As data volume increased, the performance impact became severe. The Fix After adding indexes on the missing foreign key columns (across related tables), the results were immediate: DELETE operations completed much faster ...

权力会消逝，但神永存 今天下午的讲道提醒我： 人类的权力是短暂的，但神的权能永远长存 。 尼布甲尼撒王拥有强大的帝国、财富和军队， 但他内心仍然惧怕，因为他知道自己只是一个人。 他梦见一尊由金、银、铜、铁和泥土组成的像， 这说明即使最强大的王国， 最终也会衰败和消逝 。 这教导我们： 神震动人虚假的安全感 。 我们可能信靠金钱、地位或政府， 但这些都不是永恒的， 它们会像梦中的像一样被毁灭。 然而，神也 显明真正的意义 。 但以理和他的朋友们祷告、信靠神， 而不是依靠人的智慧。 神向他们启示了梦和梦的解释： 那块击碎像的石头， 象征 神永恒的国度 ， 并在耶稣基督里得以成全。 与人类的权力不同， 神的国永不衰败、永不失败， 不受时间或帝国的影响。 这也提醒我反思： 我把信心放在哪里？ 是在短暂的事物上， 还是在神身上？ 唯有信靠祂， 我才能得到真正的平安和生命的意义。 唯有基督所成就的事才永远长存。 我们的生命和行为有意义， 是因为它们是祂工作和国度的一部分。 阿们。

Power Fades, God Remains Today’s sermon reminded me that human power is temporary, but God’s power lasts forever . King Nebuchadnezzar had a great empire, wealth, and armies, yet he was afraid because deep inside he knew he was only human. His dream of the statue made of gold, silver, bronze, iron, and clay showed that even the strongest kingdoms will fall and fade . This teaches us that God shakes false security . We may trust money, positions, or governments, but these things are not eternal. They can be destroyed, just like the statue in the dream. But God also reveals real meaning . Daniel and his friends prayed and trusted God instead of relying on human wisdom. God revealed the dream and its interpretation: the stone that destroys the statue represents God’s eternal kingdom , fulfilled in Jesus Christ. Unlike human power, God’s kingdom never fades, never fails, and is not threatened by time or empires. This calls me to ask myself: Where do I put my confidence...

听道反思：我是“做梦的人”，还是“挖掘的人”？ 今天听完犹大书的信息，有一个问题一直在我心里回响： 我是在依靠神的话，还是在依靠自己的感觉？ 犹大并没有把假教师描述成不属灵或不敬虔的人，反而称他们是“依靠自己梦的人”。问题不在于他们有没有属灵经历，而在于他们把经历当成了权柄。 这让我反思自己。很多时候，我也是凭感觉做决定——只要我觉得平安、舒服、有把握，就认为这是从神来的。但今天的信息提醒我：感觉不是根基，神的话才是。 从人的角度看，罪不是抽象的，它真实地污染我们自己。而这种污染，并不只来自明显、公开的罪，也来自日常生活中看似无害的习惯。 比如不断刷抖音、短视频，随意浏览网页，让大量碎片化、刺激性的内容充满我们的眼睛和思想。没有人强迫我们这样做，但久而久之，这些内容正在塑造我们的欲望，使我们对神变得迟钝。我们每天所“消费”的内容，从来都不是中立的，不是在塑造我们，就是在扭曲我们。 从神的角度看，不顺服从来不是小问题。当我选择按自己的方式生活，其实是在把主权从基督手中拿走，放在自己身上。我口里承认祂是主，生活中却常常自己当王。 从天使的角度看，更让我感到羞愧。连天使都不敢轻看神的权柄，而我却有时用“现在是恩典时代”来为自己的不顺服辩护。犹大提醒我，这不是自由，而是骄傲。 但感谢神，信息没有停留在责备中。耶稣已经成全了律法。律法不再是控告我的审判官，而是在基督里，成为引导我如何生活的蓝图。 当撒但控告我时，我的回应不在于我做得够不够好，而在于基督已经为我成就了一切。顺服不再是换取生命的条件，而是已经得着生命后的回应。 今天我被提醒：不要满足于做梦，要甘心挖掘；不要只问“我感觉如何”，而要问“神已经说了什么”。 愿神帮助我继续活在祂话语的权柄之下，让我的生命不再制造属灵的污染，而是因基督的恩典，散发出更新与生命的气息。

Reflection on Jude: Am I Dreaming, or Digging? After hearing today’s message from the book of Jude, one question stayed with me: Am I grounding my life in God’s Word, or in my own feelings? Jude does not describe false teachers as irreligious or unspiritual people. Instead, he calls them those who “rely on their dreams.” The problem is not that they lack spiritual experiences, but that they treat those experiences as their authority. That hit close to home. I often make decisions based on how I feel—peaceful, comfortable, confident—and assume that must mean God is leading me. But today’s message reminded me that feelings are not a foundation. God’s Word is. Jude shows us the consequences of ignoring God’s Word from three perspectives. From the human perspective, sin is not abstract—it pollutes us. And this pollution does not only come from obvious, public sins. It also comes through ordinary, everyday habits. Endlessly scrolling TikTok or short videos, casually browsing...

解决 react-native-tts Android 构建失败：Could not find method jcenter() 在运行 React Native Android 项目时，我遇到了如下构建错误： A problem occurred evaluating project ':react-native-tts'. > Could not find method jcenter() for arguments [] on repository container of type 错误发生在执行以下命令时： ./gradlew app:installDebug 根据错误信息，问题最终定位到了以下文件： node_modules/react-native-tts/android/build.gradle 问题原因分析 jcenter() 已经被 Gradle 官方弃用，并在较新的 Gradle 版本中被移除。 但部分较老的 React Native 第三方库仍然在 Android 配置中使用 jcenter() ，这会直接导致 Android 构建失败。 本次出问题的正是 react-native-tts 这个库。 为什么不能直接改 node_modules？ 直接修改 node_modules 中的代码虽然可以暂时解决问题，但并不可靠。 以下操作都会导致修改丢失： 重新执行 npm install 重新执行 yarn install 删除并重建 node_modules 因此，我们需要一种 可重复、可维护、对团队友好 的解决方案。 正确的解决方案：patch-package patch-package 是一个非常实用的工具，可以让我们对第三方依赖进行补丁修复，并在每次安装依赖时自动应用这些修改。 在 react-native-tts 官方修复之前，这是一个非常稳妥的方案。 修复步骤详解 1. 安装 patch-package npm install patch-package --save-dev 或者使用 Yarn： yarn add patch-package --d...

Fixing react-native-tts Android Build Error: Could Not Find Method jcenter() While running a React Native project on Android, I encountered the following build error: A problem occurred evaluating project ':react-native-tts'. > Could not find method jcenter() for arguments [] on repository container of type The build failed when running: ./gradlew app:installDebug After checking the stack trace, the error clearly pointed to the following file inside node_modules : node_modules/react-native-tts/android/build.gradle Why This Error Happens jcenter() has been deprecated and removed in newer versions of Gradle. However, some older React Native libraries still reference it. In this case, the library react-native-tts was still using jcenter() in its Android Gradle configuration, which caused the build to fail immediately. The Tempting but Wrong Fix You can temporarily fix the issue by directly editing the file inside node_modules — but this so...

iTrans – Fast iPhone Photo & Video Transfer for macOS Do you find Photos.app slow or cluttered when backing up your iPhone photos and videos to your Mac? I built iTrans , a lightweight macOS utility that lets you transfer your media directly into folders on your Mac — fast, simple, and without the extra bloat. How iTrans Works Plug in your iPhone Open iTrans Select photos and videos to transfer Choose the destination folder on your Mac Click transfer — done! iTrans is perfect for quick media backups, organizing photos without importing them into Photos.app, or simply moving videos off your iPhone in a flash. Demo Video Check out this short demo showing iTrans in action: Support iTrans To publish iTrans on the Mac App Store, Apple requires a $99 annual Apple Developer Program fee. If you find iTrans useful and want to support its release, you can contribute here: Support iTrans – Help Publish on the Mac App Store Even if you can't contrib...

January Traffic Snapshot: Faith & Code Across the World As January comes to a close, I want to take a moment to reflect on how Faith & Code — Reflections on Scripture and Software has been read and accessed over the past month. 📈 Overall Engagement In January, the blog recorded 8.89K total pageviews . Traffic remained steady throughout the month, with a notable peak in mid-January, suggesting that certain posts resonated more strongly during that period. Rather than relying on a single spike, the overall pattern reflects consistent readership. 🌍 Global Readership The blog continues to reach readers across the world: It’s humbling to see reflections on faith, confession, and vocation being read across cultures and time zones. 💻 Pageviews by Operating Systems Readers accessed the blog using a wide variety of operating systems: The balance between desktop and mobile platforms reflects a readership engaging both in focused reading and on-the-go moments. 🌐...