Hifzaan
Hifzaan
@AkashKumar7902 Sir is this approach correct? i changed my approach based on your feedback. Difference Between Approaches: Previous attempt: Used os.Exit(1) during validation, which terminated the entire process when Docker...
> @HifzaanDev please attach a screen recording while testing with the app mentioned in the issue description The description now contains before and afters along with screen-recording
added logic inside validate function!
test run after merge and removal of old function, completed under 25 seconds.
> hey @HifzaanDev > > looks like the changes have slowed down sanitize > > with your changes > > ``` > ❯ time keploy sanitize > > ▓██▓▄ >...
> using flask-secret > > used this for first capture > > ``` > for i in {1..100}; do curl -s http://localhost:8000/secret1; curl -s http://localhost:8000/secret2; curl -s http://localhost:8000/secret3; done >...
> > note: i deleted the secret files after testing each build so they dont spoil the sanitize > > command i used: > > please create seperate keploy directory...
yes sure , this is the one-click installation build below: it takes the same time as the test i did on the main branch build ``` hifdev@LAPTOP-OU0MUVRB:/mnt/c/Keploy_local/samples-python/flask-secret$ cp -r keploy-original...
same cant find the streaks