[log] vim changing memory contents on my laptop
strange experience today where vim's yank buffer changed to contents that were similar to what i had deleted, but different. not sure why or how this happened. the short recording showing the situation is at https://asciinema.org/a/92p5X2wyVbdw9o6mGHI4QbKNW it's hard for me to tell for certain whether vim's yank buffer was mutated in a way similar to a language model, or whether i dissociated and typed the incorrect text when intending to paste, and forgot. i had a longer recording ongoing when the issue happened. it's now on ipfs at https://dweb.link/ipfs/bafybeigtt7z4gqvq6hmvy4hucmfekw2vtuiroxvelmgrygt27y2t... . the issue is at the very end. i tried to upload this reocrding to asciinema to make it easy to jump to the end without cutting lines out of the file, but i ran into connection termination errors trying to upload it, maybe because it is so large: port 443: File "/usr/local/lib/python3.10/ssl.py", line 1237, in sendall v = self.send(byte_view[count:]) File "/usr/local/lib/python3.10/ssl.py", line 1206, in send return self._sslobj.write(data) ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:2396) port 80: File "/usr/local/lib/python3.10/urllib/request.py", line 1377, in http_open return self.do_open(http.client.HTTPConnection, req) File "/usr/local/lib/python3.10/urllib/request.py", line 1351, in do_open raise URLError(err) urllib.error.URLError: <urlopen error [Errno 32] Broken pipe>
i apologise for not verifying whether this is misleading human behavior or exotic buffer mutation. the situation surprised me and i'm somewhat confused. [thread:crazy] thread:[crazy]
the recordings have stdin enabled, so my keystrokes are visible in the json reviewing, i think the screen_mat code may be from an earlier implementation of about an hour ago. in the recording, i use the word "paste", but what i mean is "yank". maybe there is a way to have multiple yank buffers, and somehow vim was set to yank from a very old one? i just use the very basic features of vim.
i had a longer recording ongoing when the issue happened. it's now on ipfs at https://dweb.link/ipfs/bafybeigtt7z4gqvq6hmvy4hucmfekw2vtuiroxvelmgrygt27y2t... . the issue is at the very end.
Oh, hey, if somebody sees this who doesn't know me, it probably becomes quite apparent that i am both very dissociated and very psychotic etc etc. This could make it confusing to review. I'll try to stop replying to this thread. Next I would spam around the concept of trimming the log to include the relevent parts.
On 6/23/22, Undiscussed Horrific Abuse, One Victim of Many <gmkarl@gmail.com> wrote:
i had a longer recording ongoing when the issue happened. it's now on ipfs at https://dweb.link/ipfs/bafybeigtt7z4gqvq6hmvy4hucmfekw2vtuiroxvelmgrygt27y2t... . the issue is at the very end.
Oh, hey, if somebody sees this who doesn't know me, it probably becomes quite apparent that i am both very dissociated and very psychotic etc etc. This could make it confusing to review.
I'll try to stop replying to this thread. Next I would spam around the concept of trimming the log to include the relevent parts.
Here is non-spam additional information: In the recording, prior to this issue, I was working on a machine learning algorithm that used many different inaccurate optimizations. The issues with the algorithm are almost certainly simply different approximations in the underlying implementations, not memory corruption. Additionally I spend a lot of downtime waiting to figure out how to direct my arms and intentions and stuff, I'm afraid.
[the perception mistakes i make are mostly because my visual information is very low-density and my brain fills most of it in with what i expect the action mistakes i make are mostly because of mysterious spams]
participants (1)
-
Undiscussed Horrific Abuse, One Victim of Many