Loading old messages failed on first connect
When I just installed ement, ran M-x ement-connect, joined Ement.el room, and tried to load older messages with S-<SPACE>, the messages where not loaded. Instead, I got an error:
error in process sentinel: Ement API error: "Loading earlier
messages failed", #s(plz-error nil #s(plz-response 2 400 ((date .
"Wed, 13 Apr 2022 15:44:44 GMT") (content-type .
"application/json") (synapse-trace-id . "...") (cache-control .
"no-cache, no-store, must-revalidate")
(access-control-allow-origin . "*") (access-control-allow-methods
. "GET, HEAD, POST, PUT, DELETE, OPTIONS")
(access-control-allow-headers . "X-Requested-With, Content-Type,
Authorization, Date") (permissions-policy . "interest-cohort=()")
(cf-cache-status . "DYNAMIC") (expect-ct . "max-age=604800,
report-uri=\"https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct\"")
(server . "cloudflare") (cf-ray . "...-IAD"))
"{\"errcode\":\"M_UNKNOWN\",\"error\":\"'from' parameter is
invalid\"}") nil)
Running M-x ement-disconnect + M-x ement-connect solved the problem for now.
Also, M-x ement-disconnect threw another error:
error in process sentinel: Ement API error: "Ement: Unrecognized network error", #s(plz-error nil nil "curl process killed")
Thanks. Somehow the "from" token must not be getting received or saved when a room is joined, but it comes in with a full sync.
@yantar92 I hate to ask, "Does this still happen?" but I'm afraid I have to, because AFAIK I've never had this problem myself.
Adam Porter @.***> writes:
@yantar92 I hate to ask, "Does this still happen?" but I'm afraid I have to, because AFAIK I've never had this problem myself.
It only happened the first time I loaded ement. I now tried using with-emacs.sh, and I can no longer reproduce.
-- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Thanks.