-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong type argument #22
Comments
Is this something that worked before and doesn't now? Are you using the latest version (0.0.14) of sayid in clojure and emacs? The emacs package is now (as of yesterday) on MELPA. If you have the right versions, running Let me know whether that's it. |
Hmmm.... tracing individual functions ( Your error may be unrelated though. |
Ok I'll trace by ns. I am using the melpa version I believe. I got this: |
ok, yeah you're using v0.0.11 or earlier of the sayid clj lib, which is not going to work with v0.0.14 of the emacs client (which you are using). You need to bump up to sayid v0.0.14 wherever you include it -- profiles.clj or project.clj I'd expect. |
I see. A little deja-vu since last time I made this kind of error. A better error message for a mismatched version would be great. Thanks for helping me with this! |
Ha, true. I actually did add the other message you requested, but didn't get to comment/closing the ticket yet. |
I might have looked at the previous error to get a hint at the issue :) |
Added an issue for the bug I noted above |
Currently try to work with sayid (still in spacemacs), but whenever I try to initiate a trace, I'm getting this error:
sayid-write-resp-val-to-buf: Wrong type argument: listp, 19
In this case I was trying to remove a trace from this function:
I get similar errors when enabling a trace or creating an inner trace. Creating an inner trace does cause the trace to appear on the sayid-traced buffer. Just enabling a trace does not making it appear in the traced buffer. In either case, the results do not appear in the sayid workspace when I run the method.
The text was updated successfully, but these errors were encountered: