User facing errors about invalid values for the DAGSTER_HOME environment variable are not helpful, and sometimes reference internal functions. These error messages should be updated to explain to the user what DAGSTER_HOME is and how to set it.

When DAGSTER_HOME is not set:

raise DagsterInvariantViolationError(
dagster.core.errors.DagsterInvariantViolationError: DAGSTER_HOME 

Currently such a request would return an HTTP 500:

curl -H "Authorization: Bearer <valid token>" "http://localhost:7575/v1/packages/not-a-real-package-id"

I believe this is unexpected and an HTTP 404 would be more appropriate, which would mean (specification):

10.4.5 404 Not Found

The server has not found anythi

Describe the bug
Deploying a new job, then pulling logs via the CLI results in a panic (SIGSEGV).

To Reproduce

1. odin deploy -f test.job.yaml
2. odin log -i {job_id}

vagrant@vagrant:~/odin$ odin log -i dea194794589
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x40 pc=0x79c764]

goroutine

Helm chart with an optional development postgres DB included.

I am not sure if this belongs here, but I am having an issue when using this Github Action.

This is the link to the github run that failed:
https://github.com/jampp/migratron/pull/25/checks?check_run_id=456554120

and the content is:

Uploading distributions to https://test.pypi.org/legacy/
Uploading migratron-1.1.0-py3-none-any.whl

  0%|          | 0.00/30.5k [00:00<?, ?B/s]
100%|

As of alpha 2.685 there's a new action trigger_named_async_without_response which can be used in favor of trigger_named. Wrapper does not operate on trigger response anyway, so using the new method which works better for broader spectrum sounds like a good idea. More on that here: https://community.folivora.ai/t/floating-html-settings-menu/5788/44?u=worie