Clock start time is gone

Clock start time is gone

[Noah Slater]

Hello,

I'm moving point over a habit in the agenda, clocking on with I,
switching buffer a few times, then switching back and hitting O.

Occasionally, I get a "Clock start time is gone" message. I just got
one now. If I go to the node, I see this:

:LOGBOOK:
CLOCK: [2014-09-07 Sun 19:41]
- State "DONE"       from "TODO"       [2014-09-01 Mon 22:46]
CLOCK: [2014-09-01 Mon 22:01]--[2014-09-01 Mon 22:46] =>  0:45
...

So this doesn't make any sense. The clock start time is right there!

Any idea?

Thanks,

-- 
Noah Slater
https://twitter.com/nslater

Re: Clock start time is gone

[Yuri Niyazov]

Noah Slater <nslater <at> apache.org> writes:

> I'm moving point over a habit in the agenda, clocking on with I,
> switching buffer a few times, then switching back and hitting O.
> Occasionally, I get a "Clock start time is gone" message. I just got
> one now. If I go to the node, I see this:
> 
> :LOGBOOK:
> CLOCK: [2014-09-07 Sun 19:41]
> - State "DONE"       from "TODO"       [2014-09-01 Mon 22:46]
> CLOCK: [2014-09-01 Mon 22:01]--[2014-09-01 Mon 22:46] =>  0:45
> ...

I get this behavior pretty regularly as well, but I don't have a
 clear idea on how to reproduce it, or how to fix it. 
Has this been resolved?

clock start time is gone

[Samuel Wales]

recent maint.

just wondering what i could be doing wrong.

it is /usually/ the case that i get clock start tmie is gone when i
try to clock out.
it isn't gone.  so i do org-clock-cancel, which is slow.  this leaves
the start time.

so i do org-clock-in, which presents me with all the options.  i
choose K because i want to be clocked out.

but it ignores the K and keeps me clocked in.

so i clock out.  btw, clocking out is slow.
org-clock-remove-empty-clock-drawer takes up 95% of the time.

and this leaves me with a correct clock line and a new clock line with
0 time on it.

so then i have to kill the new clock line.

what i'd prefer is for clocking out to just work and be fast, without
extra actions required.  clearly i am doing something wrong.

-- 
The Kafka Pandemic: <http://thekafkapandemic.blogspot.com>

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
<http://www.meaction.net/2017/02/03/pwme-people-with-me-are-being-murdered-by-neglect>.

Re: clock start time is gone

[Nicolas Goaziou]

Hello,

Samuel Wales <samologist@gmail.com> writes:

> recent maint.
>
> just wondering what i could be doing wrong.
>
> it is /usually/ the case that i get clock start tmie is gone when i
> try to clock out.

This is odd, as this shouldn't be usual.

> it isn't gone.  so i do org-clock-cancel, which is slow.  this leaves
> the start time.
>
> so i do org-clock-in, which presents me with all the options.  i
> choose K because i want to be clocked out.
>
> but it ignores the K and keeps me clocked in.
>
> so i clock out.  btw, clocking out is slow.
> org-clock-remove-empty-clock-drawer takes up 95% of the time.

It is possible if you have really large clock drawers, i.e., hundreds of
clocks in it.

> and this leaves me with a correct clock line and a new clock line with
> 0 time on it.
>
> so then i have to kill the new clock line.

It would be nice to have an ECM for this report, with emphasis on the
"M".

Regards,

-- 
Nicolas Goaziou

Re: clock start time is gone

[Samuel Wales]

On 6/6/17, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> This is odd, as this shouldn't be usual.

just curious but why does it unless actually gone?  can't it just
check logbook drawer top line for a clock line?

> It is possible if you have really large clock drawers, i.e., hundreds of
> clocks in it.

no.

> It would be nice to have an ECM for this report, with emphasis on the
> "M".

agreed, but unlike my insufficient ad hoc report, ecm is definitely
not within my physical capacity at this time.  was hoping it would
inspire an idea or more a priori things to check.

-- 
The Kafka Pandemic: <http://thekafkapandemic.blogspot.com>

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
<http://www.meaction.net/2017/02/03/pwme-people-with-me-are-being-murdered-by-neglect>.

Re: clock start time is gone

[Nicolas Goaziou]

Hello,

Samuel Wales <samologist@gmail.com> writes:

> On 6/6/17, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>> This is odd, as this shouldn't be usual.
>
> just curious but why does it unless actually gone?  can't it just
> check logbook drawer top line for a clock line?

The active/last clock line could be at the beginning of the drawer, at
its end, anywhere else, there could be no drawer at all.

> agreed, but unlike my insufficient ad hoc report, ecm is definitely
> not within my physical capacity at this time.  was hoping it would
> inspire an idea or more a priori things to check.

OK. Let us know when you have something. Thank you.

Regards,

-- 
Nicolas Goaziou                                                0x80A93738

Re: clock start time is gone

[Samuel Wales]

perhaps it could put a temporary uuid in the task so that it knows
where to go?  silly idea, but i don't think i will be able to create
an mce.

On 6/14/17, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>> just curious but why does it unless actually gone?  can't it just
>> check logbook drawer top line for a clock line?
>
> The active/last clock line could be at the beginning of the drawer, at
> its end, anywhere else, there could be no drawer at all.

ok.  but it's right there, so i don't get why it would be gone.

-- 
The Kafka Pandemic: <http://thekafkapandemic.blogspot.com>

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
<http://www.meaction.net/2017/02/03/pwme-people-with-me-are-being-murdered-by-neglect>.

Re: clock start time is gone

[Samuel Wales]

this mce produces "clock start time is gone" bug in emacs -Q.  emacs
24, org maint.

===
* b
* clock in here, then sort below, then try to clock out here
*** SOMEWHAT b
*** c
*** c
*** c
*** c
*** sort here by alpha
***** asdfasd
***** asdfasd
***** asdfasd
***** asdfasd
***** asdfasd
*** c
*** c
*** c
*** FACT d
* d
===


On 6/5/17, Samuel Wales <samologist@gmail.com> wrote:
> recent maint.
>
> just wondering what i could be doing wrong.
>
> it is /usually/ the case that i get clock start tmie is gone when i
> try to clock out.
> it isn't gone.  so i do org-clock-cancel, which is slow.  this leaves
> the start time.
>
> so i do org-clock-in, which presents me with all the options.  i
> choose K because i want to be clocked out.
>
> but it ignores the K and keeps me clocked in.
>
> so i clock out.  btw, clocking out is slow.
> org-clock-remove-empty-clock-drawer takes up 95% of the time.
>
> and this leaves me with a correct clock line and a new clock line with
> 0 time on it.
>
> so then i have to kill the new clock line.
>
> what i'd prefer is for clocking out to just work and be fast, without
> extra actions required.  clearly i am doing something wrong.
>
> --
> The Kafka Pandemic: <http://thekafkapandemic.blogspot.com>
>
> The disease DOES progress. MANY people have died from it. And ANYBODY
> can get it at any time.
>
> "You’ve really gotta quit this and get moving, because this is murder
> by neglect." ---
> <http://www.meaction.net/2017/02/03/pwme-people-with-me-are-being-murdered-by-neglect>.
>


-- 
The Kafka Pandemic: <http://thekafkapandemic.blogspot.com>

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
<http://www.meaction.net/2017/02/03/pwme-people-with-me-are-being-murdered-by-neglect>.

Re: clock start time is gone

[Nicolas Goaziou]

Hello,

Samuel Wales <samologist@gmail.com> writes:

> this mce produces "clock start time is gone" bug in emacs -Q.  emacs
> 24, org maint.
>
> ===
> * b
> * clock in here, then sort below, then try to clock out here
> *** SOMEWHAT b
> *** c
> *** c
> *** c
> *** c
> *** sort here by alpha
> ***** asdfasd
> ***** asdfasd
> ***** asdfasd
> ***** asdfasd
> ***** asdfasd
> *** c
> *** c
> *** c
> *** FACT d
> * d
> ===

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou

Re: clock start time is gone

[Samuel Wales]

On 8/7/17, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Fixed. Thank you.

thank you!

i seem to get another bug, no active clock, on the same mwe:

:LOGBOOK:
CLOCK:
:END:

if i use -Q with these settings:

(setq org-log-into-drawer t)
(setq org-clock-into-drawer t)
(setq org-clock-mode-line-total 'today)
(setq org-clock-display-default-range 'untilnow)
(setq org-clock-in-resume t)


samuel

-- 
The Kafka Pandemic: <http://thekafkapandemic.blogspot.com>

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
<http://www.meaction.net/2017/02/03/pwme-people-with-me-are-being-murdered-by-neglect>.

Re: clock start time is gone

[Nicolas Goaziou]

Hello,

Samuel Wales <samologist@gmail.com> writes:

> i seem to get another bug, no active clock, on the same mwe:
>
> :LOGBOOK:
> CLOCK:
> :END:
>
> if i use -Q with these settings:
>
> (setq org-log-into-drawer t)
> (setq org-clock-into-drawer t)
> (setq org-clock-mode-line-total 'today)
> (setq org-clock-display-default-range 'untilnow)
> (setq org-clock-in-resume t)

I'm not sure about the steps required to reproduce your issue. What do
you do on the same mwe? Clock in

  "* clock in here, then sort below, then try to clock out here"

then sort at

  "*** sort here by alpha"

then clock out?


Regards,

-- 
Nicolas Goaziou

Re: clock start time is gone

[Samuel Wales]

On 8/7/17, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> I'm not sure about the steps required to reproduce your issue. What do
> you do on the same mwe? Clock in
>
>   "* clock in here, then sort below, then try to clock out here"
>
> then sort at
>
>   "*** sort here by alpha"
>
> then clock out?

yes.

-- 
The Kafka Pandemic: <http://thekafkapandemic.blogspot.com>

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
<http://www.meaction.net/2017/02/03/pwme-people-with-me-are-being-murdered-by-neglect>.

Re: clock start time is gone

[Nicolas Goaziou]

Hello,

Samuel Wales <samologist@gmail.com> writes:

> On 8/7/17, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>> I'm not sure about the steps required to reproduce your issue. What do
>> you do on the same mwe? Clock in
>>
>>   "* clock in here, then sort below, then try to clock out here"
>>
>> then sort at
>>
>>   "*** sort here by alpha"
>>
>> then clock out?

Then I cannot reproduce it. Either from maint or master branch.

Regards,

-- 
Nicolas Goaziou

Re: clock start time is gone

[Samuel Wales]

On 8/8/17, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Then I cannot reproduce it. Either from maint or master branch.

i am using vanilla org 9 maint which is recent as of your fixes, emacs
-Q from debian which is 24.4.1, my test case, and this command line:

clocking in produces this bt:

Debugger entered--Lisp error: (wrong-number-of-arguments decode-time 2)
  decode-time(nil t)
  org-clock-get-sum-start()
  #[0 ...
  funcall(#[0 ...
  org-clock-in(nil)
  call-interactively(org-clock-in nil nil)
  command-execute(org-clock-in)

which sounds familiar.  are you using emacs 24?

-- 
The Kafka Pandemic: <http://thekafkapandemic.blogspot.com>

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
<http://www.meaction.net/2017/02/03/pwme-people-with-me-are-being-murdered-by-neglect>.

Re: clock start time is gone

[Nicolas Goaziou]

Hello,

Samuel Wales <samologist@gmail.com> writes:

> clocking in produces this bt:
>
> Debugger entered--Lisp error: (wrong-number-of-arguments decode-time 2)

I see. The you are missing b561c8b7efa5e88763c67d9327507e01af601352.

You need to update Org.

Regards,

-- 
Nicolas Goaziou                                                0x80A93738