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

Core error while doing a lot of sqlite queries

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

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
28/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
java, sqlite
领域
backend, database

调研方向

从 SQL.java 中的 com.laytonsmith.core.functions.SQL$query.getConnection 和 exec 开始,然后通过所示的 foreach/procedure 运行重复的 SQLite inserts 来重现失败。检查 SQLite 连接为何在持续查询后失败,并验证重复查询能够继续成功执行,同时不会停止其他包中的查询。

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

描述

bug

CMDHELPER-3107 - Reported by redwall_hp

I'm writing a sort of exporter script to fill a new sqlite database with a large quantity of data exported from CommandHelper's persistance.db and a Java serialized store. Functionally, everything is in working order, but when the command runs and all of the functions run in series—executing a lot of sqlite queries in the process—CommandHelper starts throwing errors like this one after 30-60 seconds of work.

I'm fairly certain that it's related to the querying, since I can take an individual one of my functions—any of several—and invoke it excessively with a for loop to trigger the same sort of error. e.g. this one:

proc(_chce_export_channel_bulletins, @channel, @bulletins,
    foreach(@bulletins, @bulletin,
        @result = query("clanchatexport", "INSERT INTO `clanchat_bulletins` (channel, message) VALUES(?, ?);", @channel, @bulletin)
    )
)

As you can see, it's just looping through an array of strings and inserting the lines. Nothing out of the ordinary. (Except I'd use transactions if CommandHelper had an API for that, instead of going about it this inefficiently...) Now, if I fed this function enough data (or cheated and invoked it with the same data and a for loop several times) the errors start coming, and CommandHelper seemingly ceases to process any sqlite queries, even from other packages.

The error in question:

[20:35:44 ERROR]: Uh oh! You've found an error in Core.
This is an error caused while running your code, so you may be able to find a workaround, but is ultimately an error in Core itself.
The line of code that caused the error was this:
@name = '[removed]'
@channel = '[removed]'
@is_manager = 0
@uuid = '[removed]'
query('clanchatexport', 'INSERT INTO `clanchat_members` (channel, uuid, name, manager, subscribed) VALUES(?, ?, ?, ?, ?);', @channel, @uuid, @name, @is_manager, 1)
on or around /CraftBukkit/CH-1.8/plugins/CommandHelper/LocalPackages/ExportClanchat/auto_include.ms:122.
Please report this error to the developers, and be sure to include the version numbers:
Server version: 1.8.8-R0.1-SNAPSHOT;
CommandHelper version: 3.3.1-SNAPSHOT.2949-;
Loaded extensions and versions:
Core (version 3.3.1);
SKCompat (version 1.0.4);
Here's the stacktrace:
java.lang.NullPointerException
    at org.sqlite.NestedDB$CausedSQLException.fillInStackTrace(NestedDB.java:649)
    at java.lang.Throwable.<init>(Throwable.java:250)
    at java.lang.Exception.<init>(Exception.java:54)
    at java.sql.SQLException.<init>(SQLException.java:140)
    at org.sqlite.NestedDB$CausedSQLException.<init>(NestedDB.java:626)
    at org.sqlite.NestedDB._open(NestedDB.java:63)
    at org.sqlite.DB.open(DB.java:86)
    at org.sqlite.Conn.open(Conn.java:140)
    at org.sqlite.Conn.<init>(Conn.java:57)
    at org.sqlite.JDBC.createConnection(JDBC.java:77)
    at org.sqlite.JDBC.connect(JDBC.java:64)
    at java.sql.DriverManager.getConnection(DriverManager.java:571)
    at java.sql.DriverManager.getConnection(DriverManager.java:233)
    at com.laytonsmith.core.functions.SQL$query.getConnection(SQL.java:136)
    at com.laytonsmith.core.functions.SQL$query.exec(SQL.java:171)
    at com.laytonsmith.core.Script.eval(Script.java:354)
    at com.laytonsmith.core.Script.eval(Script.java:323)
    at com.laytonsmith.core.Script.eval(Script.java:323)
    at com.laytonsmith.core.functions.DataHandling$foreach.execs(DataHandling.java:741)
    at com.laytonsmith.core.Script.eval(Script.java:313)
    at com.laytonsmith.core.Procedure.execute(Procedure.java:214)
    at com.laytonsmith.core.Procedure.cexecute(Procedure.java:165)
    at com.laytonsmith.core.Script.eval(Script.java:282)
    at com.laytonsmith.core.Script.eval(Script.java:323)
    at com.laytonsmith.core.functions.DataHandling$foreach.execs(DataHandling.java:741)
    at com.laytonsmith.core.Script.eval(Script.java:313)
    at com.laytonsmith.core.Procedure.execute(Procedure.java:214)
    at com.laytonsmith.core.Procedure.cexecute(Procedure.java:165)
    at com.laytonsmith.core.Script.eval(Script.java:282)
    at com.laytonsmith.core.Script.eval(Script.java:323)
    at com.laytonsmith.core.MethodScriptCompiler.execute(MethodScriptCompiler.java:1985)
    at com.laytonsmith.core.MethodScriptCompiler.execute(MethodScriptCompiler.java:1942)
    at com.laytonsmith.core.Script.run(Script.java:195)
    at com.laytonsmith.core.AliasCore.alias(AliasCore.java:167)
    at com.laytonsmith.commandhelper.CommandHelperServerListener.onServerCommand(CommandHelperServerListener.java:41)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:306)
    at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62)
    at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:502)
    at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:487)
    at net.minecraft.server.v1_8_R3.DedicatedServer.aO(DedicatedServer.java:407)
    at net.minecraft.server.v1_8_R3.DedicatedServer.B(DedicatedServer.java:375)
    at net.minecraft.server.v1_8_R3.MinecraftServer.A(MinecraftServer.java:653)
    at net.minecraft.server.v1_8_R3.MinecraftServer.run(MinecraftServer.java:556)
    at java.lang.Thread.run(Thread.java:744)
主要语言
Java
星标
128
派生
70
PR 合并指标
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

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

EngineHub/CommandHelper 的其他 Issue

查看 EngineHub/CommandHelper 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

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