u/vivekkhera

I have a one-shot prompt that takes an interview transcript and makes a summary of it for further use. I use structured output mode in the API to include some metadata. Today the output from one of the runs of this workflow output exactly this:

{
"content": "# Your Edited Text May Now Carry an AI Watermark",
"content_use_case": "interview_summary"
}

The actual result was nowhere to be found. Opus-5 with medium effort thinking.

Any suggestions how to make it just give me the result? I find no documentation on a way to tell the API I understand it will watermark so it doesn't have to remind me.

Updating ports today, and it asked me to delete postfix-sasl (I see now it is because lmbb0 was replaced with lmdb). I figured I'd just install it back afterwards. Apparently I cannot because lmdb and lmdb0 conflict with one another. Sigh. FreeBSD 14.4-RELEASE-p8 amd64.

The following 4 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
lmdb0: 0.9.35 [FreeBSD]
postfix-sasl: 3.11.5_1,1 [FreeBSD]

Installed packages to be REMOVED:
lmdb: 1.0.0,1
samba423: 4.23.11

Number of packages to be removed: 2
Number of packages to be installed: 2

I share a list for shopping and use the tags to indicate which store to get the item. The tags do not share across to the other people. I’m using the tags from the tag menu, not adding hashtags to the title of the reminder.

Is there any setting I’m not seeing that will enable the sharing over iCloud?

I was just at an EA fast charger that I use regularly. My car is set to stop at 90%, but tonight it just kept going. The dashboard showed 1 minute left, even after it got up to 94% when I manually stopped it. I was curious how far the car would go until it requested a stop. This has never happened to me before. Has anyone else seen this with their GV60?

Every time that gitea port gets upgraded and I restart, it always fails to actually start and shows no warnings:

[root@thneed]~# service gitea restart
Stopping gitea.
Waiting for PIDS: 91883.
gitea already running?  (pid=91883).
[root@thneed]~# service gitea status
gitea is not running.
[root@thneed]~# service gitea start
[root@thneed]~# service gitea status
gitea is running as pid 2673.

The rc script seems reasonable, but clearly it needs to wait for something else before it should attempt the restart.

Does this happen to anyone else?

Running OPNsense 26.1.6_2 (amd64) on a Protectli FW4B.

I have the thermal setting configured to use Intel coretemp kernel module. The numbers on the dashboard disagree with the numbers from the sysctl output.

Right now on the dashboard, it shows 5 numbers:

CPU 0: 47 C

CPU 1: 47 C

CPU 2: 41 C

CPU 3: 39 C

Zone 0: 26.9C

Yet from the CLI at about the same time I see

% sysctl dev.cpu.{0,1,2,3}.temperature hw.acpi.thermal.tz0.temperature

dev.cpu.0.temperature: 40.0C

dev.cpu.1.temperature: 40.0C

dev.cpu.2.temperature: 38.0C

dev.cpu.3.temperature: 36.0C

hw.acpi.thermal.tz0.temperature: 26.9C

Why don't the CPU temperatures align? That's a significant difference. Is the dashboard picking the numbers from a different place? The CPU 0 temps are regularly (but not always) +7 and the CPU 2 are +3 on the dashboard.