Very slow to start and also not monitoring

[awesomebytes]

I tried this package (looks superuseful!) but it needed a long time to initialize a run, took very long to execute it and the monitoring didnt show anything.

Pasting the output of a test run:

I executed:
time smiley run -v --local --database smiley.db test.py
database already initialized
ignoring packages under /usr/local/lib/python2.7/dist-packages/smiley/
ignoring packages under /usr/local/lib/python2.7/dist-packages/coverage/
ignoring packages under /usr/lib/python2.7/
ignoring packages under /usr/lib/python2.7/
ignoring packages under /usr/lib/python2.7/
ignoring packages under /usr/lib/python2.7/
including site-packages /usr/local/lib/python2.7/dist-packages
hola
1
2
3
4
5

real    0m13.503s
user    0m0.248s
sys 0m0.088s

On another terminal:

smiley monitor -v
Waiting for incoming data

Nothing happens there.

I installed it following your instructions on the docs (sudo pip install).

Thanks for your work!

Oh, and my test code looks like this:

#! /usr/bin/env python
# -*- coding: utf-8 -*-
"""
Created on Tue Oct 22 12:00:00 2013

@author: sam
"""
print "hola"

lista = [1,2,3,4,5]
for elem in lista:
    print elem

[dhellmann]

The "--local" option is telling the run command to not monitor, and just write data directly to the database you've specified. Have a look at the "server" and "replay" commands for accessing that data.

I don't see the same performance issues you report, so I'm not sure what's going on there. Did you install smiley into a virtualenv before running it, or are you running from source (maybe it's byte-compiling the code)? Are you running over an NFS connection? Is there anything else about your setup that you can describe that might be related?

[awesomebytes]

I tried without parameters at the first tries and nothing happened either.
I just saw those parameters in a .sh file in the repo and tried them.
Also the web server shows nothing and the smiley.db has nothing in it.

I have no virtual envs.
Running on my hd (no remote disks) on an ubuntu 12.04.

I'll give it another try on another computer this weekend!
El 03/01/2014 14:18, "Doug Hellmann" notifications@github.com escribió:

The "--local" option is telling the run command to not monitor, and just
write data directly to the database you've specified. Have a look at the
"server" and "replay" commands for accessing that data.

I don't see the same performance issues you report, so I'm not sure what's
going on there. Did you install smiley into a virtualenv before running it,
or are you running from source (maybe it's byte-compiling the code)? Are
you running over an NFS connection? Is there anything else about your setup
that you can describe that might be related?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/25#issuecomment-31521749
.

[marksteve]

Fresh install here. Seems like it doesn't default to --remote like what the help says. A smiley.db is created after running smiley run ./script.py so I guess --local is default.

[tucbill]

I agree, the default is --local as code is written today. Suggest the following change and docs become correct:

diff --git a/smiley/commands/run.py b/smiley/commands/run.py
index c2d9750..0377719 100644
--- a/smiley/commands/run.py
+++ b/smiley/commands/run.py
@@ -93,10 +93,10 @@ class Run(command.Command):
         sys.argv = parsed_args.command

         # Run the app
-        if parsed_args.mode == 'remote':
-            p = publisher.Publisher(parsed_args.socket)
-        else:
+        if parsed_args.mode == 'local':
             p = local.LocalPublisher(parsed_args.database)
+        else:
+            p = publisher.Publisher(parsed_args.socket)
         t = tracer.Tracer(
             p,
             include_stdlib=parsed_args.include_stdlib,