artiga033
artiga033
> Hi, Thanks for the contribution. Please help us out here, how could we test this change? :) Some strings we can copy paste would be helpful here / instructions...
> I gave this a retest, since I saw it got recent commits. I have a file named "测试.txt" file on my desktop. I search for "ceshi" with Use Pinyin...
FYI `cmd.exe` and PowerShell (including the Core one which is cross-plat) does not record command execution time. PowerShell does record execution start and even ending timestamp but they are lost...
This seems to be a fix ```diff diff --git a/src/suggestions.rs b/src/suggestions.rs index 10a2b9d..1f65983 100644 --- a/src/suggestions.rs +++ b/src/suggestions.rs @@ -349,8 +349,9 @@ fn run_suggestion(shell: &str, command: &str) -> std::process::ExitStatus {...
+1 for this, especially on WoA devices there would be a slight performance drawback using the bundled x86 shim.exe. > It will be much easier to try such builds by...
> I think the best would be to leave it to "auto" at mount time, this means that ext4 specific mount options should be added only if it's really an...
I've did some further research and I believe it is totally possible. I've made some modifications to the source and it compiled. I have not tested if it works though...
> 我怀疑这一部分像头文件一样在中间加了一些00或者什么东西 至少从sqlite的实现上来讲，这几乎是不可能的，因为实际上没法判断某一列数据对应在文件的哪个字节偏移位置。应该还是你的导出过程产生的错误更有可能。比如导出的时候是否确定已经正常杀死QQ进程 一个建议是搞个root机或者模拟器然后直接去查/data看看( 以及这些“损坏的”数据在QQ客户端中是否能正常显示？如果是的话极大可能是你的导出过程有问题 --- > 把两次综合起来就能得到完整。有文字、有图片的聊天记录 这个直接用SQL就能实现，假设你已经打开了一个数据库，然后有另一个数据库文件为 `2nd.db` ```sql ATTACH DATABASE '2nd.db' AS db2; INSERT OR IGNORE INTO c2c_msg_table SELECT * FROM db2.c2c_msg_table; ``` 不过如果按你的说法这个子查询可能直接报错就是了，但是如果你知道损坏数据的具体范围的话可以改一下后面的子查询直接跳过那部分数据
> 这个文件的第153632行开始都是不可读的 这个意思是153632行以后的所有数据，还是只是中间一段，比如只是500行这样，跳过这500行直接读后面的数据是否可行(`OFFSET (153632 + 500)`) wrong # of entries in index group_msg_table_idx40027_40003_40002 wrong # of entries in index group_msg_table_idx40011_40012_40027 wrong # of entries in index group_msg_table_idx40027_40058 wrong # of...
> 本来有700w的数据，可读是130w多，删掉索引之后后面也不会显示红色的在加载中了，而是没有，直接130w是末尾了，即时左下角显示至少130w行 但是前面dump的方法是能拿到后面的数据的吗？还是也拿不到？ > 但是为什么qq能读取这个数据呢，qq读取的时候没有坏吗 思考，但如果qq能纠错的话按理讲它读过之后应该也会顺手把错误修了才对。 --- 不过也许qq确实实现了修复简单page错误的sqlite扩展，那只能等个逆向大佬了(