Despite following this, the environmental setting is still problematic. I ran the Pass@1 evaluation using the oracle code snippets from data.jsonl:
Running pass@1 for local_infilling oracle_greedy
TODO Completions: 275
100%|██████████| 275/275 [13:33<00:00, 2.96s/it]
pass_at_1: 36.36363636363637%
My conjecture is that, as some repositories do not specify their package versions, the environmental set up is prune to be stale.
A best way is providing a docker like bigcode-evaluation-harness. I notice that you are making a docker. I wonder when would it be available.
Before that, you may share the specific pip version and update the repo's requirements.txt with specific package versions by pip freeze.
Despite following this, the environmental setting is still problematic. I ran the Pass@1 evaluation using the oracle code snippets from
data.jsonl:My conjecture is that, as some repositories do not specify their package versions, the environmental set up is prune to be stale.
A best way is providing a docker like bigcode-evaluation-harness. I notice that you are making a docker. I wonder when would it be available.
Before that, you may share the specific pip version and update the repo's requirements.txt with specific package versions by pip freeze.