Before starting, check the git history to determine if this is a follow-up review:
git log --oneline -10 | grep -i "Co-Authored-By: Claude"| git checkout --orphan newBranch; \ | |
| git add -A; \ # Add all files and commit them | |
| git commit -m "Cleanup"; \ | |
| git branch -D main; \ # Delete the main branch | |
| git branch -m main; \ # Rename the current branch to main | |
| git push -f origin main; \ # Force push main branch to GitHub | |
| git gc --aggressive --prune=all # Remove the old files |
| curl -s -H 'X-aws-ec2-metadata-token: $(curl -s -X PUT http://169.254.169.254/latest/api/token -H "X-aws-ec2-metadata-token-ttl-seconds: 21600")' http://169.254.169.254/latest/meta-data/ |
I'm using zsh on a mac.
Always update the docs/COMPLETE.md document with what you did, and add any appropriate followup ideas to docs/TODO.md
Store any useful knowledge that you might want to refer to later that are specific to this repository in docs/KNOWLEDGE.md
Store top level knowledge about the design in docs/DESIGN.md as you go along
Store a working PRD in docs/PRD.md as you go along.
This xmlsec github issue on fixing pip install xmlsec was really annoying to parse through. I pumped the contents into ChatGPT, which got me most of the way, and then I had to follow one of the other comments to get it working. I am documenting it here in case it helps someone else or if I need to reference it in the future.
brew uninstall libxmlsec1| """ | |
| This script merges all files in a specified repository directory into a single text file. | |
| It includes features for filtering, excluding specific directories, and splitting the output | |
| into smaller files. By default, it excludes test-related directories unless specified otherwise. | |
| ### Man page | |
| usage: merge_files.py [-h] [-o OUTPUT] [--split SPLIT] [--filter-extensions FILTER_EXTENSIONS] [--no-exclude-tests] repo_path | |
| Merge all files in a repository into a single text file. |
This is an interesting exercise in how ZAP handles Swagger files on import. My primary concern is that ZAP does not support importing injectable URL parameters from a Swagger file, and interprets a path like {id} as a literal id string.
You can see the difference between the endpoints that NightVision discovers (on the left) and the spidered URLs from ZAP (on the right): https://www.diffchecker.com/JKaeR6rg/ (expires in 30 days).
If you clone this gist, you can run python3 print_endpoints.py to print the endpoints that are in swagger-paths.csv (the ones discovered by NightVision).
And you can see the endpoints that are discovered by the ZAP Spider in spidered-paths.csv.
| { | |
| "agent": { | |
| "metrics_collection_interval": 60 | |
| }, | |
| "logs": { | |
| "logs_collected": { | |
| "files": { | |
| "collect_list": [ | |
| { | |
| "file_path": "/home/ec2-user/shared-volume/zap.log", |
| # .github/workflows/app.yaml | |
| name: My Python Project | |
| on: push | |
| jobs: | |
| test: | |
| runs-on: ubuntu-latest | |
| timeout-minutes: 10 | |
| services: |