logs/keyfreq_...txt

[Sam Shleifer]

My key freq log file has timestamps, but each timestamp has a zero associated with it. When I load the webpage, there is no number next to total number of key strokes: The other log file looks reasonable.

➜ ulogme git:(master) cat logs/keyfreq_1417262400.txt
1417318604 0
1417318613 0
1417318622 0
1417318631 0
1417318640 0
....

[Andrej]

Did you go through the readme file and instructions in full? I assume you're probably using a Mac? I think you probably have to authorize Terminal in your settings. From Readme:

For iOS only: there might be an additional step where you have to go to System Preferences > Security & Privacy > Accessibility, and make sure that Terminal (or iTerm2, or whatever you use to launch ulogme) is checked. If it wasn't checked previously and you just checked it, you may need to restart ulogme. If you don't do this step, you might find that window logging works but keypress logging doesn't.

let me know if this works!

[Sam Shleifer]

I am using a Mac with Yosemite. (I thought iOS meant iPhone when I read
it). Problem persists, even after i give access. (Tried for both terminal
and iTerm.) Have tried restarting ulogme.
Potential hint: It never asks me for sudo access.

Sam

On Sun Nov 30 2014 at 12:07:03 AM Andrej [e-mail] wrote:

Did you go through the readme file and instructions in full? I assume
you're probably using a Mac? I think you probably have to authorize
Terminal in your settings. From Readme:

For iOS only: there might be an additional step where you have to go to
System Preferences > Security & Privacy > Accessibility, and make sure that
Terminal (or iTerm2, or whatever you use to launch ulogme) is checked. If
it wasn't checked previously and you just checked it, you may need to
restart ulogme. If you don't do this step, you might find that window
logging works but keypress logging doesn't.

let me know if this works!

—
Reply to this email directly or view it on GitHub
#14 (comment).

[Sam Shleifer]

No new data in browser, even though log files have expanded, grown more
numerous.
Tried running export_events again, and getting:

➜ ulogme git:(master) ✗ python export_events.py
Traceback (most recent call last):
File "export_events.py", line 116, in
updateEvents()
File "export_events.py", line 53, in updateEvents
ts = [int(x[x.find('_')+1:x.find('.txt')]) for x in L]
ValueError: invalid literal for int() with base 10: "1417348800
(Sams-MacBook-Pro-2's conflicted copy 2014-11-30 (1))"

On Sun Nov 30 2014 at 1:18:54 AM Sam Shleifer [e-mail] wrote:

I am using a Mac with Yosemite. (I thought iOS meant iPhone when I read
it). Problem persists, even after i give access. (Tried for both terminal
and iTerm.) Have tried restarting ulogme.
Potential hint: It never asks me for sudo access.

Sam

On Sun Nov 30 2014 at 12:07:03 AM Andrej [e-mail] wrote:

Did you go through the readme file and instructions in full? I assume
you're probably using a Mac? I think you probably have to authorize
Terminal in your settings. From Readme:

For iOS only: there might be an additional step where you have to go to
System Preferences > Security & Privacy > Accessibility, and make sure that
Terminal (or iTerm2, or whatever you use to launch ulogme) is checked. If
it wasn't checked previously and you just checked it, you may need to
restart ulogme. If you don't do this step, you might find that window
logging works but keypress logging doesn't.

let me know if this works!

—
Reply to this email directly or view it on GitHub
#14 (comment).

[Javi Rubio]

Hi @sshleifer, I'm running ulogme in Yosemite for a few days and didn't have your problems. First time all web was empty though, because I forgot to customize my render settings. Did you $ cp render/render_settings_example.js render/render_settings.js?

I didn't need to execute export_events.py

[Sam Shleifer]

Yes, I did. Web is not empty; just hasn't been updated since the first day
I used the tool.
Thanks,
Sam

On Thu Dec 04 2014 at 11:31:17 AM Javier Rubio [e-mail]
wrote:

Hi @sshleifer https://github.com/sshleifer, I'm running ulogme in
Yosemite for a few days and didn't have your problems. First time all web
was empty though, because I forgot to customize my render settings. Did you $
cp render/render_settings_example.js render/render_settings.js?

I didn't need to execute export_events.py

—
Reply to this email directly or view it on GitHub
#14 (comment).

[Javi Rubio]

but you keep running ulogme.sh and (optionally) the python ulogme_serve.py ? The first is the logger facility and the second just parses that data. You will see a "ulogme_osx" when pressing cmd+tab for switching apps.

[Sam Shleifer]

Yeah, it's running.

On Thu, Dec 4, 2014 at 12:55 PM Javier Rubio [e-mail]
wrote:

but you keep running ulogme.sh and (optionally) the python ulogme_serve.py
? The first is the logger facility and the second just parses that data.
You will see a "ulogme_osx" when pressing cmd+tab for switching apps.

—
Reply to this email directly or view it on GitHub
#14 (comment).

[Alec Crowell]

I'm having the same issue, is this still unresolved?

[andymaheshw]

Yes, the trick is to start the script, go to accessibility, you will see iTerm, add it. Stop the script, and restart again.