-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathatom.xml
77 lines (45 loc) · 19.1 KB
/
atom.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>Good Old Days</title>
<link href="https://hencolle.com/atom.xml" rel="self"/>
<link href="https://hencolle.com/"/>
<updated>2022-01-07T14:13:38.705Z</updated>
<id>https://hencolle.com/</id>
<author>
<name>Explorare</name>
</author>
<generator uri="https://hexo.io/">Hexo</generator>
<entry>
<title>My 2021</title>
<link href="https://hencolle.com/2022/01/03/my_2021/"/>
<id>https://hencolle.com/2022/01/03/my_2021/</id>
<published>2022-01-03T02:13:46.000Z</published>
<updated>2022-01-07T14:13:38.705Z</updated>
<content type="html"><![CDATA[<p>上次写博客还是上次，一万年过去了，我终于又想起了密码，把博客支起来，打算写一篇《我的2021》。回想一下，我摸了一年，并没什么可写的，正好值此机会，通过一系列文章总结一下我的前半生。我新建这篇文章的时间是2022年1月3日 10:14，也不知道摸多久才能写完，随缘吧。这篇文章的内容也是好多篇草稿的提纲拼起来的，跨度两年，都是只有提纲，可见我摸鱼功力不凡。</p><p><escape><span id="more"></span></escape></p><h1 id="Changelog"><a href="#Changelog" class="headerlink" title="Changelog"></a>Changelog</h1><ul><li>2022-01-03 10:14 新建文档</li><li>2021-01-07 21:56 提交《回顾 2021》</li></ul><h1 id="回顾-2021"><a href="#回顾-2021" class="headerlink" title="回顾 2021"></a>回顾 2021</h1><p>2021 是我的身份从学生转变为社会待业青年的一年。</p><p>这一年，我继续在抑郁症中挣扎。每天泡在家里，硬着头皮堆论文。当然大部分时间还是在 VTuber 们的陪伴下度过的。在导师的全力相助下，我按时达到了毕业要求，顺利拿到了美术硕士学位。在这里感谢我的导师。</p><p>毕业典礼的那天，一直以来翘了所有集体活动的我按时参加了活动，打扮整齐，只为了最后见她一面，和她合一张影。典礼不出所料的长而无趣，导师因为带研二的同学去下乡写生没能参加。好不容易熬到结束，我在手机上搓了半天，把消息发了出去，找到了她。她今天也很可爱。我打算蹲下配合她的身高，她让我站起来拍，挽住了我的胳膊。我稍微着倾斜身子，姿势僵硬的被拍了两张。然后她说还要去和别人拍照，我就先回了美院，把修士服还给库房，收拾好最后剩下的一点东西，蹭了俊杰的小电驴到公交车站，打道回府。</p><p>我最终也没收到那两张照片，也无法得知我到底是什么表情。</p><p>毕业之后，我继续着摸鱼的生活，每天就是睡觉吃饭看 VTuber。在这里感谢 VTuber，是她们撑我度过了最难过的两年，让我还有机会在这里继续发牢骚。八月底，我访问了母校日语系的系主任，得知我依然还有机会出国。在联系了介绍的中介之后我发现我选择节省这部分费用，自己调查资料申请学校，目标是旧帝或者略次一级的院校，研究方向是我一直很感兴趣的机器学习。</p><p>定下目标之后我就开始了新一轮的摸鱼，先从了解机器学习入手，在 Coursera 上参加了 Andrew Ng 大佬著名的 Machine Learning 课程。在这个过程中，我迸发出了多年没再出现过的热情，从早到晚盯着电脑，只不过内容从 VTuber 和原神换成了 Andrew Ng 的课程，认真做了笔记，靠自己通过了测验和作业，拿到了毕业证书。也确实有很大收获，真正对我感兴趣的东西有了一个清晰的认识。当然我没有 pay 那个证书，所以其实也并没完全拿到。之后参加了他的 Deep Learning Specialization 系列课程，在试听期结束前完成了两个模块并拿到证书，第三个模块没能及时完成。十月初，我的突击学习就这样告一段落，返回摸鱼常态，开始搜集院校信息和招生要求，与导师邮件套磁。</p><p>不出所料，只有两封邮件有回信，其中一封回信说只收有前期研究成果的学生，另一封则说他将在 2023 年退休，不再招收新学生了，但建议我联系同院校的另一个自然语言处理方向的研究所试试。这一次终于有了一点希望，对方让我写一篇 Research Proposal 发给他，之后再考虑安排视频会议。摸了一周后，在圣诞节的凌晨，我把邮件发给了他，瞬间收到了自动回信，告知他从当日开始放假，到下个月10号才回回来。我写这篇文章正文的时候是1月7日，是的，我从那天一直摸到了现在，每天和我最爱的 VTuber 们度过。我对结果并不抱任何希望，因为我自己也认为我不配。</p><p>随缘吧。</p><h1 id="后记"><a href="#后记" class="headerlink" title="后记"></a>后记</h1><p>这篇文章的第一篇摸了四天半，用了一小时完成。写作既是对过去自己的审视与发掘，也是内心压力释放的一个渠道，（说白了就是垃圾桶），这个过程让我感受到了愉悦。在这里贴上之后系列文章的主题。</p><ul><li>工具浪费时间</li><li>想说的</li><li>没做的</li><li>未完成的目标和规划</li><li>VTuber</li><li>留学</li><li>拖延症</li><li>我最怕的是时间</li><li>今后的打算</li></ul><p>博客也是凑合支起来的，能用就行，排版、设计、性能改进都暂且搁置，有缘再说。</p><p>最后祝您身体健康，再见。</p>]]></content>
<summary type="html"><p>上次写博客还是上次，一万年过去了，我终于又想起了密码，把博客支起来，打算写一篇《我的2021》。回想一下，我摸了一年，并没什么可写的，正好值此机会，通过一系列文章总结一下我的前半生。我新建这篇文章的时间是2022年1月3日 10:14，也不知道摸多久才能写完，随缘吧。这篇文章的内容也是好多篇草稿的提纲拼起来的，跨度两年，都是只有提纲，可见我摸鱼功力不凡。</p>
<p><escape></summary>
<category term="log" scheme="https://hencolle.com/tags/log/"/>
</entry>
<entry>
<title>Windows 10 2004 update failure diagnosis (the proper way)</title>
<link href="https://hencolle.com/2020/06/15/Windows%2010%202004%20update%20failure%20diagnosis/"/>
<id>https://hencolle.com/2020/06/15/Windows%2010%202004%20update%20failure%20diagnosis/</id>
<published>2020-06-15T10:30:00.000Z</published>
<updated>2022-01-07T14:13:37.226Z</updated>
<content type="html"><![CDATA[<p>这篇文章记录了 Windows 10 升级至 2004 版本时进度长时间卡在 61% 的排查思路和解决办法。</p><p><escape><span id="more"></span></escape></p><p>While Windows 10 updating from version 1909 to 2004, the progress stuck(,hang, freeze) at 61%, which is a <a href="https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004">known issue</a> related to Conexant ISST audio drivers.</p><p>But in my case, I don’t have this driver in my system. And the Microsoft Community Forum just provides random guesses or solutions as usual, such as unplug some external devices or do a <a href="https://support.microsoft.com/en-gb/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system">system check</a>. </p><p>Finally, here is the proper way to diagnose the issue during Windows update I found: <a href="https://docs.microsoft.com/en-us/windows/deployment/upgrade/resolve-windows-10-upgrade-errors">Resolve Windows 10 upgrade errors - Windows IT Pro - Windows Deployment | Microsoft Docs</a></p><ol><li>Download SetupDiag tool from <a href="https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag">SetupDiag - Windows Deployment</a>, which is a tool to collect and analyze the logs from Windows Update.</li><li>Excute the <code>SetupDiag.exe</code>, two files will be generated in the same path, which are <code>SetupDiagResults.log</code> and <code>Logs.zip</code>.</li><li>In my case, <code>SetupDiagResults.log</code> said <em>SetupDiag was unable to match to any known failure signatures</em>, which works <em>properly</em> because the update just stuck at 61% without any error report.</li><li>According to <a href="https://docs.microsoft.com/en-us/windows/deployment/upgrade/log-files">Log files - Windows IT Pro - Windows Deployment</a>, the issue happened at Down-Level, and the log for it is setupact.log, which is collected into <code>Logs.zip</code>. And here are the last serval lines of my log:</li></ol><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br></pre></td><td class="code"><pre><span class="line">2020-06-13 19:59:05, Info MIG AddDriverFiles: Processing driver: Mobile Intel(R) Processor Family I/O PCI Express Root Port #9 - 9D18, INTEL, INTEL</span><br><span class="line">2020-06-13 19:59:05, Info MIG AddInfAndCatalog: Adding catalog file: C:\WINDOWS\system32\catroot\{f750e6c3-38ee-11d1-85e5-00c04fc295ee}\oem120.cat</span><br><span class="line">2020-06-13 19:59:05, Info MIG DumpDeviceDriversCallback: Adding file: C:\WINDOWS\system32\DRIVERS\pci.sys</span><br><span class="line">2020-06-13 19:59:05, Info MIG AddDriverFiles: Processing device: 4d36e96c-e325-11ce-bfc1-08002be10318</span><br><span class="line">2020-06-13 19:59:05, Info MIG AddDriverFiles: Processing driver: HP Dock Audio, Synaptics, Synaptics</span><br><span class="line">2020-06-13 19:59:05, Info MIG AddInfAndCatalog: Adding catalog file: C:\WINDOWS\system32\catroot\{f750e6c3-38ee-11d1-85e5-00c04fc295ee}\oem26.cat</span><br><span class="line">2020-06-13 20:00:58, Info MOUPG CInstallUI::ShowMessageBox: Showing MessageBox</span><br><span class="line">2020-06-13 20:01:00, Info MOUPG CInstallUI::ConfirmCanceled: User cancel confirmed</span><br><span class="line">2020-06-13 20:01:00, Info MOUPG CInstallUI::OnProgressChanged: Cancel is requested. Returning ERROR_REQUEST_ABORTED</span><br><span class="line">2020-06-13 20:01:00, Error MOUPG CInstallUI::OnProgressChanged(575): Result = 0x800704D3</span><br><span class="line">2020-06-13 20:01:00, Error MOUPG CSetupUIManager::OnProgressChanged(378): Result = 0x800704D3</span><br><span class="line">2020-06-13 20:01:00, Error MOUPG CSetupHost::OnProgressChanged(2306): Result = 0x800704D3</span><br><span class="line">2020-06-13 20:01:00, Error MOUPG CSetupManager::DlpManagerCallback(2063): Result = 0x800704D3</span><br><span class="line">2020-06-13 20:01:00, Info MOUPG Cancel of current task requested...</span><br><span class="line">2020-06-13 20:01:00, Info MOUPG Attempting to cancel current task...</span><br><span class="line">2020-06-13 20:01:00, Info MOUPG MoSetupPlatform: Calling SetupPlatform::INewSystem::RequestCancelOperations...</span><br><span class="line">2020-06-13 20:01:00, Info MOUPG Task cancel request returned: [0x0]</span><br><span class="line">2020-06-13 20:01:00, Error MOUPG SendCallbackMessage: [0x7] -> user callback returned 0x800704D3</span><br><span class="line">2020-06-13 20:01:00, Error MOUPG CDlpTask::Cancel(984): Result = 0xC1800108</span><br><span class="line">2020-06-13 20:01:00, Info MOUPG SendCallbackMessage: [0x7] -> Cancel request returned 0xC1800108</span><br></pre></td></tr></table></figure><p>As the log shown above, the progress hangs at 19:59:05, which is <strong>Processing driver: HP Dock Audio, Synaptics, Synaptics</strong>. I do connect a HP Thunderbolt 3 dock to my ThinkPad X1 Tablet 3rd Gen. So I disconnected it, uninstalled the device and driver for it, reboot and the update works again as I expected.</p><p>PS. I’ve tried update the system using Windows 10 2004 MSDN image, it stuck at 31% due to the same issue. The proper way to fix this is shown above.</p><p>E.O.F.</p>]]></content>
<summary type="html"><p>这篇文章记录了 Windows 10 升级至 2004 版本时进度长时间卡在 61% 的排查思路和解决办法。</p>
<p><escape></summary>
</entry>
<entry>
<title>Guide on Packaging and Import Baidu Exporter to Chrome</title>
<link href="https://hencolle.com/2016/10/16/baidu_exporter/"/>
<id>https://hencolle.com/2016/10/16/baidu_exporter/</id>
<published>2016-10-15T16:00:00.000Z</published>
<updated>2022-01-07T14:13:36.048Z</updated>
<content type="html"><![CDATA[<h1 id="TL-DR"><a href="#TL-DR" class="headerlink" title="TL;DR"></a>TL;DR</h1><p>It’s been a loooooong time since the last update. Just cause I’m too lazy. X P</p><p>Chrome removed Baidu Exporter from Chrome App Store <del>due to some unknown Python transaction</del> recently. Due to security reason Chrome will disable extensions import locally with unknown source. You will get annoying popups every time launching Chrome if unpacked extensions are loaded.</p><p>So in this thread I’ll provide a better solution to load Baidu Exporter with the latest build using Windows Group Policy. This solution inspired by <a href="https://github.com/ungrown">ungrown@Github</a>, thanks.</p><p><escape><span id="more"></span></escape></p><h1 id="Download-the-extension"><a href="#Download-the-extension" class="headerlink" title="Download the extension"></a>Download the extension</h1><p>Clone or download the latest copy of Baidu Exporter from <a href="https://github.com/acgotaku/BaiduExporter">here</a>.</p><h1 id="Package-the-extension"><a href="#Package-the-extension" class="headerlink" title="Package the extension"></a>Package the extension</h1><p>This step is unnecessary if you have the complied version.</p><ol><li><p>Launch Chrome, open <code>chrome://extensions</code>, click <code>Pack extension</code> on top-left.</p></li><li><p>Browse the code you just downloaded, click <code>Pack Extension</code>.</p></li><li><p>The newly built extension will be found in the source folder with a <code>*.pem</code> file, <strong>keep them all</strong>, you will need that <code>.pem</code> file if you want to update the extension in the furture.</p></li><li><p>Drag the <code>*.crx</code> file to the <code>chrome://extension</code> page to install it. Select the <code>Developer Mode</code> checkbox to show the hidden extension ID, save it somewhere.</p></li></ol><h1 id="Apply-Chrome-policy-using-Group-Policy-Editor"><a href="#Apply-Chrome-policy-using-Group-Policy-Editor" class="headerlink" title="Apply Chrome policy using Group Policy Editor"></a>Apply Chrome policy using Group Policy Editor</h1><p>See <a href="#last">For MacOS Users</a> if you are using <strong>MacOS</strong>.</p><ol><li><p>Download the zip file of Chrome templates from <a href="https://dl.google.com/dl/edgedl/chrome/policy/policy_templates.zip">here</a>.</p></li><li><p>Extract the following files or folders into <code>%SystemRoot%\PolicyDefinitions</code>:</p><ul><li><code>./Windows/admx/chrome.admx</code>;</li><li><code>./Windows/admx/google.admx</code>;</li><li><code>./Windows/admx/en-US/</code>;</li><li><code>./Windows/admx/zh-CN/</code>.</li></ul></li></ol><ol start="3"><li>Press <code>Win+R</code> and run: <code>gpedit.msc</code>. A sub-folder named <code>Google / Google Chrome</code> can be found under <code>Local Computer Policy > Computer Configuration > Administrative Templates</code>. (Ps. The group policy editor is not embeded with starter and home editions. Follow <a href="https://www.itechtics.com/enable-gpedit-windows-10-home/">this</a> guide to install it first. (Thanks @metafaniel for refering this issue.))</li></ol><h1 id="Add-the-extension-ID-to-whitelist"><a href="#Add-the-extension-ID-to-whitelist" class="headerlink" title="Add the extension ID to whitelist"></a>Add the extension ID to whitelist</h1><p>Add the extension ID by the following steps:</p><ol><li><p>Navigate to <code>Administrative Templates / Google / Google Chrome / Extensions</code> section.</p></li><li><p>Double click to open <code>Configure extension installation whitelist</code> on the right side.</p></li><li><p>Enable the policy and click <code>Show...</code> to add the extension ID.</p></li></ol><p>The extension will be enabled by default after Chrome relaunched.</p><p><a id="last"></a></p><h1 id="For-MacOS-Users"><a href="#For-MacOS-Users" class="headerlink" title="For MacOS Users"></a>For MacOS Users</h1><p>The solution for MacOS came from <a href="https://github.com/tofuliang">tofuliang@Github</a>, thanks.</p><ol><li>Download the following policy template.</li></ol><script src="//gist.github.com/be3dd598289252698cd37bca04abd0fe.js?file=com.google.Chrome.mobileconfig"></script><ol start="2"><li><p>Add the extension ID to line 19, delete line 20 and 21 if you don’t need it. Save.</p></li><li><p>Double click to import this policy.</p></li><li><p><strong>Reboot</strong>.</p></li></ol><hr><h1 id="References"><a href="#References" class="headerlink" title="References"></a>References</h1><ul><li><a href="https://github.com/acgotaku/BaiduExporter/issues/277#issuecomment-253988038">0.8.5在chrome商店被删 · Issue #277 · acgotaku/BaiduExporter</a></li><li><a href="https://developer.chrome.com/webstore/get_started_simple#step5">Tutorial: Getting Started - Google Chrome</a></li><li><a href="https://developer.chrome.com/extensions/packaging">Packaging - Google Chrome</a></li><li><a href="https://support.google.com/chrome/a/answer/187202?hl=en">Set Chrome policies for devices - Chrome for business and education Help</a></li></ul>]]></content>
<summary type="html"><h1 id="TL-DR"><a href="#TL-DR" class="headerlink" title="TL;DR"></a>TL;DR</h1><p>It’s been a loooooong time since the last update. Just cause I’m too lazy. X P</p>
<p>Chrome removed Baidu Exporter from Chrome App Store <del>due to some unknown Python transaction</del> recently. Due to security reason Chrome will disable extensions import locally with unknown source. You will get annoying popups every time launching Chrome if unpacked extensions are loaded.</p>
<p>So in this thread I’ll provide a better solution to load Baidu Exporter with the latest build using Windows Group Policy. This solution inspired by <a href="https://github.com/ungrown">ungrown@Github</a>, thanks.</p>
<p><escape></summary>
</entry>
</feed>