Llm_tagger: Kon JSON-antwoord voor bericht 30871 niet parsen: onverwacht teken (na tags) op regel... [parse.c:706] in '{"tags":":["'

kuaza · 21 september 2025 om 16:16

Wat kan de oorzaak zijn van deze fout? Ik heb automatische tagging geconfigureerd, maar het werkt niet. Ik krijg deze fout op de foutpagina.

llm_tagger: Kon JSON-antwoord voor post 30871 niet parsen: onverwacht teken (na tags) op regel 45020, kolom 3 [parse.c:706] in '{\"tags\":\":[\"'

En

llm_tagger: kon post 30930 /t/xxxxxx-1758567315538/1502/1 niet verwerken: NoMethodError : private methode `select' aangeroepen voor een instantie van String

Volledig bericht en backtrace

Bericht

llm_tagger: Kon JSON-antwoord voor post 30871 niet parsen: onverwacht teken (na tags) op regel 45020, kolom 3 [parse.c:706] in '{\"tags\":\":[\"'

...

Backtrace

/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2.1/lib/active_support/broadcast_logger.rb:130:in `block in warn'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2.1/lib/active_support/broadcast_logger.rb:231:in `block in dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2.1/lib/active_support/broadcast_logger.rb:231:in `each'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2.1/lib/active_support/broadcast_logger.rb:231:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2.1/lib/active_support/broadcast_logger.rb:130:in `warn'
/var/www/discourse/plugins/discourse-ai/lib/automation/llm_tagger.rb:162:in `rescue in handle'
/var/www/discourse/plugins/discourse-ai/lib/automation/llm_tagger.rb:90:in `handle'
/var/www/discourse/plugins/discourse-ai/discourse_automation/llm_tagger.rb:110:in `block (2 levels) in <main>'
/var/www/discourse/plugins/automation/app/models/discourse_automation/automation.rb:158:in `block in trigger!'
/var/www/discourse/plugins/automation/app/models/discourse_automation/stat.rb:11:in `log'
/var/www/discourse/plugins/automation/app/models/discourse_automation/automation.rb:156:in `trigger!'
/var/www/discourse/plugins/automation/app/jobs/regular/discourse_automation/trigger.rb:29:in `execute'
/var/www/discourse/app/jobs/base.rb:318:in `block (2 levels) in perform'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rails_multisite-7.0.0/lib/rails_multisite/connection_management/null_instance.rb:49:in `with_connection'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rails_multisite-7.0.0/lib/rails_multisite/connection_management.rb:17:in `with_connection'
/var/www/discourse/app/jobs/base.rb:305:in `block in perform'
/var/www/discourse/app/jobs/base.rb:301:in `each'
/var/www/discourse/app/jobs/base.rb:301:in `perform'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:220:in `execute_job'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:185:in `block (4 levels) in process'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:180:in `traverse'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:183:in `block in traverse'
/var/www/discourse/lib/sidekiq/discourse_event.rb:6:in `call'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:182:in `traverse'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:183:in `block in traverse'
/var/www/discourse/lib/sidekiq/pausable.rb:131:in `call'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:182:in `traverse'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:183:in `block in traverse'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/job/interrupt_handler.rb:9:in `call'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:182:in `traverse'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:183:in `block in traverse'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/metrics/tracking.rb:26:in `track'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/metrics/tracking.rb:134:in `call'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:182:in `traverse'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:173:in `invoke'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:184:in `block (3 levels) in process'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:145:in `block (6 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/job_retry.rb:118:in `local'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:144:in `block (5 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/config.rb:39:in `block in <class:Config>'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:139:in `block (4 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:281:in `stats'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:134:in `block (3 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/job_logger.rb:15:in `call'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:133:in `block (2 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/job_retry.rb:85:in `global'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:132:in `block in dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/job_logger.rb:40:in `prepare'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:131:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:183:in `block (2 levels) in process'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:182:in `handle_interrupt'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:182:in `block in process'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:181:in `handle_interrupt'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:181:in `process'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:86:in `process_one'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:76:in `run'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/component.rb:10:in `watchdog'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/component.rb:19:in `block in safe_thread'

sam · 22 september 2025 om 00:15

welke LLM gebruik je?

Het lijkt erop dat het slecht gevormde JSON genereert en dat we extra werk moeten verrichten om dit te corrigeren.

kuaza · 22 september 2025 om 15:30

Ik heb GPT-5 Mini of 4.1 IDE niet verstrekt, omdat deze niet correct functioneerden en dezelfde foutmelding gaven.

en deze foutmelding

llm_tagger: failed to process post 30930 /t/xxxxxx-1758567315538/1502/1 : NoMethodError : private method `select' called for an instance of String

awesomerobot · 25 september 2025 om 16:55

Hoe is uw JSON-antwoord geformatteerd in de persona-instellingen? Is het:

{
"tags": "[string]",
"confidence": "integer"
}

Ik heb dit met succes gebruikt met GPT4o en Claude… maar zal er nog een paar proberen.

kuaza · 25 september 2025 om 20:02

I have made the recommended adjustments. I shall attempt it with Bird GPT-4.

awesomerobot · 25 september 2025 om 20:41

That’s close but not quite right, you need to select array first and then set the array_type as a string so it says "tags": ["string"]

kuaza · 25 september 2025 om 20:52

Ik vroeg me al af waarom het niet uitkwam zoals in het voorbeeld, maar het maakte me niet uit. Nu zal ik het ook op deze manier proberen. (Ik voel me behoorlijk dom :D)

llm_tagger: Kon JSON-antwoord voor bericht 30972 niet parsen: onverwacht teken (na confidence) op regel 2703, kolom 19 [parse.c:706] in '{\"tags\": [\"psikoloji\", \"eğitim\", \"aile\"], \"confidence\":

llm_tagger: kon bericht 30990 /t/gecici-baslik-1758843990882/17521/1 niet verwerken: NoMethodError : ongedefinieerde methode <’ voor een instantie van Array`

kuaza · 25 september 2025 om 23:52

De labels zijn een array van strings en het instellen van ‘confidence’ uitsluitend als een geheel getal heeft het probleem opgelost. Mijn excuses voor de valse alarm. <3

{
"tags": "[string]",
"confidence": "integer"
}

Lhc_fl · 26 september 2025 om 01:58

I’m a little curious if, we can use similar tools to try to fix it if a JSON syntax error is identified in the LLM response

pmusaraj · 29 september 2025 om 12:00

Dit onderwerp werd automatisch gesloten na 2 dagen. Nieuwe reacties zijn niet meer toegestaan.

Topic		Antwoorden	Weergaven
Unexpected error in Forum Researcher Bug ai , ai-bot	7	127	1 september 2025
The pages for the tags with the «.json» suffix are rendered incorrectly Bug	4	1319	15 april 2016
JSON API parsing error, single quotes used for errors like "['BAD CSRF']" Bug	3	1359	17 mei 2017
Error when translate post by ai （Job exception: undefined method `strip' for an instance of DiscourseAi::Completions::StructuredOutput Support ai , dynaloc	3	60	12 november 2025
Error on ask.discourse.com: SyntaxError: Unexpected end of JSON input Bug ask-discourse	3	78	10 juli 2025

Llm_tagger: Kon JSON-antwoord voor bericht 30871 niet parsen: onverwacht teken (na tags) op regel... [parse.c:706] in '{"tags":":["'

Gerelateerde topics