jaimeferj commented on PR #2565:
URL: https://github.com/apache/iceberg-python/pull/2565#issuecomment-3431330448

   Sorry for pushing again, I though that the linting error was fixed by 
https://github.com/apache/iceberg-python/pull/2654 but it still errors:
   ```
   ❯ make lint
   python -m poetry run prek run -a
   trim trailing 
whitespace.................................................Passed
   fix end of 
files.........................................................Passed
   debug statements 
(python)................................................Passed
   check 
yaml...............................................................Passed
   check python 
ast.........................................................Passed
   ruff (legacy 
alias)......................................................Passed
   ruff 
format..............................................................Passed
   
mypy.....................................................................Failed
   - hook id: mypy
   - exit code: 1
     tests/utils/test_manifest.py:51: error: "Callable[[FileIO, str], 
tuple[ManifestFile, ...]]" has no attribute "cache_clear"  [attr-defined]
     Found 1 error in 1 file (checked 166 source files)
   
markdownlint.............................................................Passed
   
pydocstyle...............................................................Passed
   
flynt....................................................................Passed
   
codespell................................................................Passed
   make: *** [Makefile:87: lint] Error 1
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to