Llm_tagger：解析帖子 30871 的 JSON 响应失败：在 '{"tags":":["' 的第... 行出现意外字符（在 tags 之后）[parse.c:706]

kuaza · 2025 年9 月 21 日 16:16

此错误可能是什么原因？我已配置自动标记，但它不起作用。我在错误页面上遇到此错误。

llm_tagger: 无法解析帖子 30871 的 JSON 响应：在第 45020 行、第 3 列 [parse.c:706] 处遇到意外字符（在 tags 之后） in '{\"tags\":\":[\"'

还有

llm_tagger: 无法处理帖子 30930 /t/xxxxxx-1758567315538/1502/1 : NoMethodError : 在 String 实例上调用了私有方法 `select`

完整消息和回溯

消息

llm_tagger: 无法解析帖子 30871 的 JSON 响应：在第 45020 行、第 3 列 [parse.c:706] 处遇到意外字符（在 tags 之后） in '{\"tags\":\":[\"'

...

回溯

/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: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 · 2025 年9 月 22 日 00:15

您正在使用哪个 LLM？

看起来它正在生成格式错误的 JSON，我们需要做一些额外的工作来纠正它。

kuaza · 2025 年9 月 22 日 15:30

我没有提供 GPT-5 Mini 或 4.1 IDE，因为它们无法正常运行并显示相同的错误。

还有这个错误

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

awesomerobot · 2025 年9 月 25 日 16:55

您在个性化设置中的 JSON 响应格式是怎样的？是：

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

我已成功将此与 GPT4o 和 Claude 结合使用……但会尝试其他一些。

kuaza · 2025 年9 月 25 日 20:02

我已经进行了建议的调整。我将尝试使用 Bird GPT-4。

awesomerobot · 2025 年9 月 25 日 20:41

那差不多，但还不太对，你需要先选择数组，然后将 array_type 设置为字符串，这样就会显示 \"tags\": [\"string\"]

kuaza · 2025 年9 月 25 日 20:52

我一直在想为什么结果不像示例那样，但我并不在意。现在，我也将尝试这种方法。（我感觉自己很傻 :D）

llm_tagger: Failed to parse JSON response for post 30972: unexpected character (after confidence) at line 2703, column 19 [parse.c:706] in '{\"tags\": [\"psikoloji\", \"eğitim\", \"aile\"], \"confidence\":

llm_tagger: failed to process post 30990 /t/gecici-baslik-1758843990882/17521/1 : NoMethodError : undefined method \u003c’ for an instance of Array`

kuaza · 2025 年9 月 25 日 23:52

标签是字符串数组，将“confidence”仅设置为整数即可解决问题。抱歉虚惊一场。 <3

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

Lhc_fl · 2025 年9 月 26 日 01:58

我想知道，如果在 LLM 响应中识别出 JSON 语法错误，我们是否可以使用类似的工具来尝试修复它。

pmusaraj · 2025 年9 月 29 日 12:00

此主题在 2 天后自动关闭。不再允许回复。

话题		回复	浏览量
Unexpected error in Forum Researcher Bug ai , ai-bot	7	128	2025 年9 月 1 日
The pages for the tags with the «.json» suffix are rendered incorrectly Bug	4	1320	2016 年4 月 15 日
JSON API parsing error, single quotes used for errors like "['BAD CSRF']" Bug	3	1359	2017 年5 月 17 日
Error when translate post by ai （Job exception: undefined method `strip' for an instance of DiscourseAi::Completions::StructuredOutput Support ai , dynaloc	5	85	2025 年11 月 30 日
Error on ask.discourse.com: SyntaxError: Unexpected end of JSON input Bug ask-discourse	3	78	2025 年7 月 10 日

Llm_tagger：解析帖子 30871 的 JSON 响应失败：在 '{"tags":":["' 的第... 行出现意外字符（在 tags 之后）[parse.c:706]

相关话题