Skip to content

westonpace/one-true-error

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Problems with current approach

Expensive imports

The current error-per-workspace approach means that the "core module" in the workspace has a ton of dependencies (some behind flags, some not) and is very heavy-weight. This is because we have to add the From impls into the core module.

Too many possibilities

By the time an error reaches the top-level HTTP handler, it could be one of many different types of errors. It's pretty much impossible to assign an HTTP error code correctly.

Loops

Sometimes we get things like LanceDBError(DataFusionError(LanceDBError(...))) and there end up being many layers of wrapping.

Lack of backtraces

There's a lot of situations where we don't have backtraces or just the location. We can do better now.

Context rarely added

We have a lot of errors that don't have context added to them. This makes it hard to debug.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages