-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Fix exports #2584
Fix exports #2584
Conversation
Thanks for this @catalintoma 🙏🏽 |
@DidierRLopes have mercy, this is the first time I've written a line of Python code but I really like it. I am using WSL for development and did not succeed in installing the pre-commit hooks. If I understand what failed in linting I will fix manually, or request some help to install the hooks. |
I will! This is great! We are actually working on improving substantially our CONTRIBUTING guidelines to make it easier for contributors to understand the code architecture (see here), it's great that you were able to even go into the tests!! Thanks for feedback. We are looking to work on some content in video format regarding leveraging all capabilities of terminal :) Hummm, we will have the team look into this (cough @colin99d cough 😄). In this case the black linter failed, so you can do:
in order to fix it. |
@DidierRLopes I ran Black on the files reported in the failed job.
But it reported it would reformat 445 files, so that's why I did it manually for the 5 files. I will also search for a VSCode extension for Black formatter. Currently I develop on VS Code installed on Windows and a "Remote - WSL" extension that allows to develop in WSL. |
@DidierRLopes
|
That's exactly the same I do, using black manually. Well actually if the pre-commit hook is working, it does that for you. Let's see if the tests pass now. Have never seen pre-commit install returning that. @colin99d have you? |
@catalintoma, thanks for the pr! Did you setup your environment using the following steps:
|
@colin99d yes, the only difference is that I installed the full Anaconda3 and I have Debian in my WSL, so I've installed it from this guide: I did now just push formatting on 2 files that I've already formatted. The weird thing is that if I try to format using black from the terminal it does nothing. |
That is really interesting. Unfortunately, I do not have windows or linux so I cannot test this. I typically just run |
I did push another fix for an error generated by flake8 (it looks to be a static code analyzer). Can you run the pipelines again please? I think running black / flake8 (who knows what else) manually is a big waste of time, seems like having the pre-commit hook is mandatory. |
Yup all of these are just checking you code to make sure it meets some basic guidelines. |
Try running |
Now it was time for pylint to fail, I pushed a fix for that also, can we try a deploy again?
I've already tried installing 'distlib' but it returns this error I did a search for that module and I can see it in the poetry.lock file |
Hmmm. And |
Well pre-commit is already installed, it's after I run Than I can't commit and get this error in Git output There is also a pre-commit.log file created that contains this: version information
error information
` |
@DidierRLopes @colin99d I did pull from main again and it seems it's waiting approval for 2 workflows. I think they will pass because they passed last time. What is the process of pushing this to main? Do we wait for a release train? |
Sorry, I've had a very hectic day! Just approved to run tests, if it passes we can merge it to main 🙏🏽 |
No worries, it's no rush, I was just anxious to get my first fix in. I am eyeing this bug next: |
That would be great! I just updated this branch with main so we should be able to merge it after 😄 |
Congrats on becoming a contributor @catalintoma. This PR looks great! |
Thank you! |
Description
Fix Eclect.us and Finviz not allowing exports
How has this been tested?
Refactored unit tests to take into account exports