Including date or time in clocktable report - org-mode

I didn't think this was going to be hard but I couldn't dig up anything on how to make an org-mode clock table report include the date/time of the task. My report is like this:
#+BEGIN: clocktable :scope agenda-with-archives :timestamp "TIMESTAMP" :link nil :maxlevel 3 :tstart "<-1w>" :tend "<now>" :stepskip0 t :fileskip0 t :tcolumns 3 :narrow 110 :hidefiles t
#+CAPTION: Clock summary at [2021-01-20 Wed 10:47]
| | | <110> | | |
| File | Timestamp | Headline | Time | |
|-----------------+-----------------------------+----------------------------------------------------------------------------+---------+------|
| | ALL | -Total time- | -12:36- | |
|-----------------+-----------------------------+----------------------------------------------------------------------------+---------+------|
| inbox.org | | -- File time | *1:12* | |
| | | Inbox | 1:12 | |
| | | \_ Chat w/Saranya | | 0:01 |
| | [2021-01-20 Wed 10:45] | \_ Troubleshoot Cylance/3503 issue | | 1:11 |
|-----------------+-----------------------------+----------------------------------------------------------------------------+---------+------|
| 01-14.org | | -- File time | *1:11* | |
| | | \_ MEETING: Build discussion/working session | | 1:11 |
|-----------------+-----------------------------+----------------------------------------------------------------------------+---------+------|
| 01-18.org | | -- File time | *1:25* | |
| | | \_ MEETING: MBean registration failures in MAG DEV2 (and MAG QA2) | | 1:25 |
|-----------------+-----------------------------+----------------------------------------------------------------------------+---------+------|
| 01-19.org | | -- File time | *1:55* | |
| | | \_ MEETING: nTier Bi-Weekly - Check point | | 1:00 |
| | | \_ MEETING: MBE Project Status Update Meeting - Investment and MRO | | 0:39 |
| | | \_ MEETING: Discuss problems encountered when installing package for 3503 | | 0:16 |
|-----------------+-----------------------------+----------------------------------------------------------------------------+---------+------|
| admin.org | | -- File time | *0:12* | |
| | | Admin | 0:12 | |
| | <2021-01-14 Thu 09:00 ++1w> | \_ Manage timesheet | | 0:07 |
| | <2021-01-13 Wed 09:00 ++1w> | \_ Create Deploy & Environments Meeting Agenda | | 0:05 |
|-----------------+-----------------------------+----------------------------------------------------------------------------+---------+------|
...
What I'd like is to NOT have the File column and then have some type of timestamp for each task. I've tried various special properties but I can't seem to find anything that consistently gives me a timestamp.
If I have a log entry that has a recurring schedule or an inactive timestamp outside of the property drawer then it's able to pick something up. For example, in the table above the underlying tasks had entries like this:
** WIP Troubleshoot Cylance/3503 issue :MBE:
:PROPERTIES:
:CREATED: <2021-01-20 Wed 10:46>
:END:
:LOGBOOK:
CLOCK: [2021-01-20 Wed 09:35]--[2021-01-20 Wed 10:46] => 1:11
:END:
[2021-01-20 Wed 10:45] - <snip log entry>.
...
** WIP [#B] Create Deploy & Environments Meeting Agenda
SCHEDULED: <2021-01-13 Wed 09:00 ++1w>
:PROPERTIES:
:LAST_REPEAT: [2021-01-06 Wed 09:35]
:EFFORT: 0:15
:END:
:LOGBOOK:
CLOCK: [2021-01-20 Wed 08:42]--[2021-01-20 Wed 08:47] => 0:05
<snip>
CLOCK: [2020-07-14 Tue 16:17]--[2020-07-14 Tue 16:39] => 0:22
:END:
The problem is most of my tasks are either unscheduled and/or don't have timestamps outside of the logbook. I've tried various values for the :timestamp parameter but it doesn't seem to matter.
Can anyone advise how to create a clock table with task times in a column?
Another problem I have is that even with :hidefiles it always shows the File column.

I'm still pretty new at using clock tables in org-mode, but I came across your question when I was searching for something related to org-mode the other day.
Something that might help with displaying timestamps relates to using a setting called :properties("CLOSED"). I read about this from a post by #Fabian. When this setting is used, it adds a column named "CLOSED" that should display the date-time-stamp of when a task was "CLOSED".
Before this works, however, you might need to add the following setting to your .emacs settings file first: (setq org-log-done 'time). I read about this in the org-mode documentation. When this setting is set, and if you are using the "TODO" feature in org-mode: once you set a task to "DONE", a "CLOSED" date-time-stamp should be added to your task. From there, once you refresh your clock table, this new date-time-stamp should appear in the "CLOSED" column.
Also, from playing around with the :hidefiles settings, I ran into the same problem you had where the "File" column kept showing up even with the :hidefiles setting set. My previous attempt at fixing this (in the earlier answer revision) appears to not actually be doing what I thought it was doing, so I took that part out for now. I have the feeling that this :hidefiles setting issue might be related to the version of org-mode that is being used.
Update: After trying a more recent version of org-mode (20210201), the :hidefiles setting appears to be working as expected. I installed the new org-mode version using the setting instructions from this documentation page along with the following steps.
Warning: You may want to use an older version of org-mode depending on your needs. For myself, I tried out a very recent version of org-mode (at the time of this writing), but it might be too new for your purposes. Please consider if you need to try an older version before going through the following steps if you choose to do so.
Add these lines to the .emacs file:
(require 'package)
(add-to-list 'package-archives '("org" . "https://orgmode.org/elpa/") t)
Open up a blank emacs editor
Type: M-x list-packages
Navigate to the org option (I picked the 20210201 option, but this might vary) so that the cursor is over the org link
Push the return/enter key
Type: C-x o
Navigate to the Install option so that the cursor is over the Install link
Push the return/enter key
Push y to continue if you want to install this
The package should install at this point
When done, exit out of emacs
Then, open up your .org file
Also: I added the following setting to my .emacs file, because I generally like to hide the various lists in my .org file when it first gets opened in org-mode:
; ref: https://orgmode.org/guide/Visibility-Cycling.html
(setq org-startup-folded t)
Here is an updated example of the settings I used in my example.org file (partly based on your original example):
#+BEGIN: clocktable :scope agenda-with-archives :properties("CLOSED") :maxlevel 3 :tstart "<-2w>" :tend "<now>" :timestamp t :hidefiles t
#+CAPTION: Clock summary at [2021-02-01 Mon 16:30]
| Timestamp | CLOSED | Headline | Time | |
|-----------------------------+------------------------+----------------------------------------------+--------+------|
| | | *Total time* | *1:17* | |
|-----------------------------+------------------------+----------------------------------------------+--------+------|
| | | topic | 1:17 | |
| | [2021-01-29 Fri 18:22] | \_ test | | 0:01 |
| [2021-01-20 Wed 10:45] | [2021-01-29 Fri 18:26] | \_ WIP Troubleshoot Cylance/3503 issue | | 1:11 |
| <2021-02-26 Fri 09:00 ++1w> | | \_ WIP [#B] Create Deploy & Environments... | | 0:05 |
|-----------------------------+------------------------+----------------------------------------------+--------+------|
|-----------------------------+------------------------+----------------------------------------------+--------+------|
#+END:
* topic
** DONE test
CLOSED: [2021-01-29 Fri 18:22]
CLOCK: [2021-01-29 Fri 18:21]--[2021-01-29 Fri 18:22] => 0:00
** DONE WIP Troubleshoot Cylance/3503 issue :MBE:
CLOSED: [2021-01-29 Fri 18:26]
:PROPERTIES:
:CREATED: <2021-01-20 Wed 10:46>
:END:
:LOGBOOK:
CLOCK: [2021-01-20 Wed 09:35]--[2021-01-20 Wed 10:46] => 1:11
:END:
[2021-01-20 Wed 10:45] - <snip log entry>.
** TODO WIP [#B] Create Deploy & Environments Meeting Agenda
SCHEDULED: <2021-02-26 Fri 09:00 ++1w>
- State "DONE" from "TODO" [2021-01-30 Sat 10:56]
:PROPERTIES:
:LAST_REPEAT: [2021-01-30 Sat 10:56]
:EFFORT: 0:15
:END:
:LOGBOOK:
CLOCK: [2021-01-20 Wed 08:42]--[2021-01-20 Wed 08:47] => 0:05
<snip>
CLOCK: [2020-07-14 Tue 16:17]--[2020-07-14 Tue 16:39] => 0:22
:END:
It's up to you if you want to take out the :timestamp t setting if adding the new "CLOSED" column.
A downside, though, with the "CLOSED" column is that I haven't found an approach that allows for scheduled tasks (that have been periodically completed) to also be shown with a date-time-stamp in the "CLOSED" column. It looks like the "SCHEDULED" setting is shown in the "Timestamp" column, but that might not be what you want.
I hope this information helps!

Related

Bootup/Startup Script Not Working for nVidia GPU Clock Offset

Trying to change GPU Graphics and Memory Transfer Rate Clock Offset on my nVidia EVGA 1030 SC on bootup. I am a linux noob here using Rocky Linux 9.
Question:
How do I check my current set values for GPUGraphicsClockOffsetAllPerformanceLevels and GPUMemoryTransferRateOffsetAllPerformanceLevels?
Currently I am checking by starting up nVidia X Server then look for the values in Graphics Clock Offset and Memory Transfer Rate Offset under the PowerMizer tab. Is there a better way? I don't even really know if that is always up to date...
What did I do wrong and what do I need to change to fix my bootup script below to work?
I think my bootup script is NOT working because the PowerMizer in nVidia X Server does NOT show clock offset values of 50MHz and 200MHz for Graphics and Memory Transfer Rates, respectively, when I boot with my script. It only shows 0 and 0.
However, it does show 50MHz and 200MHz when I enter the following 3 commands line after line directly in bash terminal.
nvidia-smi -pm 1
nvidia-settings -a [gpu:0]/"GPUGraphicsClockOffsetAllPerformanceLevels=50"
nvidia-settings -a [gpu:0]/"GPUMemoryTransferRateOffsetAllPerformanceLevels=200"
Below is the bootup script...
i.
Wrote a shell script file named nVidiaStartUp.sh and placed it in: /etc/rc.d/init.d
nVidiaStartUp.sh contains
#!/bin/bash
nvidia-smi -pm 1
nvidia-settings -a [gpu:0]/"GPUGraphicsClockOffsetAllPerformanceLevels=50"
nvidia-settings -a [gpu:0]/"GPUMemoryTransferRateOffsetAllPerformanceLevels=200"
ii.
In Terminal, executed chmod +x /etc/rc.d/init.d/nVidiaStartUp.sh
iii.
Added a script named nVidiaStartUp.service in /etc/systemd/system with contents below
[Unit]
Description=nVidia Startup Script Call with Undervolt
After=getty.target
[Service]
Type=simple
ExecStart=/etc/rc.d/init.d/nVidiaStartUp.sh
TimeoutStartSec=0
#RemainAfterExit=yes
[Install]
WantedBy=default.target
#WantedBy=graphical.target
#WantedBy=multi-user.target
iv.
Ran in terminal
systemctl enable nVidiaStartUp.service
v.
Reboot and then I check my clockoffset under PowerMizer in nVidia X Server. I don't see 50MHz and 200MHz. I only see 0 and 0. That seems to imply my bootup script isn't working? Please help!
======================================================================================================================================================
Additional background info:
I have installed nVidia driver and it loads with proper GPU information. Here is what it shows after running nvidia-smi
Fri Nov 4 11:39:36 2022
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 520.61.05 Driver Version: 520.61.05 CUDA Version: 11.8 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|===============================+======================+======================|
| 0 NVIDIA GeForce ... On | 00000000:0B:00.0 On | N/A |
| 48% 50C P0 N/A / 30W | 373MiB / 2048MiB | 0% Default |
| | | N/A |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=============================================================================|
| 0 N/A N/A 2309 G /usr/libexec/Xorg 100MiB |
| 0 N/A N/A 2439 G /usr/bin/gnome-shell 139MiB |
| 0 N/A N/A 3270 G ...470561649073451082,131072 130MiB |
+-----------------------------------------------------------------------------+
My relevant sections for Cool-bits (I am using 8 for cool-bits as this card is passively cooled) of my /etc/X11/xorg.conf shows
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "NVIDIA GeForce GT 1030"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "Coolbits" "8"
SubSection "Display"
Depth 24
EndSubSection
EndSection

horizontal rule doesn't align with each column in orgmode

I want to create a table on emacs orgmode, but table horizontal rule doesn't align with the column.(by the way, i'm using spacemacs 26).
Step1:
input "| Week Starting | Mon | Tues | Wed | Thurs | Fri | Sat | Sun |"
Step2:
input "|-" and then press "return"

HG Merge: Outstanding uncommited changes

I have a file, version.txt and other files. I changed the other files, but didn't touch version.txt.
So, I've tried to push a commit, and saw a Remote heads error. (There is a changeset which modifies versions.txt file)
I did a hg pull, then hg update.
The error is: abort: crosses branches (merge branches or use --clean to discard changes)
Then I tried hg merge: abort: outstanding uncommitted changes (use 'hg status' to list changes)
But I don't undertand, why if the versions.txt isn't modified by me, why can't it just merge.
This is something I will be doing a lot, which is, develop and merge, to keep inline with the main dev repo. How can I fix this thing?
HG Status:
M printbox/web/printbox/controllers/ct_adm_colas.php
M printbox/web/printbox/controllers/ct_adm_jobs.php
M printbox/web/printbox/controllers/ct_form_configurar_cola.php
M printbox/web/printbox/core/MY_Controller.php
M printbox/web/printbox/css/estilos.css
M printbox/web/printbox/js/js_tablas_colas-jobs_ajax.js
M printbox/web/printbox/models/md_cola.php
M printbox/web/printbox/models/md_job.php
M printbox/web/printbox/views/vw_tabla_colas.php
M printbox/web/printbox/views/vw_tabla_jobs.php
A printbox/web/printbox/core/MY_Model.php
? .idea/.name
? .idea/encodings.xml
? .idea/misc.xml
? .idea/modules.xml
? .idea/printboxweb.iml
? .idea/scopes/scope_settings.xml
? .idea/vcs.xml
? .idea/workspace.xml
EIDT: Before and After following the suggested fix, the graph log looks like this:
o changeset: 19:e21fa7b131b0
| tag: tip
| parent: 17:54f59f253460
| user: JCV
| date: Tue Apr 22 12:33:36 2014 -0300
| summary: # Modificar nombre de producto para version
|
| # changeset: 18:a03eaad764cd
|/ user: Jorge S <js#fusiondev.com.ar>
| date: Wed Apr 23 16:28:01 2014 -0300
| summary: Eliminar método que no se utiliza.
|
o changeset: 17:54f59f253460
| user: Jorge S <js#fusiondev.com.ar>
| date: Mon Apr 21 17:25:23 2014 -0300
| summary: Incluir SWHelper en Printbox.php
|
# changeset: 21:1698791a9310
|\ tag: tip
| | parent: 20:3bfa1251da1b
| | parent: 19:e21fa7b131b0
| | user: Jorge S <js#fusiondev.c
| | date: Thu Apr 24 13:59:25 2014 -0300
| | summary: Merge
| |
| o changeset: 20:3bfa1251da1b
| | parent: 18:a03eaad764cd
| | user: Jorge S <js#fusiondev.c
| | date: Thu Apr 24 13:57:23 2014 -0300
| | summary: Commit de archivos
| |
o | changeset: 19:e21fa7b131b0
| | parent: 17:54f59f253460
| | user: JCV
| | date: Tue Apr 22 12:33:36 2014 -0300
| | summary: # Modificar nombre de producto
| |
| o changeset: 18:a03eaad764cd
|/ user: Jorge S <js#fusiondev.c
| date: Wed Apr 23 16:28:01 2014 -0300
| summary: Eliminar método que no se utili
|
o changeset: 17:54f59f253460
| user: Jorge S <js#fusiondev.com
| date: Mon Apr 21 17:25:23 2014 -0300
| summary: Incluir SWHelper en Printbox.php
Ok, forget about version.txt, it is not relevant here. You have 2 repos, one on your system, and the remote one.
When you tried to push the first time, you tried to send a changeset on the remote repo, and you got an error saying that you cannot push a second head, unless you issue a --force option. This is because someone else already beat you to it and pushed a changeset (modifying version.txt) on the same branch (what you call main line, is actually a branch too, and it is probably called default).
What you did next is good, you pulled the changes from the remote repo to solve the 2 heads problem. By doing so, you are the one ending up with 2 heads on the default. This is fine, it is easy to solve, we'll get to it soon.
Your current state must look like this
% hg log --graph
o changeset: 14:3cfac6413110
| tag: tip
| parent: 10:d573f47ecc2d
| summary: vb
|
| # changeset: 13:d8edfdb0532e
|/ parent: 10:d573f47ecc2d
| summary: commit to subr2
|
Now it gets complicated when you do the hg update because mercurial notices that something is wrong with your repo. You will need to fix the 2 heads issue by doing a merge, just like mercurial's suggestion.
However, doing hg merge gives you a second error, this time because you have not committed all your changes in your repo. Now you have 2 choices. You see those files with the M in front of them when you tried the hg status command? If you indeed modified them, and you want to include them in the repo, do the following:
hg commit -m "Committing remaining files"
hg merge
hg commit -m "Merge"
This is to commit the left-over changes, merge the 2 heads, then commit the merge changeset. The reason why mercurial does not want to update with uncommitted changes is for security reasons. It does not want you to loose you current work. And this brings me to the second option. If, however, the changes in the modified files are not wanted, you can discard those changes. It is possible you attempted something else during the confusion, which updated some files and left you in an in-between state. If that is the case, you can quickly discard the changes and solve the problem by doing these commands instead (loosing your changes):
hg update --clean
hg merge
hg commit -m "Merge"
The update will simply clean out the repo, and a merge will be possible. Once the merge committed, then you can issue the final push.
hg push
If you're lucky and no one pushed anything else on the remote repo, the push should succeed. Otherwise, you can pull, merge, commit and push again.

Why via manual impex import I have a good result but if I invoke update I haven't result

I notice that if I invoke any impex files manually(console -> impex import) - it is working. But if I make update system, I haven't success. In the log I see that this file mentions. Am I misunderstanding this situation?
log:
INFO | jvm 1 | main | 2013/12/09 12:44:41.633 | INFO [hybrisHTTP26] [AbstractSystemSetup] Begin SOLR index setup [hybris]
INFO | jvm 1 | main | 2013/12/09 12:44:41.634 | INFO [hybrisHTTP26] [DefaultSetupImpexService] Importing [/merchandisecore/import/stores/hybris/solr.impex]...
INFO | jvm 1 | main | 2013/12/09 12:44:41.635 | INFO [hybrisHTTP26] [DefaultImportService] Starting import synchronous using cronjob with code=000000SL
INFO | jvm 1 | main | 2013/12/09 12:44:41.637 | INFO [hybrisHTTP26] (000000SL) [ImpExImportJob] Starting ImpEx cronjob "ImpEx-Import"
INFO | jvm 1 | main | 2013/12/09 12:44:41.638 | WARN [hybrisHTTP26] (000000SL) [HeaderDescriptor] line 28 at main script: column mode of type SolrServerConfig is not writable, but you want to update it. If you want to write this non writable attribute explicit, you have to use the forceWrite=true modifier. This warning is printed only once for header. Please check subsequent lines for similar problem.
INFO | jvm 1 | main | 2013/12/09 12:44:41.752 | WARN [hybrisHTTP26] (000000SL) [HeaderDescriptor] line 125 at main script: column type of type SolrIndexerQuery is not writable, but you want to update it. If you want to write this non writable attribute explicit, you have to use the forceWrite=true modifier. This warning is printed only once for header. Please check subsequent lines for similar problem.
INFO | jvm 1 | main | 2013/12/09 12:44:41.757 | INFO [hybrisHTTP26] (000000SL) [Importer] Finished 1 pass in 0d 00h:00m:00s:098ms - processed: 73, dumped: 3 (last pass: 0)
INFO | jvm 1 | main | 2013/12/09 12:44:41.860 | INFO [hybrisHTTP26] (000000SL) [Importer] Starting pass 2
INFO | jvm 1 | main | 2013/12/09 12:44:41.860 | INFO [hybrisHTTP26] (000000SL) [Importer] Finished 2 pass in 0d 00h:00m:00s:006ms - processed: 3, no lines dumped (last pass 3)
INFO | jvm 1 | main | 2013/12/09 12:44:41.862 | INFO [hybrisHTTP26] [DefaultImportService] Import was successful (using cronjob with code=000000SL)
INFO | jvm 1 | main | 2013/12/09 12:44:41.963 | INFO [hybrisHTTP26] [DefaultSetupImpexService] Importing [/merchandisecore/import/stores/hybris/solr_en.impex]...
As you can see, there are some columns on the type you're trying to update which need add the forceWrite=true on the impex header.
Some attributes are not writables once they are created.
I do not know how the impex you're trying to execute are,but I would try to delete the item, and then check if the impex is executed correctly on the update (but do not execute the impex first on the hac import impex).

PostgreSQL Transaction ID went backwards

In PostgreSQL 9.0, I have a table that keeps tracks of last processed transactions. For some reason, it went backwards (in time)! Here is the table data:
seq_id | tx_id
628 | 10112
629 | 10118
630 | 10124
631 | 10130
632 | 10136
654 | 10160
655 | 10166 <---
656 | 4070 <---
657 | 4071
658 | 4084
659 | 4090
660 | 4096
How can this happen? Can a restart of the database induce such behavior?
Thanks for any hints.
Regards,
D.
This is an invalid issue. Please ignore.
It turns out that the issue came out of restoring the table from a backup and continue working with (invalid) previous data, in a newly created database :-(
Thanks you for all those who responded already.
Case closed.
Lesson learned: TXID will NOT go backwards and they do get synced to a slave instance if you're using a Master/Slave setup. TXID rollovers are also correctly handled. Hope this will help others who might be thinking TXID can go backwards!