billiing problem with old etm

12 views
Skip to first unread message

lawquest

unread,
Jan 2, 2020, 3:40:56 PM1/2/20
to Event and Task Manager
Dan,

I am slowly learning the new etm but for now at least I still log my time in old etm.  At the end of a month, I do up my "bills" for the staff to review.  I tried this just now for my December hours and got the following error.  Any suggestions? I guess I could re-input the hours into new etm and learn how to "do bills" on the new etm but very busy now and would prefer deferring the switch to the new etm a while longer. Now here is what I get:

"johwhi@johwhi:~$ etm c 'a c; ddd, MMM dd yyyy e -b -1/1 -e 1 -w 0'
--- 2020-01-02 12:29:53,864 - WARNING - data.items2Hashes
   error: bad timezone: 'US/Pacific
$'
       ('monthly/2018/11.txt', 134, 136)
--- 2020-01-02 12:29:54,089 - WARNING - data.items2Hashes
   error: bad timezone: 'US/Pacific
$'
       ('monthly/2018/10.txt', 242, 244)
Traceback (most recent call last):
 File "/usr/local/bin/etm", line 78, in <module>
   data.main(etmdir, sys.argv)
 File "/home/johwhi/.local/lib/python2.7/site-packages/etmTk/data.py", line 7779, in main
   res = c.do_command(argstr)
 File "/home/johwhi/.local/lib/python2.7/site-packages/etmTk/data.py", line 6953, in do_command
   res = self.cmdDict[cmd](arg_str)
 File "/home/johwhi/.local/lib/python2.7/site-packages/etmTk/data.py", line 7553, in do_c
   self.options)
 File "/home/johwhi/.local/lib/python2.7/site-packages/etmTk/data.py", line 4291, in getReportData
   temp.extend(expenseCharge(hsh, options))
 File "/home/johwhi/.local/lib/python2.7/site-packages/etmTk/data.py", line 4908, in expenseCharge
   expense = charge = float(hsh['x'])
ValueError: invalid literal for float(): 270, 70, 65
johwhi@johwhi:~$ etm c 'a c; ddd, MMM dd yyyy e -b -1/1 -e 1 -w 0'^C
johwhi@johwhi:~$ 

I have had the "bad time zone" error for months and just ignor it, so I think the new problem is something different.

John



lawquest

unread,
Jan 2, 2020, 5:08:08 PM1/2/20
to Event and Task Manager
For what its worth, I found the offending entry, removed it and old etm now works as expected.  The following language in the offending entry is what blew it up:

"@x 270, 70, 65"
Reply all
Reply to author
Forward
0 new messages