Repository navigation
test(dev): стабильная сверка бинарных данных сертификатов - #834
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Что изменено
В служебной проверке сохранности BinaryField сравнивается по байтам. PostgreSQL возвращает memoryview: default=str раньше хешировал адрес объекта, поэтому одинаковые файлы старых сертификатов давали разные хеши. Диагностика server run40320287777: ProgramCertificateAsset,6→6 записей, измененных полей нет.
API / UI / Permissions
Product runtime, C00, роли, миграции и UI не менялись. Исправлены только2 QA-скрипта и добавлен чистый unit test.
Проверки
Риски / migration
Бинарное содержимое не выводится и не меняется. Сверка всех исходных полей и ID сохранена. Production операций нет.