Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://arusahni.net/blog/rss.xml

  1. <?xml version="1.0" encoding="utf-8"?>
  2. <?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Entropy</title><link>http://arusahni.net/</link><description>Aru Sahni's personal blog.</description><atom:link href="http://arusahni.net/blog/rss.xml" type="application/rss+xml" rel="self"></atom:link><language>en</language><lastBuildDate>Sat, 07 Jun 2025 13:53:51 GMT</lastBuildDate><generator>https://getnikola.com/</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Persisting a Default Kernel with systemd-boot</title><link>http://arusahni.net/blog/2025/05/systemd-boot-default-kernel.html</link><dc:creator>Aru Sahni</dc:creator><description>&lt;div&gt;&lt;p&gt;I use &lt;a href="https://wiki.archlinux.org/title/Systemd-boot"&gt;systemd-boot&lt;/a&gt; instead of
  3. Grub. It's pretty barebones, which I like. It simply presents a boot menu and
  4. then gets out of the way. Like other boot managers, it allows you to set the
  5. default boot entry. I just need to set the &lt;code&gt;default=&lt;/code&gt; key in
  6. &lt;code&gt;/efi/loader/loader.conf&lt;/code&gt; to reference one of the &lt;code&gt;.conf&lt;/code&gt; files in
  7. &lt;code&gt;/efi/loader/entries/&lt;/code&gt; (e.g.,
  8. &lt;code&gt;00000000000000000000000000000000-6.14.6-arch1-1.conf&lt;/code&gt;). This setup works well.
  9. However, in a rolling-release distro like Arch, where kernel packages are
  10. frequently updated, there's an issue to address.&lt;/p&gt;
  11. &lt;p&gt;Arch provides two kernel packages: &lt;code&gt;linux&lt;/code&gt;, which tracks the latest stable
  12. kernel, and &lt;code&gt;linux-lts&lt;/code&gt;, which tracks the latest LTS kernel version. Having the
  13. LTS kernel installed simultaneously gives me a handy fallback if a new mainline
  14. kernel makes it so I can't boot. The problem arises when updating &lt;code&gt;linux&lt;/code&gt; or
  15. &lt;code&gt;linux-lts&lt;/code&gt; packages. The &lt;code&gt;.conf&lt;/code&gt; filenames change, invalidating the &lt;code&gt;default=&lt;/code&gt;
  16. value. Ideally, I could make the default entry track either the mainline or LTS
  17. kernels regardless of explicit version.&lt;/p&gt;
  18. &lt;p&gt;Well, I can! The &lt;code&gt;default=&lt;/code&gt; field accepts patterns. So, instead of
  19. &lt;code&gt;00000000000000000000000000000000-6.14.6-arch1-1.conf&lt;/code&gt;, you can use
  20. &lt;code&gt;00000000000000000000000000000000-*-arch?-?.conf&lt;/code&gt; and, boom, you're always on
  21. the latest stable version.&lt;/p&gt;
  22. &lt;p&gt;You may be wondering what the field &lt;code&gt;00000000000000000000000000000000&lt;/code&gt;
  23. represents - that's your &lt;a href="https://www.freedesktop.org/software/systemd/man/latest/machine-id.html"&gt;machine
  24. ID&lt;/a&gt;.
  25. It's a 32-character hexadecimal ID. You can see yours via &lt;code&gt;cat
  26. /etc/machine-id&lt;/code&gt;.&lt;/p&gt;&lt;/div&gt;</description><category>linux</category><guid>http://arusahni.net/blog/2025/05/systemd-boot-default-kernel.html</guid><pubDate>Sat, 07 Jun 2025 02:02:40 GMT</pubDate></item><item><title>Installing a Release Candidate Kernel in Arch Linux</title><link>http://arusahni.net/blog/2024/12/arch-rc-kernel.html</link><dc:creator>Aru Sahni</dc:creator><description>&lt;div&gt;&lt;p&gt;I recently received a shiny new Thinkpad for my shiny new job. I had the option
  27. to select what I wanted from Lenovo (or Apple, but I dislike MacOS) and chose a
  28. machine that wouldn't have the same issues &lt;a href="http://arusahni.net/blog/2024/04/arch-crash-recovery-chroot.html"&gt;my other workstation
  29. had&lt;/a&gt;. I made it a point to avoid Intel
  30. chipsets (due to webcam issues) and stayed far away from discrete Nvidia
  31. graphics. I settled on a nice AMD Ryzen-based system. It had a very new
  32. Qualcomm radio, but I saw people online saying that Wi-Fi and Bluetooth worked
  33. fine. I took the plunge and selected that as my workstation.&lt;/p&gt;
  34. &lt;p&gt;It arrived, I popped in my live USB, and a few hours later, I had a fully
  35. provisioned Arch Linux system. Wi-Fi worked fine, and I was able to scan for
  36. Bluetooth devices. Success! Or was it?&lt;/p&gt;
  37. &lt;p&gt;The next morning, I sat down at my desk, clocked in, and grabbed my Bluetooth
  38. headphones to listen to some morning tunes. I initiated pairing from the
  39. headphones, selected them from my laptop's device list, and... nothing. It
  40. timed out. I tried again, and again, and again, messing with timeouts and using
  41. &lt;code&gt;bluetoothctl&lt;/code&gt; to manually negotiate things, but no luck.&lt;/p&gt;
  42. &lt;p&gt;&lt;a href="http://arusahni.net/blog/2024/12/arch-rc-kernel.html"&gt;Read more…&lt;/a&gt; (3 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>linux</category><guid>http://arusahni.net/blog/2024/12/arch-rc-kernel.html</guid><pubDate>Fri, 20 Dec 2024 01:33:03 GMT</pubDate></item><item><title>Repairing a Botched Arch Linux Kernel Upgrade</title><link>http://arusahni.net/blog/2024/04/arch-crash-recovery-chroot.html</link><dc:creator>Aru Sahni</dc:creator><description>&lt;div&gt;&lt;p&gt;I made the jump to Arch Linux on my personal and work computers a few years
  43. ago. Ubuntu was a dependable experience, but a combination of issues with the
  44. Debian way of life (slow progress) and Canonical's stewardship of the project
  45. (e.g., Snaps) convinced me it was time to try another distribution.&lt;/p&gt;
  46. &lt;p&gt;It's been a great experience. Pacman is a wonderful package manager, and AUR is
  47. everything I wanted PPAs to be. I get the latest versions of packages
  48. (including the Linux kernel) shortly after they're released. Of course, that
  49. isn't &lt;em&gt;always&lt;/em&gt; a good thing, but rolling back to an older version is
  50. straightforward.&lt;/p&gt;
  51. &lt;p&gt;I recently stubbed my toe in a way that's unique to Arch - my computer crashed
  52. while I was in the middle of upgrading my kernel. What's great is I was able to
  53. recover with only an hour or so of downtime. What happened?&lt;/p&gt;
  54. &lt;p&gt;&lt;a href="http://arusahni.net/blog/2024/04/arch-crash-recovery-chroot.html"&gt;Read more…&lt;/a&gt; (5 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>linux</category><guid>http://arusahni.net/blog/2024/04/arch-crash-recovery-chroot.html</guid><pubDate>Sun, 07 Apr 2024 02:00:00 GMT</pubDate></item><item><title>Migrating my Neovim Config to Lua</title><link>http://arusahni.net/blog/2022/10/neovim-lua-config.html</link><dc:creator>Aru Sahni</dc:creator><description>&lt;div&gt;&lt;p&gt;I've been a happy &lt;a href="https://neovim.io"&gt;Neovim&lt;/a&gt; user for the past several years.
  55. The pace of development, quality of the product, and energy of the community
  56. have made it enjoyable to use. Recently, the project has introduced
  57. &lt;a href="https://en.wikipedia.org/wiki/Lua_(programming_language)"&gt;Lua&lt;/a&gt; as a first-class
  58. citizen in the editor. In places where you may otherwise be forced to wrangle
  59. the mess that is VimL (aka Vimscript), you can instead use a saner, faster
  60. scripting language.&lt;/p&gt;
  61. &lt;p&gt;I initially refrained from making the jump over to Lua as I held the ideal of
  62. being able to return to Vim whenever I wanted. With the release of Vim version
  63. 8, which doubled down on VimL, I realized my folly. Vim wasn't going to
  64. suddenly adopt the good parts of Neovim, nor was that community going to
  65. change overnight. With that, I sat down one Saturday to get to porting. After a
  66. few weeks of on-and-off experimentation (and exploring both /r/neovim and
  67. GitHub to see how other people did things) , I landed on a stable, Lua-first
  68. config that's been humming along for several weeks now.&lt;/p&gt;
  69. &lt;p&gt;Let's dive in!&lt;/p&gt;
  70. &lt;p&gt;&lt;a href="http://arusahni.net/blog/2022/10/neovim-lua-config.html"&gt;Read more…&lt;/a&gt; (6 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>vim</category><guid>http://arusahni.net/blog/2022/10/neovim-lua-config.html</guid><pubDate>Sun, 20 Nov 2022 23:04:45 GMT</pubDate></item><item><title>How Git Checkout's Previous Branch Shortcut Works Under the Hood</title><link>http://arusahni.net/blog/2021/04/git-revisions.html</link><dc:creator>Aru Sahni</dc:creator><description>&lt;div&gt;&lt;p&gt;One piece of Git shorthand I use all the time is &lt;code&gt;git checkout -&lt;/code&gt;. Much like
  71. &lt;code&gt;cd -&lt;/code&gt;, it references the previous item in your history. In the case of &lt;code&gt;cd&lt;/code&gt;,
  72. it will change your current directory to the previous one you were in. So,&lt;/p&gt;
  73. &lt;pre class="code literal-block"&gt;&lt;span class="nv"&gt;$ &lt;/span&gt;&lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="nv"&gt;$PWD&lt;/span&gt;
  74. /home/aru
  75. &lt;span class="nv"&gt;$ &lt;/span&gt;&lt;span class="nb"&gt;cd &lt;/span&gt;code/git-req
  76. &lt;span class="nv"&gt;$ &lt;/span&gt;&lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="nv"&gt;$PWD&lt;/span&gt;
  77. /home/aru/code/git-req
  78. &lt;span class="nv"&gt;$ &lt;/span&gt;&lt;span class="nb"&gt;cd&lt;/span&gt; -
  79. ~
  80. &lt;span class="nv"&gt;$ &lt;/span&gt;&lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="nv"&gt;$PWD&lt;/span&gt;
  81. /home/aru
  82. &lt;/pre&gt;
  83.  
  84.  
  85. &lt;p&gt;Git has its own version of this:&lt;/p&gt;
  86. &lt;pre class="code literal-block"&gt;&lt;span class="nv"&gt;$ &lt;/span&gt;git branch --show-current
  87. master
  88. &lt;span class="nv"&gt;$ &lt;/span&gt;git checkout my-new-feature
  89. Switched to branch &lt;span class="s1"&gt;'my-new-feature'&lt;/span&gt;
  90. Your branch is up to date with &lt;span class="s1"&gt;'origin/my-new-feature'&lt;/span&gt;.
  91. &lt;span class="nv"&gt;$ &lt;/span&gt;git checkout -
  92. Switched to branch &lt;span class="s1"&gt;'master'&lt;/span&gt;
  93. Your branch is up to date with &lt;span class="s1"&gt;'origin/master'&lt;/span&gt;.
  94. &lt;/pre&gt;
  95.  
  96.  
  97. &lt;p&gt;Handy! But how does it work? I poked through the files in &lt;code&gt;.git&lt;/code&gt; (and even
  98. watched the filesystem for changes, but nothing jumped out).&lt;/p&gt;
  99. &lt;p&gt;&lt;a href="http://arusahni.net/blog/2021/04/git-revisions.html"&gt;Read more…&lt;/a&gt; (3 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>tech</category><guid>http://arusahni.net/blog/2021/04/git-revisions.html</guid><pubDate>Mon, 26 Apr 2021 22:02:51 GMT</pubDate></item><item><title>Elixir Development with Vim</title><link>http://arusahni.net/blog/2020/08/elixir-vim.html</link><dc:creator>Aru Sahni</dc:creator><description>&lt;div&gt;&lt;p&gt;I love Vim (more specifically, &lt;a href="http://neovim.org"&gt;the NeoVim fork&lt;/a&gt;). Modal
  100. editing as part of my
  101. &lt;a href="https://sanctum.geek.nz/arabesque/unix-as-ide-introduction/"&gt;Unix IDE&lt;/a&gt; brings
  102. an immense amount of productivity and enjoyment to my day-to-day development
  103. activities. As such, whenever I take up a new language or framework, I enjoy
  104. experimenting with how best to integrate it into my existing workflow.&lt;/p&gt;
  105. &lt;p&gt;Having started programming in Elixir, I've started the customization journey
  106. for the language.  Much as with Maslow's Hierarchy of Needs, there's a
  107. hierarchy of editor support required for an fulfilling programming experience.
  108. Let's get there with Elixir!&lt;/p&gt;
  109. &lt;p&gt;&lt;a href="http://arusahni.net/blog/2020/08/elixir-vim.html"&gt;Read more…&lt;/a&gt; (3 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>elixir</category><category>tech</category><category>vim</category><guid>http://arusahni.net/blog/2020/08/elixir-vim.html</guid><pubDate>Tue, 25 Aug 2020 17:41:20 GMT</pubDate></item><item><title>Kicking the Tires with Elixir, Part 1 - Pipes</title><link>http://arusahni.net/blog/2020/08/elxir-intro-01.html</link><dc:creator>Aru Sahni</dc:creator><description>&lt;div&gt;&lt;p&gt;Lately I've been playing with Elixir, a functional language that sits over
  110. &lt;a href="https://www.erlang.org/"&gt;Erlang&lt;/a&gt; and
  111. &lt;a href="https://learnyousomeerlang.com/what-is-otp"&gt;the OTP framework&lt;/a&gt;. It's exciting
  112. because it handles embarrassingly scalable problems with aplomb, enabling a
  113. high level of parallelism and concurrency with a great developer experience.
  114. While I think Rust shines at the system programming level, Elixir seems like a
  115. perfect candidate for web services - balancing power with ergonomics.&lt;/p&gt;
  116. &lt;p&gt;There are plenty of well-written posts about the language and its associated
  117. libraries. I wanted to touch on what stood out to me as a Pythonista, web
  118. developer, and nerd. I don't know how many posts will comprise the series, but
  119. I have at least a few topics in mind.&lt;/p&gt;
  120. &lt;p&gt;First up: pipes.&lt;/p&gt;
  121. &lt;p&gt;&lt;a href="http://arusahni.net/blog/2020/08/elxir-intro-01.html"&gt;Read more…&lt;/a&gt; (2 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>elixir</category><category>tech</category><guid>http://arusahni.net/blog/2020/08/elxir-intro-01.html</guid><pubDate>Wed, 12 Aug 2020 21:41:11 GMT</pubDate></item><item><title>Migrating from Gmail to Fastmail</title><link>http://arusahni.net/blog/2020/08/gmail-to-fastmail.html</link><dc:creator>Aru Sahni</dc:creator><description>&lt;div&gt;&lt;p&gt;In 2004, Google launched Gmail. This service changed everything. You didn't
  122. have to worry about running over your few megabytes of quota - your storage
  123. space was "unlimited" (with a ticker and everything)! Deletion was a thing of
  124. the past, you now archive! Folders were so ninety-ninety-late, there
  125. were labels! I got an invite within the first two weeks of it launching, and it
  126. was good.&lt;/p&gt;
  127. &lt;p&gt;A decade or so later, Google launched Inbox, which brought innovations like
  128. bundles, snoozing, highlights, pinning, sweeping, and smart filtering to the
  129. deluge of email that flooded your account each day. I switched from Gmail to
  130. Inbox, and it was better.&lt;/p&gt;
  131. &lt;p&gt;Then, in true Google fashion, it was sacrificed at the altar of project
  132. mismanagement (or whatever the lack of product strategy is called). And it
  133. was bad.&lt;/p&gt;
  134. &lt;p&gt;Since being forced back to Gmail, I've constantly lamented the death of a
  135. service that made dealing with email less painful for me. Gmail is not only
  136. without new innovation, but it's also slow; It regularly fails to load new
  137. messages, or seemingly loses track of what it should be showing, necessitating
  138. a hard refresh. Sure, Google has thrown a few bones at it, like smart replies,
  139. but I respond to so few emails that spending a few seconds to formulate a
  140. response has never been an issue.&lt;/p&gt;
  141. &lt;p&gt;Given these concerns, I realized that the "stickiness" of Gmail was gone.
  142. I have the means to pay for service, and nothing is keeping me on Gmail
  143. (other than the fact that everyone's been using my Gmail address for 16 years).
  144. Leaving Gmail sounded doable, and I owned a personal domain on that I'd love to
  145. use for email. The only question was: where do I go for hosting?&lt;/p&gt;
  146. &lt;p&gt;&lt;a href="http://arusahni.net/blog/2020/08/gmail-to-fastmail.html"&gt;Read more…&lt;/a&gt; (4 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>tech</category><guid>http://arusahni.net/blog/2020/08/gmail-to-fastmail.html</guid><pubDate>Sun, 02 Aug 2020 21:47:35 GMT</pubDate></item><item><title>Optimizing Rust Binary Size</title><link>http://arusahni.net/blog/2020/03/optimizing-rust-binary-size.html</link><dc:creator>Aru Sahni</dc:creator><description>&lt;div&gt;&lt;p&gt;I develop and maintain a git extension called
  147. &lt;a href="https://arusahni.github.io/git-req/"&gt;git-req&lt;/a&gt;. It enables developers to check
  148. out pull requests from GitHub and GitLab by their number instead of branch
  149. name. It initially started out as a bash script that invoked Python for harder
  150. tasks (e.g., JSON parsing). It worked well enough, but I wanted to add
  151. functionality that would have been painful to implement in bash.  Additionally,
  152. one of my goals was to make it as portable as possible, and requiring a Python
  153. distribution be available flew against that. That meant that I needed to
  154. distribute this as a binary instead of a script, so I set about finding a
  155. programming language to use. After surveying what was available, and
  156. determining what would be the best addition to my toolbox, &lt;a href="https://www.rust-lang.org/"&gt;I selected
  157. Rust&lt;/a&gt;.&lt;/p&gt;
  158. &lt;p&gt;The programming language has a steep learning curve, but has been fun to learn
  159. and immerse myself within.  The community is great, and I'm excited to find
  160. more opportunities to use Rust in the future.&lt;/p&gt;
  161. &lt;p&gt;The rewrite took a while to accomplish, but when all was said and done,
  162. everything worked, and worked well.  I was able to implement some snazzy new
  163. features as well as polish some rough edges. However, for how "simple" I felt
  164. the underlying program to be, it clocked in at 13 megabytes. That felt like a
  165. lot.  So, I decided to see what could be done.&lt;/p&gt;
  166. &lt;p&gt;&lt;a href="http://arusahni.net/blog/2020/03/optimizing-rust-binary-size.html"&gt;Read more…&lt;/a&gt; (5 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>code</category><category>rust</category><guid>http://arusahni.net/blog/2020/03/optimizing-rust-binary-size.html</guid><pubDate>Tue, 31 Mar 2020 00:00:05 GMT</pubDate></item><item><title>Elasticsearch Frustration: The Curious Query</title><link>http://arusahni.net/blog/2017/04/elasticsearch-frustration.html</link><dc:creator>Aru Sahni</dc:creator><description>&lt;div&gt;&lt;p&gt;Last year I was poking at an Elasticsearch cluster to review the indexed data
  167. and verify that things were healthy. It was all good until I stumbled upon this
  168. weird document:&lt;/p&gt;
  169. &lt;pre class="code javascript"&gt;&lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-1"&gt;&lt;/a&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  170. &lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-2"&gt;&lt;/a&gt;  &lt;span class="s2"&gt;"_version"&lt;/span&gt;&lt;span class="o"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  171. &lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-3"&gt;&lt;/a&gt;  &lt;span class="s2"&gt;"_index"&lt;/span&gt;&lt;span class="o"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"events"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  172. &lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-4"&gt;&lt;/a&gt;  &lt;span class="s2"&gt;"_type"&lt;/span&gt;&lt;span class="o"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"event"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  173. &lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-5"&gt;&lt;/a&gt;  &lt;span class="s2"&gt;"_id"&lt;/span&gt;&lt;span class="o"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"_query"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  174. &lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-6"&gt;&lt;/a&gt;  &lt;span class="s2"&gt;"_score"&lt;/span&gt;&lt;span class="o"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  175. &lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-7"&gt;&lt;/a&gt;  &lt;span class="s2"&gt;"_source"&lt;/span&gt;&lt;span class="o"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  176. &lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-8"&gt;&lt;/a&gt;    &lt;span class="s2"&gt;"query"&lt;/span&gt;&lt;span class="o"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  177. &lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-9"&gt;&lt;/a&gt;      &lt;span class="s2"&gt;"bool"&lt;/span&gt;&lt;span class="o"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  178. &lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-10"&gt;&lt;/a&gt;        &lt;span class="s2"&gt;"must"&lt;/span&gt;&lt;span class="o"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
  179. &lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-11"&gt;&lt;/a&gt;          &lt;span class="p"&gt;{&lt;/span&gt;
  180. &lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-12"&gt;&lt;/a&gt;            &lt;span class="s2"&gt;"range"&lt;/span&gt;&lt;span class="o"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  181. &lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-13"&gt;&lt;/a&gt;              &lt;span class="s2"&gt;"date_created"&lt;/span&gt;&lt;span class="o"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  182. &lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-14"&gt;&lt;/a&gt;                &lt;span class="s2"&gt;"gte"&lt;/span&gt;&lt;span class="o"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2016-01-01"&lt;/span&gt;
  183. &lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-15"&gt;&lt;/a&gt;              &lt;span class="p"&gt;}&lt;/span&gt;
  184. &lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-16"&gt;&lt;/a&gt;            &lt;span class="p"&gt;}&lt;/span&gt;
  185. &lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-17"&gt;&lt;/a&gt;          &lt;span class="p"&gt;}&lt;/span&gt;
  186. &lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-18"&gt;&lt;/a&gt;        &lt;span class="p"&gt;]&lt;/span&gt;
  187. &lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-19"&gt;&lt;/a&gt;      &lt;span class="p"&gt;}&lt;/span&gt;
  188. &lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-20"&gt;&lt;/a&gt;    &lt;span class="p"&gt;}&lt;/span&gt;
  189. &lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-21"&gt;&lt;/a&gt;  &lt;span class="p"&gt;}&lt;/span&gt;
  190. &lt;a name="rest_code_3814aff0c34b44b7b018cbf67463a7b7-22"&gt;&lt;/a&gt;&lt;span class="p"&gt;}&lt;/span&gt;
  191. &lt;/pre&gt;&lt;p&gt;It may not be immediately obvious what's going on in the above snippet.
  192. Instead of a valid &lt;code&gt;event&lt;/code&gt; document, there's a document with a query as
  193. the contents. Additionally, the document ID appears to be &lt;code&gt;_query&lt;/code&gt;
  194. instead of the expected GUID. The combination of these two irregularities makes
  195. it seem as if someone accidentally posted a query to the wrong endpoint. No
  196. problem, just delete the document, right?&lt;/p&gt;
  197. &lt;pre class="code text"&gt;&lt;a name="rest_code_234788fd6e054f2fbde1a47c78d4131c-1"&gt;&lt;/a&gt;DELETE /events/event/_query
  198. &lt;a name="rest_code_234788fd6e054f2fbde1a47c78d4131c-2"&gt;&lt;/a&gt;ActionRequestValidationException[Validation Failed: 1: source is missing;]
  199. &lt;/pre&gt;&lt;p&gt;Wat.&lt;/p&gt;
  200. &lt;p&gt;&lt;a href="http://arusahni.net/blog/2017/04/elasticsearch-frustration.html"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>elasticsearch</category><category>tech</category><guid>http://arusahni.net/blog/2017/04/elasticsearch-frustration.html</guid><pubDate>Sun, 23 Apr 2017 20:23:28 GMT</pubDate></item></channel></rss>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//arusahni.net/blog/rss.xml

Home · About · News · Docs · Terms

 
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda