Replaces our custom Sentry WSGI middleware with middleware shipped by
sentry-sdk. Adds sentry-sdk ASGI middleware. Our custom sentry
middleware also allowed logging slow requests to sentry. I have dropped
this for now, and if we still want this in the future, we should
probably implement this as a custom logging middleware instead, which
would automatically appear in Sentry as well.
We used to hardcode the log level for events to WARNING, and the Sentry
default is ERROR now, which I think is a good idea. I've made this
configurable using the sentry_event_level config variable.
It does not seem to be possible to connect multiple dsn's in the same
app, unless we start hacking
(https://github.com/getsentry/sentry-python/issues/198), so I dropped
the custom_dsn from the sentry error reporting plugin (which has been
broken anyway, so shouldn't be a big deal).
make runnable from pr. Still need to debug
divs out
tree
broken into components
cleaning
formatting, file names, jest tests
jest
removed image files, will be retrieved via npm or separate repo
update
plugin via webpack
webpack plugin
change to plugin to prevent repeated image downloading
update
add actual page accessible from help and registration
Full draft
jest fix, next to make package customizeable
yarn lock
fix
update
Update
Refactor from here for the confiuration stuff -- this displays the bundle
drop plugin_build_hash -- these should never be committed
Update plugin gitignore
Oops, left in a debug
Addresses https://github.com/galaxyproject/galaxy/issues/11488.
One drawback here is that if multiple jobs are concurrently creating
datasets in a history the HID is not guaranteed to be sequential
between chunks. We can address this, but this is also a problem
when breaking workflow executions at
``maximum_workflow_jobs_per_scheduling_iteration``.
If we consider this to be a problem (personally I don't think it is, but
I could be convinved otherwise) I would work on this in a different PR.
On the upside the history panel will display an increasing amount of
datasets created during the dataset discovery.
It's kind of brittle, and https://github.com/galaxyproject/galaxy/pull/10804
has improved the parsing so much that it doesn't add much benefit.
Instances on Anvil start up in ~ 32 seconds, with all of main's toolbox.
And always serialize input dataset metadata using the model exports.
This means we don't have to pickle anymore, which breaks with weakrefs
used by sqlalchemy-json's Mutable class.
mvdbeek