IRC channel logs
2024-01-30.log
back to list of logs
<jfred>In particular this part feels like it jives with what Spritely is going for: <jfred>> Imagine a cybersecurity program with the goal of relieving the rest of the organization from anxiety about security… cybersecurity that promotes convenience and puts in the hard work of crafting design-based mitigations. <jfred>(And the paragraph above that, but was too long to quote it here haha) <villageidiot>Actually, dthompson: I feel a bit rude asking here... but I couldn't get your Chickadee "Hello World" example running in a guix shell (see https://bpa.st/DGLDM for the error). I hope it's something I've done wrong - if not I can report it at an appropriate place. <dthompson>villageidiot: happy to talk about chickadee related things in #chickadee or #guile :) <dthompson>looks like guile is failing to write to the directory where it stores auto-compiled files though <dthompson>more of an environment issue than a chickadee one <ieugen>I saw hoot 0.3.0 release on website - but no announce on mastodon :) <ieugen>I'm going to wait a bit until I announce it <encryptedwhisper>hey folks! i was wondering if i could get a code review and figure out why my little chat app is complaining about "wrong type to apply" and not churning the vat without hitting return to refresh... <dthompson>well that would be a bug in itself... would like to understand that a bit more because we attempt to provide relevant backtraces with relevant slices of the call stack <dthompson>but in any case even a bad backtrace could be helpful along with the relevant section of code to look at <encryptedwhisper>(#<&assertion-failure> #<&origin origin: #f> #<&message message: "Wrong type to apply: ~S"> <encryptedwhisper>#<&irritants irritants: (#<unspecified>)> #<&exception-with-kind-and-args kind: wrong-type-arg <encryptedwhisper>args: (#f "Wrong type to apply: ~S" (#<unspecified>) (#<unspecified>))>)> <encryptedwhisper>(#<&assertion-failure> #<&origin origin: #f> #<&message message: "Wrong type to apply: ~S"> <encryptedwhisper>#<&irritants irritants: (#<unspecified>)> #<&exception-with-kind-and-args kind: wrong-type-arg <encryptedwhisper>args: (#f "Wrong type to apply: ~S" (#<unspecified>) (#<unspecified>))>)> <dthompson>okay so somewhere the unspecified value is operator position <encryptedwhisper>im not sure exactly what that means, though i know "wrong type to apply" often means a stray set of parens <dthompson>"wrong type to apply" means trying to call something that is not a procedure <dthompson>and the exception irritants shows that the something in question was #<unspecified> <dthompson>which is like the equivalent of undefined in javascript <dthompson>ACTION works on getting r7rs benchmarks running with hoot <encryptedwhisper>i think the best approach is to binary search for it by deleting bits of code along the execution patg <dthompson>encryptedwhisper: yeah that should help get you close to the problem