HackerTrans
トップ新着トレンドコメント過去質問紹介求人

halifaxbeard

no profile record

コメント

halifaxbeard
·11 日前·議論
https://www.priv.gc.ca/en/opc-actions-and-decisions/investig...

Non consensual adult content, at that.

Truly makes me wonder if xAI/Cursor will honour the spirit of enterprise agreements around data retention.
halifaxbeard
·2 か月前·議論
Do children that are the product of sexual assault count?
halifaxbeard
·2 か月前·議論
This is really poor form given that Anthropic is going around getting all kinds of public goodwill for finding CVEs in other people’s products.
halifaxbeard
·2 か月前·議論
> Fixed: HTTP request smuggling attack vector

> Fixed: missing bounds check in maliciously-crafted Blob deserialization

> Fixed: integer overflow in IPC advanced serialization mode with malicious input

Where are the CVEs, Jarred?
halifaxbeard
·2 か月前·議論
Any plans to issue a CVE for this HTTP request smuggling attack vector fixed in the latest bun release?

https://github.com/oven-sh/bun/issues/29732
halifaxbeard
·4 か月前·議論
Wow, I was spoiled building firmware for my ARM boards then (building, not developing).

Marvell has a source available DDR driver that actually takes care of training on a few of their platforms! https://github.com/MarvellEmbeddedProcessors/mv-ddr-marvell
halifaxbeard
·6 か月前·議論
> 8 lets me refresh weekly and have a fixed day of the week to check whether there was some API 429 timeout

There’s your answer.

6 days means on a long enough enough timeframe the load will end up evenly distributed across a week.

8 days would result in things getting hammered on specific days of the week.
halifaxbeard
·8 か月前·議論
At this point I’m not convinced that Gemini 3 Pro was post-trained on data Google had permission to use, going by the myriad of issues on the Gemini CLI tracker around Google AI/Google One/Google Cloud/Google Workspaces.

https://github.com/google-gemini/gemini-cli/issues/12121

It is far too easy to accidentally end up under the wrong privacy agreement, to the point of where some workplaces are banning use of the Gemini CLI!
halifaxbeard
·8 か月前·議論
I think OP is wrong in their hypothesis based on the logs they share and the root cause AWS support provided them.

I think the promotion fails to happen and then an external watchdog notices that it didn’t, and kills everything ASAP as it’s a cluster state mismatch.

The message about the storage subsystem going away is after the other Postgres process was kill -9’d.
halifaxbeard
·8 か月前·議論
How would you propose we address the therapist shortage then?
halifaxbeard
·9 か月前·議論
If the universe is closed and knowable, free will can't exist. Fortunately, Heisenberg left the door open.
halifaxbeard
·10 か月前·議論
unironically, this is such an elegant way to express ray marching

https://github.com/cedardb/DOOMQL/blob/f14b5ef9ef0b23045376b...
halifaxbeard
·11 か月前·議論
the log stays on kafka for replay until your per log retention settings delete it