Allow pueue status to order tasks by enqueue_at

[pacien]

pueue status order_by enqueue_at [asc/desc]
does not appear to order tasks as requested.

Minimal non-working example:

❯ pueue add --delay 2024-07-21 echo hi
New task added (id 0). It will be enqueued at 2024-07-21 00:00:00

❯ pueue add --delay 2024-07-22 echo hi
New task added (id 1). It will be enqueued at 2024-07-22 00:00:00

❯ pueue add --delay 2024-07-21 echo hi
New task added (id 2). It will be enqueued at 2024-07-21 00:00:00

❯ pueue status order_by enqueue_at
Group "default" (1 parallel): running
───────────────────────────────────────────────────────────────
 Id   Status    Enqueue At   Command   Path        Start   End 
═══════════════════════════════════════════════════════════════
 2    Stashed   00:00:00     echo hi   /home/user               
───────────────────────────────────────────────────────────────
 1    Stashed   2024-07-22   echo hi   /home/user               
                00:00:00                                       
───────────────────────────────────────────────────────────────
 0    Stashed   00:00:00     echo hi   /home/user               
───────────────────────────────────────────────────────────────

❯ pueue status order_by enqueue_at desc
Group "default" (1 parallel): running
───────────────────────────────────────────────────────────────
 Id   Status    Enqueue At   Command   Path        Start   End 
═══════════════════════════════════════════════════════════════
 0    Stashed   00:00:00     echo hi   /home/user               
───────────────────────────────────────────────────────────────
 1    Stashed   2024-07-22   echo hi   /home/user               
                00:00:00                                       
───────────────────────────────────────────────────────────────
 2    Stashed   00:00:00     echo hi   /home/user               
───────────────────────────────────────────────────────────────

Expected output:
task ID 1 shouldn't be in-between in either cases.

Platform info:

• pueue 3.4.0
• NixOS 24.05 (GNU/Linux 6.6.32, x86_64)

[Nukesor]

Feel free to implement this :) Please add proper tests as well.

Also: Please don't mark missing features as bugs.
A bug is something that doesn't work as intended. If you're missing some functionality that doesn't exist yet, it's a feature request.

[pacien]

Hi!

Feel free to implement this :) Please add proper tests as well.

I'll try to submit some changeset for this.

Also: Please don't mark missing features as bugs. A bug is something that
doesn't work as intended. If you're missing some functionality that doesn't
exist yet, it's a feature request.

The help text of the pueue status sub-command indicates that enqueue_at
is a possible order to give to the order_by clause.

The query is indeed accepted without any error or warning,
producing some unexpected effect, even more so with asc/desc.
So that looks like a bug from my point of view of user.

Perhaps the grammar could be tightened, so that the order_by clause only
accepts a subset of columns, similarly to what's being done for the filter
clause with filter_column?

[Nukesor]

You're right, I completely forgot about those docs as I didn't write them myself. Sorry for that.

Yep, according to the docs, enqueue_at should be possible to be ordered by. Should be fairly straight forward to add it to https://github.com/Nukesor/pueue/blob/main/pueue/src/client/query/mod.rs#L65

I would wait for #556 to be merged first though, as this changes quite a lot of stuff.

[Nukesor]

#556 is merged :D