Closed eschnett closed 4 years ago
Looking deeper, the problem might be that the empty dictionary does not contain the default entries that should be present in the CalibanConfig
schema.
I pushed a change for this here: https://github.com/google/caliban/pull/41. I think this should be sufficient if you'd like to give it a shot prior to review/merge. I was able to reproduce what you saw and this fixes things for me.
Hey @eschnett , I believe this is fixed now with #41. Closing, but please re-open if you run into this again! (I've added some tests that check for this so we should be good.)
I'm also working on a patch that change the default mode to cpu
so you won't have to add that --nogpu
flag all over. The patch is a default_mode
setting that will let you choose the mode you prefer, with always the ability to override with a flag.
The latest commit seems to have introduce an error into handling configuration files. I have a project that does not have a
.calibanconfig.json
file, andcaliban shell
now reports an error:I believe the problem is that
caliban_config
creates an empty dictionary, andapt_packages
later tries to access the key"apt_packages"
in there.