Clicking on any commit creates this error. I’ve changed gitlab from no timezone configured to one and after that Also tried updating postgres to have a default timezone for that database. Neither change the behavior. The error seems to be related to using a timestamp without a timezone but it was set with show timezone; This was broken before the update to 10.3 I think is the newest patch but still didn’t work after updating.
ActiveRecord::StatementInvalid (PG::UndefinedFunction: ERROR: could not identify an ordering operator for type timestamp without time zone LINE 1: …type" IN (‘LegacyDiffNote’, ‘DiffNote’) ORDER BY “notes”."c… ^ HINT: Use an explicit ordering operator or modify the query. : SELECT “notes”.* FROM “notes” WHERE “notes”.“project_id” = 7 AND “notes”.“noteable_type” = ‘Commit’ AND “notes”.“commit_id” = ‘eb872b535639a2ead2814139fbfd351d4ed9208c’ AND “notes”.“type” IN (‘LegacyDiffNote’, ‘DiffNote’) ORDER BY “notes”.“created_at” ASC, “notes”.“id” ASC): app/models/discussion.rb:25:in build_collection’ app/models/note.rb:131:indiscussions’ app/models/note.rb:147:in grouped_diff_discussions’ app/models/concerns/noteable.rb:46:ingrouped_diff_discussions’ app/controllers/projects/commit_controller.rb:134:in define_note_vars’ lib/gitlab/i18n.rb:47:inwith_locale’ lib/gitlab/i18n.rb:53:in with_user_locale’ app/controllers/application_controller.rb:324:inset_locale’ lib/gitlab/middleware/multipart.rb:93:in call’ lib/gitlab/request_profiler/middleware.rb:14:incall’ lib/gitlab/middleware/go.rb:18:in call’ lib/gitlab/etag_caching/middleware.rb:11:incall’ lib/gitlab/middleware/read_only.rb:31:in call’ lib/gitlab/request_context.rb:18:incall’ lib/gitlab/metrics/requests_rack_middleware.rb:27:in `call’