-
Notifications
You must be signed in to change notification settings - Fork 44
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
Emacs version #198
Comments
You don't need emacs 29 to use ellama. Instead of |
Show me your ellama configuration without keys (if applicable). |
I switch to setq. |
I found where is the problem. It's in this part of ellama.el I can't understand the problem, but if I comment it out all works. |
Try this one: (setq ellama-naming-provider
(make-llm-ollama
:chat-model "qwen2.5:3b"
:embedding-model "nomic-embed-text"
:default-chat-non-standard-params '(("stop" . ("\n"))))) for this to work: ollama pull qwen2.5:3b And check if it works. |
I did the change you propose but the result is same: If I can help debug give me guidance. Else I will continue by commenting this block of the code. |
try to update |
Hello,
first I need to say that I use emacs for a couple of months so forgive me if the problem is something that is expected I should know :)
I see you are using setopt. This is present in emacs 29+ does it mean that it is a must have to use ellama?
Ii ask because when I use ellama-code-review I receive this error
Debugger entered--Lisp error: (invalid-slot-type ellama-context-element-buffer name string #)
eieio--validate-slot-value(#s(eieio--class :name ellama-context-element-buffer :docstring "A structure for holding information about a contex..." :parents (#s(eieio--class :name ellama-context-element :docstring "A structu$
eieio-oset(# name #)
#f(compiled-function (obj slots) "Set slots of OBJ with SLOTS which is a list of name/value pairs.\nCalled from the constructor routine." #<bytecode -0xc921a205373af6f>)(#<ellama-context-element-buffer ellama-context-eleme$
apply(#f(compiled-function (obj slots) "Set slots of OBJ with SLOTS which is a list of name/value pairs.\nCalled from the constructor routine." #<bytecode -0xc921a205373af6f>) #<ellama-context-element-buffer ellama-context$
shared-initialize(# (:name #))
#f(compiled-function (this &optional args) "Construct the new object THIS based on ARGS.\nARGS is a property list where odd numbered elements are tags, and\neven numbered elements are the values to store in the tagged slot$
apply(#f(compiled-function (this &optional args) "Construct the new object THIS based on ARGS.\nARGS is a property list where odd numbered elements are tags, and\neven numbered elements are the values to store in the tagge$
initialize-instance(# (:name #))
#f(compiled-function (class &rest slots) "Default constructor for CLASS
eieio-default-superclass'.\nSLOTS are the initialization slots used by
initialize-instance'.\nThis static method is called when an object is constru$apply(#f(compiled-function (class &rest slots) "Default constructor for CLASS
eieio-default-superclass'.\nSLOTS are the initialization slots used by
initialize-instance'.\nThis static method is called when an object is c$make-instance(ellama-context-element-buffer :name #)
ellama-context-element-buffer(:name #)
ellama-context-add-buffer(#)
ellama-code-review()
funcall-interactively(ellama-code-review)
command-execute(ellama-code-review record)
execute-extended-command(nil "ellama-code-review" "ellama-code-re")
funcall-interactively(execute-extended-command nil "ellama-code-review" "ellama-code-re")
command-execute(execute-extended-command)
Which means that there something related to make-instance, as far as I understand.
If I am totally wrong please point me to my mistake.
The text was updated successfully, but these errors were encountered: