-
Notifications
You must be signed in to change notification settings - Fork 69
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
Builder updates (topology) #21
Conversation
@mkhorton wrt logging, I added a logging utility to maggma.lava.util before @shyamd nuked the
Perhaps you can re-add this util somewhere? |
Ok, thanks. Regarding the first issue I mentioned I added a quick:
to Store.update in my maggma PR materialsproject/maggma#15 unless there's a better solution to this |
Can you ensure the codacy issues are worked out? Ignore the unused variable class. I turned off that rule just now. 1.) I'll fix the first issue in maggma runner. |
Thanks! |
Topology builders should work now, including with Nil's OPs. I need to submit a quick bugfix to pymatgen too, but this won't change the builder.
I did run into a few issues:
When trying to
update_targets
with only a few documents,items
is padded with None values to meet the chunk size (which is fine), but the Storeupdate
method can't handle these None values... can submit a quick fix to maggma for this unless something else is planned?For a reason I couldn't figure out, I had to manually
.connect()
to a Store before the Runner would work. Error message wasn't too helpful here,.query()
just returned None, instead of warning the Store wasn't accessible?I'm not sure why, but many errors/exceptions seemed to not display to stdout unless I was running my build script interactively... is there a logging setting to change this somewhere? Would help with debugging.