lorniu / go-translate

Translator on Emacs. Supports multiple engines such as Google, Bing, deepL, ChatGPT, StarDict, Youdao and so on.
GNU General Public License v3.0
274 stars 37 forks source link

Error when using gts-google-rpc-engine #40

Closed jumper047 closed 1 year ago

jumper047 commented 1 year ago

Seems like something changed on google's side. I set up go translate like that:

 (setq gts-default-translator
      (gts-translator
       :picker (gts-prompt-picker)
       :engines (gts-google-rpc-engine)
       :render (gts-posframe-pop-render)))

Debugger output:

Debugger entered--Lisp error: (error "Error occurred when request with token (gts-google-rpc-engine, \"FdrFJe\":\"\\([^\"]*\\)\")")
  signal(error ("Error occurred when request with token (gts-google-rpc-engine, \"FdrFJe\":\"\\([^\"]*\\)\")"))
  error("Error occurred when request with token (%s, %s)" gts-google-rpc-engine "\"FdrFJe\":\"\\([^\"]*\\)\"")
  #f(compiled-function () #<bytecode 0x1a4591322e488b70>)()
  #f(compiled-function () #<bytecode 0x75db26c29414d04>)()
  #f(compiled-function (status) #<bytecode -0x6ac1f0e2b53f6c5>)((:peer (:certificates ((:version 3 :serial-number "60:e4:64:67:a0:cf:71:5d:0a:9d:5a:ef:7f:83:42:5a" :issuer "C=US,O=Google Trust Services LLC,CN=GTS CA 1C3" :valid-from "2022-09-12" :valid-to "2022-12-05" :subject "CN=*.google.cn" :public-key-algorithm "EC/ECDSA" :certificate-security-level "High" :signature-algorithm "RSA-SHA256" :public-key-id "sha1:70:b0:53:a3:73:b7:29:0d:03:d5:36:3f:a4:74:ae:..." :certificate-id "sha1:23:eb:ce:6f:00:b5:88:3d:44:7d:8b:97:5f:9d:24:..." :pem "-----BEGIN CERTIFICATE-----\nMIIEizCCA3OgAwIBAgIQYO...") (:version 3 :serial-number "02:03:bc:53:59:6b:34:c7:18:f5:01:50:66" :issuer "C=US,O=Google Trust Services LLC,CN=GTS Root R1" :valid-from "2020-08-13" :valid-to "2027-09-30" :subject "C=US,O=Google Trust Services LLC,CN=GTS CA 1C3" :public-key-algorithm "RSA" :certificate-security-level "Medium" :signature-algorithm "RSA-SHA256" :public-key-id "sha1:34:69:bb:fa:7c:26:15:12:8d:8d:9b:d6:1e:b3:14:..." :certificate-id "sha1:1e:7e:f6:47:cb:a1:50:28:1c:60:89:72:57:10:28:..." :pem "-----BEGIN CERTIFICATE-----\nMIIFljCCA36gAwIBAgINAg...") (:version 3 :serial-number "77:bd:0d:6c:db:36:f9:1a:ea:21:0f:c4:f0:58:d3:0d" :issuer "C=BE,O=GlobalSign nv-sa,OU=Root CA,CN=GlobalSign R..." :valid-from "2020-06-19" :valid-to "2028-01-28" :subject "C=US,O=Google Trust Services LLC,CN=GTS Root R1" :public-key-algorithm "RSA" :certificate-security-level "High" :signature-algorithm "RSA-SHA256" :public-key-id "sha1:85:56:53:49:be:ea:4a:b1:86:49:b5:61:71:a9:95:..." :certificate-id "sha1:08:74:54:87:e8:91:c1:9e:30:78:c1:f2:a0:7e:45:..." :pem "-----BEGIN CERTIFICATE-----\nMIIFYjCCBEqgAwIBAgIQd7...")) :certificate (:version 3 :serial-number "60:e4:64:67:a0:cf:71:5d:0a:9d:5a:ef:7f:83:42:5a" :issuer "C=US,O=Google Trust Services LLC,CN=GTS CA 1C3" :valid-from "2022-09-12" :valid-to "2022-12-05" :subject "CN=*.google.cn" :public-key-algorithm "EC/ECDSA" :certificate-security-level "High" :signature-algorithm "RSA-SHA256" :public-key-id "sha1:70:b0:53:a3:73:b7:29:0d:03:d5:36:3f:a4:74:ae:..." :certificate-id "sha1:23:eb:ce:6f:00:b5:88:3d:44:7d:8b:97:5f:9d:24:..." :pem "-----BEGIN CERTIFICATE-----\nMIIEizCCA3OgAwIBAgIQYO...") :key-exchange "ECDHE-RSA" :protocol "TLS1.3" :cipher "AES-256-GCM" :mac "AEAD" :encrypt-then-mac nil)))
  url-http-activate-callback()
  url-http-chunked-encoding-after-change-function@54989-backport(1849 1854 5)
  apply(url-http-chunked-encoding-after-change-function@54989-backport (1849 1854 5))
  url-http-chunked-encoding-after-change-function(1849 1854 5)
  url-http-generic-filter(#<process translate.google.cn> "0\15\n\15\n")
jumper047 commented 1 year ago

Just found a reason - it trying to connect to translate.google.cn, which seems hardcoded. Changing url to .com solves this issue, but I suppose it is still worth it to make this url easy customizeable

lorniu commented 1 year ago

Have a try plz. The default url is .com now. You can config it using (setq gts-google-rpc-base-url "...").

jumper047 commented 1 year ago

Yep, now it works. BTW, thank you for awesome package!