Beiträge nicht zwischen Themen verschieben können

rtyhbfdvsd · 10. Dezember 2024 um 02:24

Hallo, ich versuche, Beiträge zwischen Threads zu verschieben und erhalte immer wieder diese Fehlermeldung. Dieser Fehler verhindert, dass Beiträge in der gesamten Installation verschoben werden können. Wenn jemand Vorschläge hat, wäre ich äußerst vorsichtig. Danke fürs Lesen!

PG::UniqueViolation (FEHLER:  doppelte Schlüsselwert verletzt eindeutige Einschränkung „post_timings_unique“
DETAIL:  Schlüssel (topic_id, post_number, user_id)=(4175, 6, 1074) existiert bereits.
)
lib/mini_sql_multisite_connection.rb:109:in `run'
app/models/post_mover.rb:507:in `move_post_timings'
app/models/post_mover.rb:138:in `handle_moved_references'
app/models/post_mover.rb:108:in `move_posts_to'
app/models/post_mover.rb:35:in `block in to_topic'
app/models/post_mover.rb:35:in `to_topic'
app/models/topic.rb:1308:in `move_posts'
app/controllers/topics_controller.rb:1415:in `move_posts_to_destination'
app/controllers/topics_controller.rb:917:in `move_posts'
app/controllers/application_controller.rb:424:in `block in with_resolved_locale'
app/controllers/application_controller.rb:424:in `with_resolved_locale'
lib/middleware/omniauth_bypass_middleware.rb:64:in `call'
lib/content_security_policy/middleware.rb:12:in `call'
lib/middleware/anonymous_cache.rb:403:in `call'
lib/middleware/csp_script_nonce_injector.rb:12:in `call'
config/initializers/008-rack-cors.rb:14:in `call'
config/initializers/100-quiet_logger.rb:20:in `call'
config/initializers/100-silence_logger.rb:29:in `call'
lib/middleware/enforce_hostname.rb:24:in `call'
lib/middleware/processing_request.rb:12:in `call'
lib/middleware/request_tracker.rb:360:in `call'

Backtrace

rack-mini-profiler (3.3.1) lib/patches/db/pg.rb:113:in `exec'
rack-mini-profiler (3.3.1) lib/patches/db/pg.rb:113:in `async_exec'
mini_sql (1.6.0) lib/mini_sql/postgres/connection.rb:217:in `run'
mini_sql (1.6.0) lib/mini_sql/active_record_postgres/connection.rb:38:in `block in run'
mini_sql (1.6.0) lib/mini_sql/active_record_postgres/connection.rb:34:in `block in with_lock'
activesupport (7.2.2) lib/active_support/concurrency/null_lock.rb:9:in `synchronize'
mini_sql (1.6.0) lib/mini_sql/active_record_postgres/connection.rb:34:in `with_lock'
mini_sql (1.6.0) lib/mini_sql/active_record_postgres/connection.rb:38:in `run'
lib/mini_sql_multisite_connection.rb:109:in `run'
mini_sql (1.6.0) lib/mini_sql/postgres/connection.rb:196:in `exec'
app/models/post_mover.rb:507:in `move_post_timings'
app/models/post_mover.rb:138:in `handle_moved_references'
app/models/post_mover.rb:108:in `move_posts_to'
app/models/post_mover.rb:35:in `block in to_topic'
activerecord (7.2.2) lib/active_record/connection_adapters/abstract/transaction.rb:616:in `block in within_new_transaction'
activesupport (7.2.2) lib/active_support/concurrency/null_lock.rb:9:in `synchronize'
activerecord (7.2.2) lib/active_record/connection_adapters/abstract/transaction.rb:613:in `within_new_transaction'
activerecord (7.2.2) lib/active_record/connection_adapters/abstract/database_statements.rb:361:in `transaction'
activerecord (7.2.2) lib/active_record/transactions.rb:234:in `block in transaction'
activerecord (7.2.2) lib/active_record/connection_adapters/abstract/connection_pool.rb:421:in `with_connection'
activerecord (7.2.2) lib/active_record/connection_handling.rb:296:in `with_connection'
activerecord (7.2.2) lib/active_record/transactions.rb:233:in `transaction'
app/models/post_mover.rb:35:in `to_topic'
app/models/topic.rb:1308:in `move_posts'
app/controllers/topics_controller.rb:1415:in `move_posts_to_destination'
app/controllers/topics_controller.rb:917:in `move_posts'
actionpack (7.2.2) lib/action_controller/metal/basic_implicit_render.rb:8:in `send_action'
actionpack (7.2.2) lib/abstract_controller/base.rb:226:in `process_action'
actionpack (7.2.2) lib/action_controller/metal/rendering.rb:193:in `process_action'
actionpack (7.2.2) lib/abstract_controller/callbacks.rb:261:in `block in process_action'
activesupport (7.2.2) lib/active_support/callbacks.rb:121:in `block in run_callbacks'
app/controllers/application_controller.rb:424:in `block in with_resolved_locale'
i18n (1.14.6) lib/i18n.rb:353:in `with_locale'
app/controllers/application_controller.rb:424:in `with_resolved_locale'
activesupport (7.2.2) lib/active_support/callbacks.rb:130:in `block in run_callbacks'
activesupport (7.2.2) lib/active_support/callbacks.rb:141:in `run_callbacks'
actionpack (7.2.2) lib/abstract_controller/callbacks.rb:260:in `process_action'
actionpack (7.2.2) lib/action_controller/metal/rescue.rb:27:in `process_action'
actionpack (7.2.2) lib/action_controller/metal/instrumentation.rb:77:in `block in process_action'
activesupport (7.2.2) lib/active_support/notifications.rb:210:in `block in instrument'
activesupport (7.2.2) lib/active_support/notifications/instrumenter.rb:58:in `instrument'
activesupport (7.2.2) lib/active_support/notifications.rb:210:in `instrument'
actionpack (7.2.2) lib/action_controller/metal/instrumentation.rb:76:in `process_action'
actionpack (7.2.2) lib/action_controller/metal/params_wrapper.rb:259:in `process_action'
activerecord (7.2.2) lib/active_record/railties/controller_runtime.rb:39:in `process_action'
actionpack (7.2.2) lib/abstract_controller/base.rb:163:in `process'
actionview (7.2.2) lib/action_view/rendering.rb:40:in `process'
rack-mini-profiler (3.3.1) lib/mini_profiler/profiling_methods.rb:115:in `block in profile_method'
actionpack (7.2.2) lib/action_controller/metal.rb:252:in `dispatch'
actionpack (7.2.2) lib/action_controller/metal.rb:335:in `dispatch'
actionpack (7.2.2) lib/action_dispatch/routing/route_set.rb:67:in `dispatch'
actionpack (7.2.2) lib/action_dispatch/routing/route_set.rb:50:in `serve'
actionpack (7.2.2) lib/action_dispatch/journey/router.rb:53:in `block in serve'
actionpack (7.2.2) lib/action_dispatch/journey/router.rb:133:in `block in find_routes'
actionpack (7.2.2) lib/action_dispatch/journey/router.rb:126:in `each'
actionpack (7.2.2) lib/action_dispatch/journey/router.rb:126:in `find_routes'
actionpack (7.2.2) lib/action_dispatch/journey/router.rb:34:in `serve'
actionpack (7.2.2) lib/action_dispatch/routing/route_set.rb:896:in `call'
lib/middleware/omniauth_bypass_middleware.rb:64:in `call'
rack (2.2.10) lib/rack/tempfile_reaper.rb:15:in `call'
rack (2.2.10) lib/rack/conditional_get.rb:40:in `call'
rack (2.2.10) lib/rack/head.rb:12:in `call'
actionpack (7.2.2) lib/action_dispatch/http/permissions_policy.rb:38:in `call'
lib/content_security_policy/middleware.rb:12:in `call'
lib/middleware/anonymous_cache.rb:403:in `call'
lib/middleware/csp_script_nonce_injector.rb:12:in `call'
config/initializers/008-rack-cors.rb:14:in `call'
rack (2.2.10) lib/rack/session/abstract/id.rb:266:in `context'
rack (2.2.10) lib/rack/session/abstract/id.rb:260:in `call'
actionpack (7.2.2) lib/action_dispatch/middleware/cookies.rb:704:in `call'
actionpack (7.2.2) lib/action_dispatch/middleware/callbacks.rb:31:in `block in call'
activesupport (7.2.2) lib/active_support/callbacks.rb:101:in `run_callbacks'
actionpack (7.2.2) lib/action_dispatch/middleware/callbacks.rb:30:in `call'
actionpack (7.2.2) lib/action_dispatch/middleware/debug_exceptions.rb:31:in `call'
actionpack (7.2.2) lib/action_dispatch/middleware/show_exceptions.rb:32:in `call'
logster (2.20.0) lib/logster/middleware/reporter.rb:40:in `call'
railties (7.2.2) lib/rails/rack/logger.rb:41:in `call_app'
railties (7.2.2) lib/rails/rack/logger.rb:29:in `call'
config/initializers/100-quiet_logger.rb:20:in `call'
config/initializers/100-silence_logger.rb:29:in `call'
actionpack (7.2.2) lib/action_dispatch/middleware/request_id.rb:33:in `call'
lib/middleware/enforce_hostname.rb:24:in `call'
rack (2.2.10) lib/rack/method_override.rb:24:in `call'
actionpack (7.2.2) lib/action_dispatch/middleware/executor.rb:16:in `call'
rack (2.2.10) lib/rack/sendfile.rb:110:in `call'
rack-mini-profiler (3.3.1) lib/mini_profiler.rb:334:in `call'
lib/middleware/processing_request.rb:12:in `call'
message_bus (4.3.8) lib/message_bus/rack/middleware.rb:60:in `call'
lib/middleware/request_tracker.rb:360:in `call'
actionpack (7.2.2) lib/action_dispatch/middleware/remote_ip.rb:96:in `call'
railties (7.2.2) lib/rails/engine.rb:535:in `call'
railties (7.2.2) lib/rails/railtie.rb:226:in `public_send'
railties (7.2.2) lib/rails/railtie.rb:226:in `method_missing'
rack (2.2.10) lib/rack/urlmap.rb:74:in `block in call'
rack (2.2.10) lib/rack/urlmap.rb:58:in `each'
rack (2.2.10) lib/rack/urlmap.rb:58:in `call'
unicorn (6.1.0) lib/unicorn/http_server.rb:634:in `process_client'
unicorn (6.1.0) lib/unicorn/http_server.rb:739:in `worker_loop'
unicorn (6.1.0) lib/unicorn/http_server.rb:547:in `spawn_missing_workers'
unicorn (6.1.0) lib/unicorn/http_server.rb:143:in `start'
unicorn (6.1.0) bin/unicorn:128:in `<top (required)>'
vendor/bundle/ruby/3.3.0/bin/unicorn:25:in `load'
vendor/bundle/ruby/3.3.0/bin/unicorn:25:in `<main>'

Env

HTTP HOSTS: forums.insertcredit.com

nat · 10. Dezember 2024 um 09:30

Hey, tolle Neuigkeiten, wir haben eine Korrektur, die gerade gemerged wurde:

github.com/discourse/discourse

FIX: When moving posts between topics, ensure only relevant timings are moved

main ← pento/fix-moving-posts-to-topic-chronologically

opened 03:01AM - 09 Dec 24 UTC

pento

+45 -1

## ✨ What's This? When moving posts to an existing topic whilst preserving ch…ronological ordering, the second chunk of posts moved can trigger a PostgreSQL error: ``` PG::UniqueViolation (ERROR: duplicate key value violates unique constraint "post_timings_unique" DETAIL: Key (topic_id, post_number, user_id)=(36, 29, 1) already exists. ) lib/mini_sql_multisite_connection.rb:109:in `run' app/models/post_mover.rb:432:in `copy_shifted_post_timings_from_temp' app/models/post_mover.rb:118:in `handle_moved_references' app/models/post_mover.rb:94:in `move_posts_to' app/models/post_mover.rb:28:in `block in to_topic' app/models/post_mover.rb:28:in `to_topic' ``` The cause of this error is a little bit silly. After a post has been moved from a different topic, a moderator post is inserted into the old topic, pointing to where the post has been moved to. This moderator post is ultimately created using `PostCreator`, which by default, records a 5000ms Post Timing for that newly created post. Because of how Post Timings are tracked, this timing will be inserted into the `post_timings` table with the same `topic_id`, `post_number`, and `user_id` as the moved post used to have before it was moved. Now, when we proceed to moving the next post, `PostMover.move_post_timings` will look for post timings to move based on whether there's a corresponding entry in the `moved_posts` table. This is where our problem lays: the post that we previously moved has an entry in the `moved_posts` table, but now there's an unexpected entry in `post_timings` that we know doesn't belong to the previously moved post, but it has matching `topic_id`, `post_number`, and `user_id` of the what that moved post used to have, anyway. To fix this, we can enforce only matching post IDs that are being moved in this run of `PostMover`. Internal ref t/142010/5 ## 👑 Testing The simplest way to reproduce this error is: - Create a destination topic. - Create the first source topic, and add a reply to it. - Create a second source topic, and add a reply to it. - Move the reply in the second source topic to the destination topic, remembering to check the “preserve chronological order” option. - Move the reply in the first source topic to the destination, again checking the “preserve chronological order” option.

Ich bin mir nicht sicher, ob du deine Seite gerade upgraden kannst, aber das sollte dir helfen, diesen Fehler zu beheben.

rtyhbfdvsd · 10. Dezember 2024 um 14:30

Danke!

j.jaffeux · 13. Dezember 2024 um 14:30

Dieses Thema wurde 3 Tage nach der letzten Antwort automatisch geschlossen. Neue Antworten sind nicht mehr zulässig.

Thema		Antworten	Aufrufe
"There was an error moving posts" Bug	3	78	12. Dezember 2024
Moving shipments causes an error Bug	5	90	19. Dezember 2024
Unable to move posts due to 500 error Support	9	444	18. Oktober 2025
Rake posts:reorder_posts gives `UniqueViolation` error Bug fixed	5	368	10. März 2025
Moving a post fails in unknown circumstances Bug	8	1298	10. Februar 2018

Beiträge nicht zwischen Themen verschieben können

Verwandte Themen