wrenger / obsidian-languagetool

LanguageTool Plugin for Obsidian
GNU Affero General Public License v3.0
13 stars 1 forks source link

Error message #13

Open aarontimo opened 2 weeks ago

aarontimo commented 2 weeks ago

Hi there,

Not sure why I am getting this error message now? I haven't had any issues previously (though I'm still fairly new to LanguageTools and this Plugin)

13/11/2024, 14:24:22:
Error: 'Request to LanguageTool failed: Please check your connection and server URL.
Error: Request failed, status 413'
Settings: {"serverUrl":"https://api.languagetoolplus.com","autoCheckDelay":3000,"shouldAutoCheck":true,"languageVariety":{"en":"en-AU","de":"de-DE","pt":"pt-PT","ca":"ca-ES"},"dictionary":["...words deleted..."],"pickyMode":false,"username":"REDACTED","apikey":"REDACTED","synonyms":"en","staticLanguage":"en-AU"}

Thanks for the great plugin!

wrenger commented 1 week ago

Ok I I'll look into this. Does this error occur for all files or only sometimes? Did you change something in the settings? Maybe a config is invalid or the request is too long (file too large...).

aarontimo commented 1 week ago

Thanks, Lars. It only occurs on large files. I am working between a 10k+ words in one note and 6k words in another note. I didn’t think about file size… One note has a single graphic and the other has none, so the file size should still be very small, despite the word count.

Thanks for looking into this - and your great work on this plugin!

On 15 Nov 2024, at 3:49 AM, Lars Wrenger @.***> wrote:

Ok I I'll look into this. Does this error occur for all files or only sometimes? Did you change something in the settings? Maybe a config is invalid or the request is too long (file too large...).

— Reply to this email directly, view it on GitHub https://github.com/wrenger/obsidian-languagetool/issues/13#issuecomment-2477055544, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADCFLIRD5R4V4CNM4SCB2JL2ATPDXAVCNFSM6AAAAABRVSRRAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZXGA2TKNJUGQ. You are receiving this because you authored the thread.

wrenger commented 1 week ago

The problem is that the public LanguageTool APIs are rate limited, meaning that you can only send 20K/60K characters per request (free/premium) and 75K/300K characters per minute. So if your files are becoming big, checking the whole file in one go is not possible anymore.

It's probably a good idea for the extension to split the request into multiple chunks. Maybe I find a good way to do this. Still, if you want to check giant files, this then takes time due to these limits.

EDIT: You can already select a portion of the document and then run 'Check text'. This should still work. And also the auto-check (Settings/LanguageTool/Auto check text) only checks the currently changed test.

aarontimo commented 1 week ago

Thanks, Lars. You are definitely correct about it being a file size issue.

If splitting the file into multiple chunks could be included in a possible update in the future, that would be tremendous. Although I appreciate your time spent developing and maintaining this plugin- and the fact that it might not be technically possible.

Again, thank you for your work on this plugin.

On 16 Nov 2024, at 7:24 AM, Lars Wrenger @.***> wrote:

The problem is that the public LanguageTool APIs are rate limited, meaning that you can only send 20K/60K characters per request (free/premium) and 75K/300K characters per minute. So if your files are becoming big, checking the whole file in one go is not possible anymore.

It's probably a good idea for the extension to split the request into multiple chunks. Maybe I find a good way to do this. Still, if you want to check giant files, this then takes time due to these limits.

— Reply to this email directly, view it on GitHub https://github.com/wrenger/obsidian-languagetool/issues/13#issuecomment-2479951779, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADCFLIRMF5NXM64MGSUCB6D2AZQ7ZAVCNFSM6AAAAABRVSRRAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZZHE2TCNZXHE. You are receiving this because you authored the thread.