You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
grip README.md
* Serving Flask app 'grip.app'
* Debug mode: off
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
* Running on http://localhost:6419
Press CTRL+C to quit
refreshing or opening http://localhost:6419 yields the following additional lines to the terminal output:
I know very little about CSS, but it appears all my links are in black text rather than the expected blue. Looking at the "Inspect" utility in firefox it appears the color variables used by the links are not set. I suspect this is in one of the css files that returned a 404 error.
If I instead clone the repo and install via pip install -e . from the current tip of the master branch (a3f0ab5), (as I don't see a tag for 4.6.2), then the links are blue, but some other 404 errors still populate the terminal
Not sure how you are publishing to pip, but wonder if the missing tag has something to do with this. I see the same black text links if I checkout v4.6.1 (3c3f852) so guessing the current pip package doesn't have something from the recent commits that fixed this.
The text was updated successfully, but these errors were encountered:
After having a full read through your README, I tried grip --pass $GITHUB_TOKEN thinking the 404 errors were possibly this API limit, but don't see any difference.
Installed via
pip3 install grip
grip -V
returns 4.6.2Running
grip README.md
returns:|refreshing or opening http://localhost:6419 yields the following additional lines to the terminal output:
I know very little about CSS, but it appears all my links are in black text rather than the expected blue. Looking at the "Inspect" utility in firefox it appears the color variables used by the links are not set. I suspect this is in one of the css files that returned a 404 error.
If I instead clone the repo and install via
pip install -e .
from the current tip of the master branch (a3f0ab5), (as I don't see a tag for 4.6.2), then the links are blue, but some other 404 errors still populate the terminalNot sure how you are publishing to pip, but wonder if the missing tag has something to do with this. I see the same black text links if I checkout v4.6.1 (3c3f852) so guessing the current pip package doesn't have something from the recent commits that fixed this.
The text was updated successfully, but these errors were encountered: