| 19 Aug 2025 |
dramforever | mixed with a whole bunch of stuff | 20:27:54 |
dramforever | maybe try clearing the cargoDepsHash (or whatever the proper name) and refetching the package? | 20:28:31 |
dramforever | there's definitely something wrong | 20:28:44 |
Gaétan Lepage | Yup, maybe upstream should try to update to 0.2.0... | 20:32:03 |
dramforever | In reply to @dramforever:matrix.org maybe try clearing the cargoDepsHash (or whatever the proper name) and refetching the package? i would guess just redoing cargoDepsHash might fix it | 20:33:32 |
dramforever | but in that case would this mean hayro-interpret 0.1.0 changed...? | 20:33:58 |
Gaétan Lepage | I tried to clean cargoDepsHash | 20:41:45 |
dramforever | nevermind actually, it says it's pinned to https://github.com/LaurenzV/hayro?rev=e701f95#e701f956 | 20:58:56 |
dramforever | not the version | 20:59:02 |
dramforever | just more reasons doing debugging on a phone is a bad idea, i keep missing stuff | 20:59:46 |
dramforever | so it's pinned to e701f956 on github, which is a broken "0.1.0" | 21:00:19 |
Gaétan Lepage | Ok too bad... Maybe let's wait for tinymist to update their lockfile then... | 21:02:06 |