When user encounter error in dashboard, can we show the specific error information rather than 'Unexpected error'?

For example for Missing dataset error, can we show the error title to bubble up as 'Missing dataset' rather than 'Unexpected error'? It will be easier for user to see specific error right away.

<img width="674" alt="Screen Shot 2021-10-01 at 10 48 24 AM" src="https://user-image

Opened from the Prefect Public Slack Community

michael.ball: Hey there. I’ve been playing around with Docker storage today, trying to get all source code packaged together with the flows each time they are registered, and am using the files and env_vars attributes as outlined in the Docs. But it seems that my .dockerignore file (in the directory from whic

Describe the bug
data docs columns shrink to 1 character width with long query

To Reproduce
Steps to reproduce the behavior:

1. make a batch from a long query string
2. run validation
3. render result to data docs
4. See screenshot
   <img width="1525" alt="Data_documentation_compiled_by_Great_Expectations" src="https://user-images.githubusercontent.com/928247/103230647-30eca500-4

Steps to reproduce

1. Log out of GUI.
   Result: Get logged out, redirect to page auth/login?next=%2Fauth%2Flogin.
2. Log in.
   Result: Get logged in, but redirected to auth/login as requested.
3. Ignore URL bar, ask "what just happened?" and log in again.
   Result: Get logged in, redirect to main page.

Analysis

The next query parameter after logging out seems wro

if they are not class methods then the method would be invoked for every test and a session would be created for each of those tests.

`class PySparkTest(unittest.TestCase):
@classmethod
def suppress_py4j_logging(cls):
logger = logging.getLogger('py4j')
logger.setLevel(logging.WARN)

@classmethod
def create_testing_pyspark_session(cls):
    return Sp

Brief Description of Fix

When I see docs I found [get_features_targets page](https://pyjanitor-devs.github.io/pyjanitor/reference/janitor.functions/janitor.get_features_targe

Sphinx's built-in search isn't great. It'd be much better to use Algolia or similar.

Looks like it's possible:

https://stackoverflow.com/q/54872828/709975
readthedocs/sphinx_rtd_theme#761

If anyone wants to take this, I'm happy to help.

In the repository handler

• removeEntity tries to delete then if delete is not supported issues a purge, the purge method issues an audit log
• There are 2 callers to purgeRelationship only one of which audit logs

This is inconsistent.
I suggest we move the relationship audit log to the purge method, which means that both callers will audit log.