-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot change datatype of a collection #19064
Comments
There are a lot of tests for this in the codebase, here's one that I just put together: It is possible that you have a traceback somewhere in your logs, in that case it would be good if you can post that.
You'll need celery for changing datatypes in batch. If you don't have Celery that tab isn't shown. |
Celery was configured (I definitely forgot that was a requirement for that!)
and seems to be processing jobs
the tracebacks all look pretty normal:
|
You need to enable celery in the galaxy config (the jobs you listed are cron-style jobs), and
explains the second part. |
right there's multiple celery toggles. Yes you're right I'm missing enable celery tasks. this needs to be communicated more usefully to the user/admin, I think? e.g. showing the tab but disabling it and having a tooltip of "please enable celery tasks in your galaxy.yml to allow changing datatypes of a collection" would have potentially removed this issue completely.
I'm not sure it does? that was unrelated testing on the same dataset and i triggered it by trying to extract element identifiers from that collection (which required manually dragging it into the form, hence I didn't report that) though I can see how it looks related |
Is there a reason not to default Also, SQLAlchemy can be used as a results backend, is there any reason not to have Galaxy use it as the default if you don't specify something else (e.g. redis)? |
Regarding this, the default is now using a simple SQLite database as the results backend #17949 I think the main concern about enabling it by default was the user rate limiting issue, but if I remember correctly it was fixed some time ago, so probably we could enable it by default at this point. |
couldn't/shouldn't this default to using whatever the database connection is? so it could default to postgres when that's in use? either way would be great to have this enabled by default!! (or any notification to the end user that this feature is available in galaxy but disabled due to administrator (mis)configuration) |
For 25.0 we'll consider enabling Celery by default. |
Describe the bug
I'm trying to work around galaxyproject/tools-iuc#6493 which produces a collection labelled
txt,tabular
.Galaxy Version and/or server at which you observed the bug
The Galaxy Server is running version 24.1.4.dev0 , and the web client was built on Saturday Oct 26th 10:07:28 2024 GMT+2 .
Commit: ccf4353
Browser and Operating System
Operating System: Linux
Browser: Chrome
To Reproduce
Steps to reproduce the behavior:
I've tried two solutions:
Expected behavior
I can change the datatype, either via WF, or afterwards manually to work around issues manually.
Screenshots
Additional context
potentially xref #17734
The text was updated successfully, but these errors were encountered: