Re: python-avro: FTBFS: AssertionError: 'reader type: null not compatible with writer type: int' not found in {'reader type: SchemaType.NULL not compatible with writer type: SchemaType.INT'}

2022-12-29 Thread Scott Talbert 

On Thu, 29 Dec 2022, Scott Kitterman wrote:


On Thursday, December 29, 2022 4:13:20 PM EST Andreas Tille wrote:

Control: tags -1 help

Hi,

I wonder whether someone might suggest a fix for


==
FAIL: test_schema_compatibility_type_mismatch
(avro.test.test_compatibility.TestCompatibility.test_schema_compatibility_t
ype_mismatch)
--
Traceback (most recent call last):
  File
"/build/python-avro-1.11.1+dfsg/.pybuild/cpython3_3.11_avro/build/avro/test
/test_compatibility.py", line 1039, in
test_schema_compatibility_type_mismatch self.assertIn(message,
result.messages)
AssertionError: 'reader type: null not compatible with writer type: int' not
found in {'reader type: SchemaType.NULL not compatible with writer type:
SchemaType.INT'}

--
Ran 421 tests in 8.358s

FAILED (failures=1, skipped=3)


Otherwise I will probably exclude Python3.11 from the build to fix this bug.


That's not an actual solution.  If you close the bug on this basis it will
hide the issue and make it appear we are more ready to move to Python 3.11 as
the default (and probably only) Python version for Bookworm.

I didn't look at the actual code.  Typically when something comes up Null is
means that something was not found.  I would look at the code where SchemaType
is determined to see how it might come up with no SchemaType.


It looks like this has already been fixed upstream (although with a 
non-obvious commit message):


https://github.com/apache/avro/commit/432f073c3cfb8ac7edb2793b797ab855c5a978dd

I just uploaded a fix.

Scott T.

Re: python-avro: FTBFS: AssertionError: 'reader type: null not compatible with writer type: int' not found in {'reader type: SchemaType.NULL not compatible with writer type: SchemaType.INT'}

2022-12-29 Thread Scott Kitterman 
On Thursday, December 29, 2022 4:13:20 PM EST Andreas Tille wrote:
> Control: tags -1 help
> 
> Hi,
> 
> I wonder whether someone might suggest a fix for
> 
> 
> ==
> FAIL: test_schema_compatibility_type_mismatch
> (avro.test.test_compatibility.TestCompatibility.test_schema_compatibility_t
> ype_mismatch)
> --
> Traceback (most recent call last):
>   File
> "/build/python-avro-1.11.1+dfsg/.pybuild/cpython3_3.11_avro/build/avro/test
> /test_compatibility.py", line 1039, in
> test_schema_compatibility_type_mismatch self.assertIn(message,
> result.messages)
> AssertionError: 'reader type: null not compatible with writer type: int' not
> found in {'reader type: SchemaType.NULL not compatible with writer type:
> SchemaType.INT'}
> 
> --
> Ran 421 tests in 8.358s
> 
> FAILED (failures=1, skipped=3)
> 
> 
> Otherwise I will probably exclude Python3.11 from the build to fix this bug.

That's not an actual solution.  If you close the bug on this basis it will 
hide the issue and make it appear we are more ready to move to Python 3.11 as 
the default (and probably only) Python version for Bookworm.

I didn't look at the actual code.  Typically when something comes up Null is 
means that something was not found.  I would look at the code where SchemaType 
is determined to see how it might come up with no SchemaType.

Scott K

signature.asc
Description: This is a digitally signed message part.

Re: python-avro: FTBFS: AssertionError: 'reader type: null not compatible with writer type: int' not found in {'reader type: SchemaType.NULL not compatible with writer type: SchemaType.INT'}

2022-12-29 Thread Andreas Tille 
Control: tags -1 help

Hi,

I wonder whether someone might suggest a fix for


==
FAIL: test_schema_compatibility_type_mismatch 
(avro.test.test_compatibility.TestCompatibility.test_schema_compatibility_type_mismatch)
--
Traceback (most recent call last):
  File 
"/build/python-avro-1.11.1+dfsg/.pybuild/cpython3_3.11_avro/build/avro/test/test_compatibility.py",
 line 1039, in test_schema_compatibility_type_mismatch
self.assertIn(message, result.messages)
AssertionError: 'reader type: null not compatible with writer type: int' not 
found in {'reader type: SchemaType.NULL not compatible with writer type: 
SchemaType.INT'}

--
Ran 421 tests in 8.358s

FAILED (failures=1, skipped=3)


Otherwise I will probably exclude Python3.11 from the build to fix this bug.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Broken symlinks in /etc/alternatives

2022-12-29 Thread Jakub Wilk 

I noticed this on my system:

$ ls /etc/alternatives/* | xargs -n1 file | grep -w broken | grep python
/etc/alternatives/bandit: broken symbolic link to /usr/bin/python3-bandit
/etc/alternatives/bandit-baseline: broken symbolic link to 
/usr/bin/python3-bandit-baseline
/etc/alternatives/bandit-config-generator: broken symbolic link to 
/usr/bin/python3-bandit-config-generator
/etc/alternatives/doc8: broken symbolic link to /usr/bin/python3-doc8
/etc/alternatives/pbr: broken symbolic link to /usr/bin/python3-pbr
/etc/alternatives/restructuredtext-lint: broken symbolic link to 
/usr/bin/python3-restructuredtext-lint
/etc/alternatives/rst-lint: broken symbolic link to 
/usr/bin/python3-rst-lint
/etc/alternatives/wsdump: broken symbolic link to /usr/bin/python3-wsdump

I guess this is fallout from Python 2 removal?

Please fix your packages.

--
Jakub Wilk