chris
05/23/2024, 7:07 PMnpx promptfoo cache clear via the CLI, however is there a way to do the equivalent from the web viewer?
Also, is there a way to set a flag like cache_results: false in the config file? I'm having a hard time finding it in the docs if so. Thanks!ian
05/24/2024, 7:17 AMyaml
evaluateOptions:
cache: falsechris
05/29/2024, 12:42 AMchris
05/29/2024, 4:57 PMcache: false value, it still caches the resultsian
05/29/2024, 6:09 PM- maxConcurrency should just be maxConcurrencyian
05/29/2024, 6:10 PM- you make it a list itemchris
05/30/2024, 8:29 PMdescription: 'Segmenter'
prompts:
- " "
providers:
- id: 'python:call_segmenter.py'
label: 'Staging'
config:
env: 'staging'
- id: 'python:call_segmenter.py'
label: 'Production'
config:
env: 'production'
tests: segmenter_tests.yaml
evaluateOptions:
maxConcurrency: 2
delay: 500
showProgressBar: true
cache: false
Both when running via CLI when specifying that config in the web viewerian
05/30/2024, 9:22 PMcache: falsechris
05/30/2024, 9:56 PMdescription: 'Segmenter'
prompts:
- " "
providers:
- id: 'python:provider.py'
label: 'Staging'
config:
env: 'staging'
- id: 'python:provider.py'
label: 'Production'
config:
env: 'production'
tests: tests.yaml
cache: false
evaluateOptions:
maxConcurrency: 2
delay: 500
showProgressBar: true
it caches the results when running with CLI. on the webviewer, it doesnt even persist that change in the yaml after savingian
05/31/2024, 4:32 AMian
05/31/2024, 4:32 AMchris
05/31/2024, 4:08 PMcache: false in the config. I don't know if that's intended though, basically should yaml config supercede CLI args. I would vote yes