-
Notifications
You must be signed in to change notification settings - Fork 80
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
Host Fuzz Introspector locally in cloud experiments #176
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: David Korczynski <david@adalogics.com>
Signed-off-by: David Korczynski <david@adalogics.com>
Adds ability to set Fuzz Introspector endpoint to point to a local deployment. Signed-off-by: David Korczynski <david@adalogics.com>
Signed-off-by: David Korczynski <david@adalogics.com>
JOB: https://pantheon.corp.google.com/kubernetes/job/us-central1-c/llm-experiment/default/ofg-pr-176-dg |
# Create (small) DB. | ||
(cd /fi/tools/web-fuzzing-introspection/app/static/assets/db/ && \ | ||
find "/experiment/benchmark-sets/$BENCHMARK_SET" -type f -name "*.yaml" \ | ||
-exec basename {} .yaml \; | sort > must_include_small.config && \ | ||
./launch_minor_oss_fuzz.sh) | ||
|
||
/fi/tools/web-fuzzing-introspection/.venv/bin/deactivate | ||
|
||
touch /FI_DB_READY |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@DavidKorczynski What would be the best way to check if local FI is ready to use?
I am using this file as a naive way to mark the completion of DB creation so that another process knows when to resume.
If there is a better way, I would love to learn.
Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, the easiest may be to ping it after running main.py
? The following shows connection refused while loading to providing the html when the app is live.
(.venv) dav@ubuntu-main:/tmp$ wget http://localhost:8080/
--2024-03-23 14:05:04-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... failed: Connection refused.
(.venv) dav@ubuntu-main:/tmp$ wget http://localhost:8080/
--2024-03-23 14:05:05-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... failed: Connection refused.
(.venv) dav@ubuntu-main:/tmp$ wget http://localhost:8080/
--2024-03-23 14:05:06-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... failed: Connection refused.
(.venv) dav@ubuntu-main:/tmp$ wget http://localhost:8080/
--2024-03-23 14:05:07-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... 200 OK
Length: 75079 (73K) [text/html]
Saving to: ‘index.html’
index.html 100%[===============================================================================================================================================================================================================================>] 73.32K --.-KB/s in 0s
2024-03-23 14:05:07 (428 MB/s) - ‘index.html’ saved [75079/75079]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I will try this.
Now: Replicates #145 to run PR experiments.
Later: Complete the TODOs to host FI locally in full experiments, which often have
timeout
error that are likely caused by too frequent access to publicintrospector.oss-fuzz.com
.This PR is ready except these TODOs:
run_all_experiments.py
to use local FI after merging Use introspector to retrieve context. #144.ContextRetriever
so that it can call_set_introspector_endpoints
with it to use local FI.