<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Error on SANJAY REGMI</title>
    <link>https://sanjayregmi.com/tags/error/</link>
    <description>Recent content in Error on SANJAY REGMI</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    
    <lastBuildDate>Mon, 12 Aug 2024 15:42:39 -0700</lastBuildDate><atom:link href="https://sanjayregmi.com/tags/error/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Microsoft Outlook Error: The Operation Cannot Be Performed Because the Message Has Been Changed</title>
      <link>https://sanjayregmi.com/posts/microsoft-outlook-error-the-operation-cannot-be-performed-because-the-message-has-been-changed/</link>
      <pubDate>Mon, 12 Aug 2024 15:42:39 -0700</pubDate>
      
      <guid>https://sanjayregmi.com/posts/microsoft-outlook-error-the-operation-cannot-be-performed-because-the-message-has-been-changed/</guid>
      <description>&lt;p&gt;This message appears when editing a draft email in outlook and generally when using IMAP with/without a flaky wifi. The solution is simple:&lt;/p&gt;&#xA;&#xA;&lt;h2 class=&#34;relative group&#34;&gt;Solution&#xA;    &lt;div id=&#34;solution&#34; class=&#34;anchor&#34;&gt;&lt;/div&gt;&#xA;    &#xA;    &lt;span&#xA;        class=&#34;absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none&#34;&gt;&#xA;        &lt;a class=&#34;text-primary-300 dark:text-neutral-700 !no-underline&#34; href=&#34;#solution&#34; aria-label=&#34;Anchor&#34;&gt;#&lt;/a&gt;&#xA;    &lt;/span&gt;&#xA;    &#xA;&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Open Outlook, File -&amp;gt; Options -&amp;gt; Mail.&lt;/li&gt;&#xA;&lt;li&gt;Uncheck all options under &amp;ldquo;Conversation Clean up&amp;rdquo;.&lt;/li&gt;&#xA;&lt;li&gt;Save, quit Outlook and restart Outlook.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&#xA;&lt;h2 class=&#34;relative group&#34;&gt;Workaround&#xA;    &lt;div id=&#34;workaround&#34; class=&#34;anchor&#34;&gt;&lt;/div&gt;&#xA;    &#xA;    &lt;span&#xA;        class=&#34;absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none&#34;&gt;&#xA;        &lt;a class=&#34;text-primary-300 dark:text-neutral-700 !no-underline&#34; href=&#34;#workaround&#34; aria-label=&#34;Anchor&#34;&gt;#&lt;/a&gt;&#xA;    &lt;/span&gt;&#xA;    &#xA;&lt;/h2&gt;&#xA;&lt;p&gt;If you don&amp;rsquo;t want to or cannot spend any time tinkering as explained above, you can use the online version of Outlook at either office.com or outlook.com. Online versions are not affected by this issue.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Failed to Load Kernel &#39;Kernel&#39; FreeBSD</title>
      <link>https://sanjayregmi.com/posts/failed-to-load-kernel-kernel-freebsd/</link>
      <pubDate>Tue, 18 Jun 2024 14:35:21 -0700</pubDate>
      
      <guid>https://sanjayregmi.com/posts/failed-to-load-kernel-kernel-freebsd/</guid>
      <description>&lt;p&gt;Sometimes when you release upgrade freebsd, you might get the following error:&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;Failed to load kernel &amp;lsquo;kernel&amp;rsquo;&lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;can&amp;rsquo;t load &amp;lsquo;kernel&amp;rsquo;&lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt; can&amp;rsquo;t load &amp;lsquo;kernel&amp;rsquo;&lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt; Type &amp;lsquo;?&amp;rsquo; for a list of commands&amp;hellip; &lt;/code&gt;&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Git Error - Fatal: the Remote End Hung Up Unexpectedly</title>
      <link>https://sanjayregmi.com/posts/git-error-fatal-the-remote-end-hung-up-unexpectedly/</link>
      <pubDate>Tue, 04 Jun 2024 16:54:29 -0700</pubDate>
      
      <guid>https://sanjayregmi.com/posts/git-error-fatal-the-remote-end-hung-up-unexpectedly/</guid>
      <description>&lt;p&gt;When you push commits to git, you sometimes might get into this error. I got this when pushing hugo code into git.&lt;/p&gt;&#xA;&lt;code&gt;&#xA;git push -u origin main&#xA;Enumerating objects: 61, done.&#xA;Counting objects: 100% (61/61), done.&#xA;Delta compression using up to 4 threads&#xA;Compressing objects: 100% (45/45), done.&#xA;error: RPC failed; HTTP 400 curl 22 The requested URL returned error: 400&#xA;send-pack: unexpected disconnect while reading sideband packet&#xA;Writing objects: 100% (54/54), 2.07 MiB | 5.37 MiB/s, done.&#xA;Total 54 (delta 14), reused 0 (delta 0), pack-reused 0 (from 0)&#xA;fatal: the remote end hung up unexpectedly&#xA;&lt;/code&gt;&#xA;&lt;p&gt;This is caused by git buffer settings. Run:&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Rsync Fails When Copying Files With Tilde: rsync: [sender] fstat failed: No such file or directory</title>
      <link>https://sanjayregmi.com/posts/rysnc-fails-when-copying-files-with-tilde/</link>
      <pubDate>Wed, 21 Feb 2024 21:58:08 -0800</pubDate>
      
      <guid>https://sanjayregmi.com/posts/rysnc-fails-when-copying-files-with-tilde/</guid>
      <description>&lt;p&gt;Rsync Error:&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;send_files(71922, /source/TQR6~B)&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;rsync: [sender] fstat failed: No such file or directory (2) &lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;Trying to rsync between two different machines, I found rsync fails when it finds files that have ~ (tilde) in their filenames. I initially thought this was an issue specific to copying from a Samba Share to FreeBSD zpool. I couldn&amp;rsquo;t solve the issue entirely but figured escaping the awful tilde was a way to finish copying without rsync crashing. Here&amp;rsquo;s the command:&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2</title>
      <link>https://sanjayregmi.com/posts/how-to-resolve-zfs-unsupported-feature-com.klarasystems-vdev_zaps_v2/</link>
      <pubDate>Fri, 16 Feb 2024 21:12:43 -0800</pubDate>
      
      <guid>https://sanjayregmi.com/posts/how-to-resolve-zfs-unsupported-feature-com.klarasystems-vdev_zaps_v2/</guid>
      <description>&lt;p&gt;Note of caution:&lt;/p&gt;&#xA;&lt;blockquote&gt;&lt;p&gt;Read the FreBSD Release Notes carefully at &lt;a href=&#34;https://www.freebsd.org/releases/14.0R/relnotes/&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;https://www.freebsd.org/releases/14.0R/relnotes/&lt;/a&gt; especially the section called &amp;ldquo;Upgrading from Previous Releases of FreeBSD&amp;rdquo;.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&lt;p&gt;If you recently upgraded to FreeBSD 14 but you get the above error displayed before the beastie logo (see image below), here&amp;rsquo;s a solution for those with the boot loader in the MBR and that use the GPT partition scheme.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
