Thanks much, Carlos - I owe you a beer!
On Mon, Feb 4, 2013 at 4:01 PM, Dan Tenenbaum wrote:
> On Mon, Feb 4, 2013 at 11:45 AM, Carlos Borroto
> wrote:
> > On Mon, Feb 4, 2013 at 1:55 PM, Dan Tenenbaum
> wrote:
> >>> Re: login: I believe there's a redirect in place that moves you past
> the
>
Even better - thanks again, Carlos - and thanks for the help in tracking
this down, Dan.
On Mon, Feb 4, 2013 at 4:46 PM, Dan Tenenbaum wrote:
> On Mon, Feb 4, 2013 at 1:21 PM, Carl Eberhard
> wrote:
> > Just to be clear, Dan - this solved the login issue and not the upload
> issue
> > (in whic
On Mon, Feb 4, 2013 at 4:46 PM, Dan Tenenbaum wrote:
> On Mon, Feb 4, 2013 at 1:21 PM, Carl Eberhard wrote:
>> Just to be clear, Dan - this solved the login issue and not the upload issue
>> (in which case I'd owe Carlos a six-pack), correct?
>
> Sorry...this solved both issues.
Great, glad it h
On Mon, Feb 4, 2013 at 1:21 PM, Carl Eberhard wrote:
> Just to be clear, Dan - this solved the login issue and not the upload issue
> (in which case I'd owe Carlos a six-pack), correct?
Sorry...this solved both issues.
Dan
> C
>
>
> On Mon, Feb 4, 2013 at 4:04 PM, Carl Eberhard
> wrote:
>>
>>
Just to be clear, Dan - this solved the login issue and not the upload
issue (in which case I'd owe Carlos a six-pack), correct?
C
On Mon, Feb 4, 2013 at 4:04 PM, Carl Eberhard wrote:
> Thanks much, Carlos - I owe you a beer!
>
>
> On Mon, Feb 4, 2013 at 4:01 PM, Dan Tenenbaum wrote:
>
>> On Mo
On Mon, Feb 4, 2013 at 11:45 AM, Carlos Borroto
wrote:
> On Mon, Feb 4, 2013 at 1:55 PM, Dan Tenenbaum wrote:
>>> Re: login: I believe there's a redirect in place that moves you past the
>>> older 'Return to the homepage' message automatically - I think you're good
>>> there (and logged in). Are
On Mon, Feb 4, 2013 at 1:55 PM, Dan Tenenbaum wrote:
>> Re: login: I believe there's a redirect in place that moves you past the
>> older 'Return to the homepage' message automatically - I think you're good
>> there (and logged in). Are you seeing the 'Logged in as ' in the
>> 'User' menu at the t
Sorry about the miscommunication: when I mentioned 'make sure you're using
a fresh history' I meant that you may want to go to the history options
menu (the gear in the upper right of the history panel and click 'Create
new'). It may be that previous datasets are causing some of the problems
we're
Hello, Dan.
I'm glad you updated.
I noticed another error in your log:
127.0.0.1 - - [04/Feb/2013:09:50:43 -0700] "POST
/tool_runner/upload_async_create HTTP/1.1" 500 - "http://localhost:8080/";
"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.17 (KHTML,
like Gecko) Chrome/24.0.1312
Ok - interesting!
Can you send me the paster.log from a daemon session where you try an
upload?
Steps for that are:
1. from the directory of your galaxy installation: sh run.sh --daemon (you
should see 'Entering daemon mode')
2. Wait a minute, then load localhost:8080 in your browser, login, and t
On Wed, Jan 30, 2013 at 11:36 AM, Carl Eberhard wrote:
> Well - as long as those errors don't happen again - it may well be progress.
>
> For the next step, can you:
> 1. open Galaxy in Chrome
> 2. Go to the settings menu (the button with three horizontal bars on the
> right side of the address ba
On Wed, Jan 30, 2013 at 10:36 AM, Carl Eberhard wrote:
> Dan,
> Are you cloning from galaxy-central or galaxy-dist? Are you cloning from the
> tip or a specific revision?
>
I installed galaxy as recommended in the docs:
hg clone https://bitbucket.org/galaxy/galaxy-dist/
> When you see the Synt
On Mon, Jan 28, 2013 at 1:59 PM, Carl Eberhard wrote:
> If you go to your galaxy root in a terminal and then cd to eggs, what is the
> version listed for SQLAlchemy?
>
SQLAlchemy-0.5.6_dev_r6498-py2.7.egg
> Do you have SQLAlchemy installed already on that machine (apart from the one
> in Galaxy
If you go to your galaxy root in a terminal and then cd to eggs, what is
the version listed for SQLAlchemy?
Do you have SQLAlchemy installed already on that machine (apart from the
one in Galaxy's eggs)?
On Mon, Jan 28, 2013 at 4:50 PM, Dan Tenenbaum wrote:
> On Mon, Jan 28, 2013 at 1:40 PM,
On Mon, Jan 28, 2013 at 1:40 PM, Carl Eberhard wrote:
> I was incorrect in stating that the changes in the next galaxy-dist will
> help in this case, unfortunately. From the stack trace you posted, there is
> a deeper error with your instance that the client-side changes won't help.
>
> Can you po
I was incorrect in stating that the changes in the next galaxy-dist will
help in this case, unfortunately. From the stack trace you posted, there is
a deeper error with your instance that the client-side changes won't help.
Can you post the size, type, and name of the file you're trying to upload?
On Wed, Jan 23, 2013 at 3:19 PM, Carl Eberhard wrote:
> Another thing you might try is to upload the file to our test server:
> https://test.g2.bx.psu.edu/ and see if that works.
>
Thanks, that does work.
Setting up an FTP server on my local installation seems pretty
complex. All I really want t
Another thing you might try is to upload the file to our test server:
https://test.g2.bx.psu.edu/ and see if that works.
On Wed, Jan 23, 2013 at 6:06 PM, Carl Eberhard wrote:
> If this is happening consistently and a refresh on the history isn't doing
> anything, you might try ftp upload:
> http
If this is happening consistently and a refresh on the history isn't doing
anything, you might try ftp upload: http://wiki.galaxyproject.org/FTPUpload
or if you have permissions or are an admin you can try uploading to a data
library:
http://wiki.galaxyproject.org/Admin/DataLibraries/UploadingLib
On Wed, Jan 23, 2013 at 2:42 PM, Carl Eberhard wrote:
> What sort of database are you using on your local instance?
>
The default (sqlite I guess). It's a completely vanilla instance, I
have not touched the config files.
Dan
>
> On Wed, Jan 23, 2013 at 5:37 PM, Dan Tenenbaum wrote:
>>
>> On We
What sort of database are you using on your local instance?
On Wed, Jan 23, 2013 at 5:37 PM, Dan Tenenbaum wrote:
> On Wed, Jan 23, 2013 at 2:35 PM, Carl Eberhard
> wrote:
> > Thanks, Dan. That helps and I'll start looking into this.
> >
> > We will be pushing out a new galaxy-dist revision so
On Wed, Jan 23, 2013 at 2:35 PM, Carl Eberhard wrote:
> Thanks, Dan. That helps and I'll start looking into this.
>
> We will be pushing out a new galaxy-dist revision sometime this week if all
> goes well. This revision includes some code for the history panel that may
> help handle this situatio
Thanks, Dan. That helps and I'll start looking into this.
We will be pushing out a new galaxy-dist revision sometime this week if all
goes well. This revision includes some code for the history panel that may
help handle this situation a bit better. I'd recommend updating to that
revision when it
Hi Carl,
On Wed, Jan 23, 2013 at 2:14 PM, Carl Eberhard wrote:
> Heya, Dan.
>
> Sorry for the trouble.
> When you get that error again look for a line like you have above:
> Debug at: http://localhost:8080/_debug/view/1358978130
>
> If you open a new tab or window in your browser and go to the ad
Heya, Dan.
Sorry for the trouble.
When you get that error again look for a line like you have above:
Debug at: http://localhost:8080/_debug/view/1358978130
If you open a new tab or window in your browser and go to the address ('
http://localhost:8080/_debug ...'), you should see a more informativ
25 matches
Mail list logo
