2025/01/13

Newest at the top

2025-01-13 19:30:45 +0100alecs(~alecs@61.pool85-58-154.dynamic.orange.es) alecs
2025-01-13 19:30:20 +0100housemate(~housemate@146.70.66.228) (Max SendQ exceeded)
2025-01-13 19:29:39 +0100peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 252 seconds)
2025-01-13 19:27:54 +0100housemate(~housemate@146.70.66.228) housemate
2025-01-13 19:25:33 +0100 <r-sta> ok, at least now it hits the <<loop>> and loads in all the data
2025-01-13 19:24:39 +0100 <r-sta> cant*!
2025-01-13 19:24:37 +0100 <r-sta> can*
2025-01-13 19:24:34 +0100 <r-sta> i ant deal with nodeterministic errors!
2025-01-13 19:24:31 +0100housemate(~housemate@146.70.66.228) (Ping timeout: 252 seconds)
2025-01-13 19:24:24 +0100 <r-sta> there are some blas i hope it doesnt mess up in the ghci prompt
2025-01-13 19:24:13 +0100 <r-sta> it mentions hmatrix
2025-01-13 19:24:10 +0100 <r-sta> the repl seems to be messing something up
2025-01-13 19:24:03 +0100 <r-sta> it wasnt doing that before. im going back to cabal v2-run
2025-01-13 19:23:51 +0100 <r-sta>  * 0x8ec1afd9f0 0x7ff687e1a1a0
2025-01-13 19:23:51 +0100 <r-sta>    Frame Code address
2025-01-13 19:23:50 +0100 <r-sta>  Attempting to reconstruct a stack trace...
2025-01-13 19:23:49 +0100 <r-sta> Access violation in generated code when executing data at 0x7ff687e1a1a0
2025-01-13 19:23:38 +0100 <r-sta> now if i dont do any profiling, it even still gives a new different error!
2025-01-13 19:20:19 +0100ljdarj(~Thunderbi@user/ljdarj) ljdarj
2025-01-13 19:19:38 +0100tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net) tzh
2025-01-13 19:14:12 +0100peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich
2025-01-13 19:13:11 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2025-01-13 19:13:09 +0100target_i(~target_i@user/target-i/x-6023099) target_i
2025-01-13 19:09:33 +0100 <r-sta> i want to step through line by line
2025-01-13 19:09:27 +0100 <r-sta> i just need to find this loop!
2025-01-13 19:08:48 +0100 <r-sta> the code version of free climbing el chapo
2025-01-13 19:08:35 +0100 <r-sta> !!!!
2025-01-13 19:08:31 +0100 <EvanR> that you have
2025-01-13 19:08:28 +0100 <EvanR> to find out what you changed, look at the version control system
2025-01-13 19:07:55 +0100 <r-sta> still idk why it breaks now or what i changed, or why the thing that finds the bugs introduces new bugs or anything
2025-01-13 19:07:23 +0100housemate(~housemate@146.70.66.228) housemate
2025-01-13 19:07:16 +0100 <r-sta> so the last propper run checks almost all the components
2025-01-13 19:07:03 +0100 <r-sta> no i mean, i didnt break most of it
2025-01-13 19:06:50 +0100 <r-sta> oh
2025-01-13 19:06:39 +0100 <EvanR> that you can run
2025-01-13 19:06:26 +0100 <EvanR> it's where you have a set of tests which sanity check subsections of the code
2025-01-13 19:06:17 +0100 <r-sta> problem atm is its throwing some other unknown error for some unknown reason before it even hits the loop, simply by virtue of enabling -fbreak-on-exception, which i think is lame
2025-01-13 19:05:30 +0100Smiles(uid551636@id-551636.lymington.irccloud.com) (Quit: Connection closed for inactivity)
2025-01-13 19:05:30 +0100 <r-sta> EvanR: any details on this test suite, idk what it is, but if it could be a path to finding the <<loop>> id be overjoyed
2025-01-13 19:04:52 +0100 <r-sta> (and obviously even after deleting plenty, it still throws a non-deterministic error when trying to load in the data)
2025-01-13 19:04:44 +0100gehmehgehgmg
2025-01-13 19:04:25 +0100sprotte24(~sprotte24@p200300d16f245c002d65884199a66258.dip0.t-ipconnect.de)
2025-01-13 19:04:23 +0100 <r-sta> testsuite!?
2025-01-13 19:01:59 +0100ash3en(~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Quit: ash3en)
2025-01-13 18:59:20 +0100gehmehgeh(~user@user/gehmehgeh) gehmehgeh
2025-01-13 18:56:12 +0100gmg(~user@user/gehmehgeh) (Remote host closed the connection)
2025-01-13 18:51:30 +0100 <EvanR> I am grateful that <<loop>> exists, it could be much worse
2025-01-13 18:50:53 +0100 <EvanR> that you have
2025-01-13 18:50:48 +0100 <EvanR> run the test suite
2025-01-13 18:48:44 +0100 <r-sta> this piece of code is huge! iv no idea what changed