It works! Thanks! And--getting back to the original request--it doesn't
have the multiplexing button anymore after setting it as avalable: false.
Awesome!
On Tue, Jul 2, 2013 at 7:19 PM, Brad Chapman wrote:
>
> Lee;
> I pushed a fix to the nglims fork on bitbucket which should resolve this
>
Lee;
I pushed a fix to the nglims fork on bitbucket which should resolve this
errors. Apologies, the nglims error is a mistake on my part. The way
Galaxy handles version updates changed a bit on the infrastructure side
and I hadn't coded correctly to handle all the cases.
You shouldn't need to re
Actually I didn't notice that I had an error in 114->115 in addition to
115->116 (below).
So actually I just deleted the whole database, checked out a fresh version
with hg, upgraded, upgraded the database with manage_db, and then ran the
add_defaults script for nglims. Everything works and is fi
Thanks! I did hg pull -u. For the database, I downgraded to 108 and then
upgraded again but got this error when upgrading. Is it due to the Ubuntu
bug? Or something else? Should I be sticking with a particular Hg version
instead of the latest?
$ sh manage_db.sh upgrade
115 -> 116...
Tables fo
On Mon, Jul 1, 2013 at 8:34 PM, Brad Chapman wrote:
>
> This was a typo in the downgrade function for one of the patches. I
> pushed a fix so if you update from bitbucket things should work smoothly
> again (once we get to problem 2 below).
>
> For anyone with galaxy-dist commit privileges, here'
Lee;
Thanks for all the patience with this. I'll take the errors in order:
> Original exception was:
> Traceback (most recent call last):
[...]
> raise TypeError("upgrade/downgrade functions must accept engine"
> TypeError: upgrade/downgrade functions must accept engine parameter (since
> ver
Thank you. I feel like this next error might be my fault (I don't know
python very well). I think it is saying that I don't have a module, but it
is installed via Ubuntu aptitude, so now I don't really know what to do
next. I reinstalled the module like so: aptitude reinstall python-apport
$ sh
It's that previous versions of sqlalchemy-migrate didn't clean up these tables
under sqlite and didn't mind overwriting them if they existed, but the new
version both does clean up after itself, and expects the table to not exist,
failing miserably if it does.
I think there's a Trello card for
Lee;
> Thanks Brad! I updated with hg pull -u and then ran "sh manage_db.sh
> upgrade" but I have an error. Could you help? I backed up my database
> before I ran the upgrade script, so I can go back in time.
I think there is something funky going on with the version of
SQLAlchemy-migrate cur
Thanks Brad! I updated with hg pull -u and then ran "sh manage_db.sh
upgrade" but I have an error. Could you help? I backed up my database
before I ran the upgrade script, so I can go back in time.
(sorry about the wall of text)
109 -> 110...
/home/galaxy/bin/chapman-dist/eggs/SQLAlchemy-0.7.9
Lee;
> Hi, I would like to remove the "multiplexed" menu from the nglims sample
> information form. How would I do that? In our lab, we don't want
> submitters making their own libraries since they might accidentally use the
> same barcodes or somehow mess up others' libraries. We want to remo
11 matches
Mail list logo