-
- Downloads
Fix 500 error when trying to resolve non-ASCII conflicts in editor
When we added caching, this meant that calling `can_be_resolved_in_ui?` didn't always call `lines`, which meant that we didn't get the benefit of the side-effect from that, where it forced the conflict data itself to UTF-8. To fix that, make this explicit by separating the `raw_content` (any encoding) from the `content` (which is either UTF-8, or an exception is raised).
Showing
- changelogs/unreleased/44564-error-500-while-attempting-to-resolve-conflicts-due-to-utf-8-conversion-error.yml 5 additions, 0 deletions...ng-to-resolve-conflicts-due-to-utf-8-conversion-error.yml
- lib/gitlab/conflict/file_collection.rb 4 additions, 1 deletionlib/gitlab/conflict/file_collection.rb
- lib/gitlab/git/conflict/file.rb 13 additions, 3 deletionslib/gitlab/git/conflict/file.rb
- lib/gitlab/git/conflict/parser.rb 0 additions, 5 deletionslib/gitlab/git/conflict/parser.rb
- lib/gitlab/gitaly_client/conflict_files_stitcher.rb 1 addition, 1 deletionlib/gitlab/gitaly_client/conflict_files_stitcher.rb
- spec/lib/gitlab/git/conflict/file_spec.rb 50 additions, 0 deletionsspec/lib/gitlab/git/conflict/file_spec.rb
- spec/lib/gitlab/git/conflict/parser_spec.rb 0 additions, 7 deletionsspec/lib/gitlab/git/conflict/parser_spec.rb
spec/lib/gitlab/git/conflict/file_spec.rb
0 → 100644
Please register or sign in to comment