Nicholas Cilfone

@philipGaudreau Hmmmm this should have been caught by unit tests if something changed in a release... Working on seeing why it isn't covered and seeing what patch is needed. In...

Just thinking out loud here which might help you grok some of the internals of spock so you can contribute if you're up for it... ### Basics Most of the...

@svenstehle if you are still interested #254 should implement the Environment Resolver feature above. Apologies that you couldn't ever get the unit tests to run for #246... You might have...

Hi @wanicca It's possible and I see the difficulty with verbosity (and not 1:1 drop in for argparse)... However given the user defined hierarchy and inheritance, it's pretty hard to...

@bkleyn @skadio This is the minimal set of changes needed for Spock integration without heavily refactoring the backend and/or front-end API

I do not have the power to assign anymore but that doesn't prevent you from working on a PR to contribute!

Noted. Will see what it takes to support the basic non typing lib types. I'm assuming the following basic types: - `int` - `float` - `str` - `list` - `tuple`...

Current way to handle LR Scheduler: ```python stoke_optimizer= StokeOptimizer( optimizer = AdamW, optimizer_kwargs = { "lr" : 1e-3, "betas" : (0.9, 0.99), "eps" : 1e-8, "weight_decay" : 1e-4 } )...

@sualehasif Heads up, I think you might have wanted to respond to the PR on the deepspeed repo instead of this one!