Debugging "500 bad request" type exceptions

Sometimes I write code that has bugs. I know, I know, I’m embarrassed to admit it.

When I make a bad call to a neptune function like create_experiment, the result is generally an HTTP error. Is there some way to get more info about what the server is objecting to? (And if the answer to that is “no”, then I’ll resubmit this as a feature request…)

Hi @densied,

We’ll definitely work on throwing more meaningful exceptions.
Thanks for the push :slight_smile:

@piotr.lusakowski: you are welcome :slight_smile: