Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

912.bugfix allow checksum to be None on ConsumerRecord #912

Merged
merged 1 commit into from
Aug 5, 2023

Conversation

zschumacher
Copy link
Contributor

Changes

When using serialization frameworks like pydantic, I can not attach a consumer record because checksum can be None. Since it is marked as deprecated, it seems reasonable to mark it as optional here.

Checklist

  • I think the code is well written
  • Unit tests for the changes exist
  • Documentation reflects the changes
  • Add a new news fragment into the CHANGES folder
    • name it <issue_id>.<type> (e.g. 588.bugfix)
    • if you don't have an issue_id change it to the pr id after creating the PR
    • ensure type is one of the following:
      • .feature: Signifying a new feature.
      • .bugfix: Signifying a bug fix.
      • .doc: Signifying a documentation improvement.
      • .removal: Signifying a deprecation or removal of public API.
      • .misc: A ticket has been closed, but it is not of interest to users.
    • Make sure to use full sentences with correct case and punctuation, for example: Fix issue with non-ascii contents in doctest text files.

When using serialization frameworks like pydantic, I can not attach a consumer record because checksum can be None.  Since it is marked as deprecated, it seems reasonable to mark it as optional here.
@zschumacher zschumacher changed the title Make checksum optional 912.bugfix allow checksum to be None on ConsumerRecord Aug 1, 2023
@zschumacher
Copy link
Contributor Author

Add a new news fragment into the CHANGES folder

Not really sure what this means - do I need to create a CHANGES folder?

@codecov
Copy link

codecov bot commented Aug 5, 2023

Codecov Report

Merging #912 (8a28c44) into master (772aa75) will not change coverage.
Report is 1 commits behind head on master.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #912   +/-   ##
=======================================
  Coverage   97.56%   97.56%           
=======================================
  Files          30       30           
  Lines        5451     5451           
=======================================
  Hits         5318     5318           
  Misses        133      133           
Flag Coverage Δ
cext 88.40% <100.00%> (ø)
integration 97.52% <100.00%> (ø)
purepy 97.10% <100.00%> (+0.03%) ⬆️
unit 38.10% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed Coverage Δ
aiokafka/structs.py 100.00% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@ods ods merged commit abd39be into aio-libs:master Aug 5, 2023
25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants