[U] Update channel content
This commit is contained in:
@@ -2,7 +2,7 @@
|
||||
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="zh-cn">
|
||||
<id>https://aza.moe/life</id>
|
||||
<title>小桂桂的回忆录 📒</title>
|
||||
<updated>2024-11-24T08:10:19.323668+00:00</updated>
|
||||
<updated>2024-11-24T10:12:53.258021+00:00</updated>
|
||||
<link href="https://aza.moe/life" rel="alternate"/>
|
||||
<generator uri="https://lkiesow.github.io/python-feedgen" version="0.9.0">python-feedgen</generator>
|
||||
<logo>https://aza.moe/meru_256px.png</logo>
|
||||
|
||||
File diff suppressed because one or more lines are too long
+11
-11
@@ -56960,7 +56960,7 @@
|
||||
"id": 4178,
|
||||
"date": "2024-07-19T15:36:21",
|
||||
"text": "测试了半天百度翻译,百度翻译确实没有英语歧义的问题\n\n...因为百度的中转语言是中文,当然没有英语歧义的问题,只有中文歧义的问题 🌚\n\n\"Beat a car\" > 「打车」 > 「タクシーを拾う」 (\"Take a taxi\")\n\n不过感觉中文确实比英文更难出现歧义,而且因为亚洲语言离中文更近,感觉百度翻译翻亚洲语言的准确率肯定比英语中转的 Google / DeepL 高",
|
||||
"views": 86,
|
||||
"views": 87,
|
||||
"forwards": 0,
|
||||
"reply": {
|
||||
"id": 4174,
|
||||
@@ -57014,7 +57014,7 @@
|
||||
"id": 4182,
|
||||
"date": "2024-07-20T09:18:30",
|
||||
"text": "好吧又仔细查了一下,Github 上有人开了 issue,他们的结论是这是 AMD Zen4 显卡驱动 Adrenaline 24 的 bug,会让所有结束了的进程变成僵尸进程释放不出去... 大家给 docker 丢锅只是正好 docker 结束进程比较频繁而已\n\n试了从 24.4 更新到 24.7.1,不知道会不会好",
|
||||
"views": 92,
|
||||
"views": 93,
|
||||
"forwards": 1,
|
||||
"reply": {
|
||||
"id": 4179,
|
||||
@@ -57026,7 +57026,7 @@
|
||||
"id": 4183,
|
||||
"date": "2024-07-20T09:44:20",
|
||||
"text": "草 \n\n我: 在 /gen 请求参数面加了一个变量,你加一下\nsyama: 我找找,是这个类吗 GenerateResponse... 好像是返回类。找不到欸 <i class=\"custom-emoji\" emoji-src=\"emoji/6323412532367198064.webp\">🍔</i>",
|
||||
"views": 96,
|
||||
"views": 97,
|
||||
"forwards": 0,
|
||||
"images": [
|
||||
{
|
||||
@@ -57045,7 +57045,7 @@
|
||||
"id": 4184,
|
||||
"date": "2024-07-20T11:05:17",
|
||||
"text": "感觉是怎样设计模型都绕不开的问题",
|
||||
"views": 94,
|
||||
"views": 95,
|
||||
"forwards": 0,
|
||||
"images": [
|
||||
{
|
||||
@@ -57179,7 +57179,7 @@
|
||||
"id": 4193,
|
||||
"date": "2024-07-21T14:01:31",
|
||||
"text": "楼下新开了一家米线店,原来直接用廉价建材装修成「很老旧装修的气氛」也能很好看 quq",
|
||||
"views": 81,
|
||||
"views": 82,
|
||||
"forwards": 0,
|
||||
"media_group_id": 13772563932384525,
|
||||
"images": [
|
||||
@@ -57323,7 +57323,7 @@
|
||||
"id": 4205,
|
||||
"date": "2024-07-21T19:18:02",
|
||||
"text": "...更新到 24.7.1 不仅没有修 bug 还会蓝屏。回退到已知没有 bug 的版本 23.12 了",
|
||||
"views": 89,
|
||||
"views": 90,
|
||||
"forwards": 0,
|
||||
"reply": {
|
||||
"id": 4182,
|
||||
@@ -57369,7 +57369,7 @@
|
||||
"id": 4207,
|
||||
"date": "2024-07-22T05:17:14",
|
||||
"text": "syama: 你看那个水杯旁边的镜头像不像一个水杯\n\n...它就是个水杯 🌚",
|
||||
"views": 93,
|
||||
"views": 94,
|
||||
"forwards": 0,
|
||||
"images": [
|
||||
{
|
||||
@@ -57510,7 +57510,7 @@
|
||||
"id": 4217,
|
||||
"date": "2024-07-22T20:32:45",
|
||||
"text": "syama: 明天早点叫我起床,我怕起床他们下班了\n我:所以我们现在“早点起床”是“下午五点之前“吗 <i class=\"custom-emoji\" emoji-src=\"emoji/5445342095453725432.tgs\">😴</i>",
|
||||
"views": 105,
|
||||
"views": 106,
|
||||
"forwards": 0
|
||||
},
|
||||
{
|
||||
@@ -64180,7 +64180,7 @@
|
||||
"id": 4671,
|
||||
"date": "2024-11-21T03:25:16",
|
||||
"text": "今天花了一整天调查这个数据库问题, Hibernate 全责 <i class=\"custom-emoji\" emoji-src=\"emoji/6323582802050680516.webp\">🛌</i> 以后的项目再也不用 Java EE 了\n\n我试了一下把这整个函数用 native mysql 写出来,发现这条大查询只用 1.19 秒,那为什么我的 kotlin 代码运行速度差这么大呢?\n\n开了 SQL debug 之后我发现即使只是 .findAll() 都要 N 条查询,按理来说 select * from table 只要一条查询就行啊,为什么呢?仔细看看这 N 条查询发现它把 OneToOne fk 都一个一个拉下来了。原本首先花了一条查询 SELECT * FROM parent,然后又花了 N 条查询拉 SELECT * FROM child WHERE id=i...\n\n查了一下这个问题,网上说开 Hibernate bytecode enhance 就好了,它会修改编译完的字节码让 fk 链接用到的时候再查询而不是预先把所有东西查询好。问题是它不太兼容 kotlin,绕过了三个不同的问题才成功编译,之后加上 lazy fetch 终于可以让它在用到 fk 的时候再拉数据了... \n\n但是即使这样依然要把需要拉所有 fk 数据的地方改成手动 mysql 查询,因为 orm/jpql 没办法让 findAll 把单独的查询优化成 join <i class=\"custom-emoji\" emoji-src=\"emoji/6323582802050680516.webp\">🛌</i>\n\n唉 感觉凡是透明一点的 ORM 比如 ktorm 或者 exposed 都不会有这样的问题,以后不会再用 Java EE 了",
|
||||
"views": 87,
|
||||
"views": 88,
|
||||
"forwards": 0,
|
||||
"media_group_id": 13857276129125749,
|
||||
"images": [
|
||||
@@ -64373,7 +64373,7 @@
|
||||
"id": 4682,
|
||||
"date": "2024-11-23T01:14:05",
|
||||
"text": "时隔一年半的后续:今天 Zotero 告诉我说之前遇到的这篇造假的论文被 retract 了,可喜可贺\n\n看到 Retract notice 里面指出了一个 \"Paper Mill: A business that creates and sells research papers where the buyer(s) claim authorship; the business is generally unacknowledged as a contributor.\" ...居然这个世界上还有这种业务存在,好可怕。",
|
||||
"views": 69,
|
||||
"views": 70,
|
||||
"forwards": 1,
|
||||
"reply": {
|
||||
"id": 2202,
|
||||
@@ -64396,7 +64396,7 @@
|
||||
"id": 4683,
|
||||
"date": "2024-11-24T05:52:34",
|
||||
"text": "唉 这就是 AI hype 的 nonsense 吗\n\n<a href=\"https://arxiv.org/abs/2308.09597\">ChatHaruhi</a> 这篇没写完的论文,结果评估都没有,居然就发 preprint 了,居然已经有 15 citation 了... <i class=\"custom-emoji\" emoji-src=\"emoji/6170424195260877091.webm\">🤗</i>\n\n非常可惜我也会给它贡献一个 citation",
|
||||
"views": 38,
|
||||
"views": 45,
|
||||
"forwards": 0,
|
||||
"images": [
|
||||
{
|
||||
|
||||
@@ -12,7 +12,7 @@
|
||||
<link>https://aza.moe/life</link>
|
||||
</image>
|
||||
<language>zh-cn</language>
|
||||
<lastBuildDate>Sun, 24 Nov 2024 08:10:19 +0000</lastBuildDate>
|
||||
<lastBuildDate>Sun, 24 Nov 2024 10:12:53 +0000</lastBuildDate>
|
||||
<item>
|
||||
<title>小桂桂的回忆录 📒 #4683</title>
|
||||
<link>https://aza.moe/life?post=4683</link>
|
||||
|
||||
Reference in New Issue
Block a user