Codecov Report

Merging #371 (1f0f517) into main (7c91c7b) will decrease coverage by 3.00%.
The diff coverage is 40.00%.

@@            Coverage Diff             @@
##             main     #371      +/-   ##
==========================================
- Coverage   86.53%   83.52%   -3.01%     
==========================================
  Files         134      136       +2     
  Lines        6704     6726      +22     
==========================================
- Hits         5801     5618     -183     
- Misses        903     1108     +205     

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

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@alaeddine-13 please take care of this PR thanks, we have to move forward. It doesn't make sense to be blocked by paddle because of the lack of maintenance on their side. Please refactor the tests, or in the worst case, remove paddle tests (or even functions). Move this PR forward at any cost.

Ref: https://jinaai.slack.com/archives/C02AC4T8Y5T/p1661117495528849

we're proceeding like so:

1. create another protoc gen image with new version
2. build protos in 2 versions (old and new)
3. in docarray and jina, dynamically find the version of protobuf and accordingly, use the appropriate protobuf file

could you also change __version__ = 0.16.0 so

after this merge,

1. the corresponding PR in core has to be merged, with version restriction of docarray >=0.16.0 and its own __version=3.18.0
2. docarray release 0.16.0
3. jina release 3.8.0

I agree on this
old jina versions will no more be compatible with new docarray and installing old versions of jina becomes buggy
the dependency here should be fixed to use docarray~=0.16.0: https://github.com/jina-ai/jina/blob/master/extra-requirements.txt#L35

i haven't looked at the protobuf docs generation, is it affected?