The Dockerfile in this project and the hack to always listen on localhost (ipv4 or ipv6) leads to a situation where the port in the container is not reachable from other containers or host.

Instead, kent should bind to :: or 0.0.0.0

This cannot be worked around with:

docker run -p 5000:5000 --entrypoint "" quay.io/dimaqq/kent flask --app kent.app run --host ::

Or in docker-compose.yaml:

version: "3.4"
services:
  sentry:
    image: quay.io/dimaqq/kent:latest
    ports:
      - "5000:5000"
    entrypoint: ""
    command: "flask --app kent.app run --host ::"

Because the Python code in kent specifically overrides the bind address with ::1 or 127.0.0.1 😭

> docker compose run sentry
 * Serving Flask app 'kent.app'
 * Debug mode: off
[2022-11-18 09:01:51,484] INFO: _internal: WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
 * Running on all addresses (::)
 * Running on http://[::1]:5000
 * Running on http://[::1]:5000

And thus the app is accessible from inside the container but not from outside the container.

This fixes Kent to work with Flask 2.1.0. Something about the way we were (ab)using Flask's cli was triggering an error in werkzeug. This fixes it.

Fixes #23.

Flask 2.1.0 released yesterday and kent fails with that:

> kent-server run
Traceback (most recent call last):
  File "/home/willkg/venvs/kent/bin/kent-server", line 33, in <module>
    sys.exit(load_entry_point('kent', 'console_scripts', 'kent-server')())
  File "/home/willkg/mozilla/kent/src/kent/cli_server.py", line 30, in main
    flask_cli.main()
  File "/home/willkg/venvs/kent/lib/python3.8/site-packages/flask/cli.py", line 579, in main
    return super().main(*args, **kwargs)
  File "/home/willkg/venvs/kent/lib/python3.8/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/home/willkg/venvs/kent/lib/python3.8/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/willkg/venvs/kent/lib/python3.8/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/willkg/venvs/kent/lib/python3.8/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/home/willkg/venvs/kent/lib/python3.8/site-packages/click/decorators.py", line 84, in new_func
    return ctx.invoke(f, obj, *args, **kwargs)
  File "/home/willkg/venvs/kent/lib/python3.8/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/home/willkg/venvs/kent/lib/python3.8/site-packages/flask/cli.py", line 851, in run_command
    run_simple(
  File "/home/willkg/venvs/kent/lib/python3.8/site-packages/werkzeug/serving.py", line 1047, in run_simple
    fd = int(os.environ["WERKZEUG_SERVER_FD"])
  File "/home/willkg/.pyenv/versions/3.8.10/lib/python3.8/os.py", line 675, in __getitem__
    raise KeyError(key) from None
KeyError: 'WERKZEUG_SERVER_FD'

The SDK docs talk about an Envelope endpoint:

https://develop.sentry.dev/sdk/envelopes/

I've seen that url pop up in the Kent logs when I'm using Kent.

Is there a compelling reason to implement this other than comprehensive sentry sdk support?

This updates the checkout and setup-python actions. This also fixes the push event to only run on the main branch and the pull_request event to only run on pull requests against the main branch.

This changes what gets logged when Kent gets a request. Previously, it would log all the HTTP headers. That's not helpful when you're debugging issues in an application. This changes it to log sentry-sdk related headers as well as the exception type/value or message from the payload.

This also logs the url for the event if you want to look at it.

Fixes #32.

This moves dev requirements out of EXTRAS and into a requirements-dev.txt file. This also updates them to current versions.

This updates the sample Dockerfile and the example in the README to use the latest Python 3.10 alpine image. It tweaks some comments and documentation around that, too. It switches to using the --init argument for docker run.

Sometimes I'm using Kent as a fakesentry service and I'm debugging things. When Kent gets a Sentry event, it logs information about the HTTP POST. It'd be more helpful if it logged information about the event. Maybe some information about the HTTP POST (size, sentry-trace, sentry-auth) and the event (summary)?

• switch to using build
• update version and release
• add kent_submit.py to manifest
• fix formatting of test_app.py
• update HISTORY
• remove lint environment from tox.ini -- we have a make rule and a CI item, so we don't need it in tox.ini as well

This adds a summary column to the error list table. It adds some helper CSS for that.

It also adds a kent_submit.py script to make it easier to test kent in local dev environment.

It also fixes the linting rule in tox and Makefile.

Fixes #27.

This changes flush from a GET to a POST. It changes the state of the server, so it should have been a POST all along.

This adds a "[Flush]" link to the index page for convenience. It saves you from having to curl the API directly or shutting down and restarting Kent.

This adds a kent-testpost command for using sentry-sdk and capturing a message. This makes it easier to manually test Kent.

Fixes #9

Kent server stores data from golang sentry integration as bytes, and is not able to render error list nor error details.

User-Agent: raven-go/1.0
Content-Length: 1872
Content-Type: application/octet-stream
X-Sentry-Auth: Sentry sentry_version=4, sentry_key=public
Accept-Encoding: gzip

I get zero signal for the work I do and have no idea if it's generally positive or negative in the world. I do a lot of work, so this is weird.

I'm experimenting with ways to get some signal with the least amount of effort for you.

If you have some positive feeling about Kent (it's useful! you think it's a cool idea! you with you named your project Kent!), add a :smile: or a +1 or something with the thing in the upper right hand corner.

If you have some negative feeling about Kent, add a :frown: or a -1.