Fediver

重複のある特定のキーから重複を除いたキーごとになんちゃらかんちゃら的なのものもMAPとLAMBDAで表現できる

=MAP(
  UNIQUE(テーブル[hoge]),
  LAMBDA(
    key, 
    COUNTA(UNIQUE(FILTER(テーブル[fuga], テーブル[hoge]=key)))
  )
)

unique_ptrがOption<Box<T>>で悲しい

CFのUnique Visitorsって何を表してるんだろう。何もコンテンツがないドメインで3k/30dayとかあるんだけど何？

[Auto Note]:Updated
Fetch URL: https://github.com/misskey-dev/misskey
Commit: 607bf600 to 2f8d0202
feat(frontend): 画像を投稿前にプレビュー可能に (#15341)
enhance(frontend): クライアントエラー画面の多言語対応 (#15411)
fix(dev): devcontainerのcorepackのバージョンを指定するように (#15415)
fix(backend): use unique operationId in the OpenAPI schema (#15420)
fix(ci): oktetoの導線を削除 (#15427)
chore: update .swcrc schema link (#15428)

#みーくりあ！UpdateLog

そして制約が欠けてる、、、
以上が起きてるdb↓

misskey=# \d "__chart_day__per_user_notes"
                                         Table "public.__chart_day__per_user_notes"
      Column       |          Type          | Collation | Nullable |                         Default                         
-------------------+------------------------+-----------+----------+---------------------------------------------------------
 id                | integer                |           | not null | nextval('__chart_day__per_user_notes_id_seq'::regclass)
 date              | integer                |           | not null | 
 group             | character varying(128) |           | not null | 
 ___total          | integer                |           | not null | '0'::bigint
 ___inc            | smallint               |           | not null | '0'::bigint
 ___dec            | smallint               |           | not null | '0'::bigint
 ___diffs_normal   | smallint               |           | not null | '0'::bigint
 ___diffs_reply    | smallint               |           | not null | '0'::bigint
 ___diffs_renote   | smallint               |           | not null | '0'::bigint
 ___diffs_withFile | smallint               |           | not null | '0'::smallint
Indexes:
    "PK_58bab6b6d3ad9310cbc7460fd28" PRIMARY KEY, btree (id)

misskey=#  \d "__chart_day__per_user_notes"
                                         Table "public.__chart_day__per_user_notes"
      Column       |          Type          | Collation | Nullable |                         Default                         
-------------------+------------------------+-----------+----------+---------------------------------------------------------
 id                | integer                |           | not null | nextval('__chart_day__per_user_notes_id_seq'::regclass)
 date              | integer                |           | not null | 
 group             | character varying(128) |           | not null | 
 ___total          | integer                |           | not null | '0'::bigint
 ___inc            | smallint               |           | not null | '0'::bigint
 ___dec            | smallint               |           | not null | '0'::bigint
 ___diffs_normal   | smallint               |           | not null | '0'::bigint
 ___diffs_reply    | smallint               |           | not null | '0'::bigint
 ___diffs_renote   | smallint               |           | not null | '0'::bigint
 ___diffs_withFile | smallint               |           | not null | '0'::smallint
Indexes:
    "PK_58bab6b6d3ad9310cbc7460fd28" PRIMARY KEY, btree (id)
    "IDX_c5545d4b31cdc684034e33b81c" UNIQUE, btree (date, "group")
    "UQ_c5545d4b31cdc684034e33b81c3" UNIQUE CONSTRAINT, btree (date, "group")

このエラーの対処法わかる人います？
ちなみにdbにはそもそも<ユーザー名>のレコードはないのと、https://mastodon.social/users/<ユーザー名>でアクセスするとそのページは存在しないと言われる
くわえて現時点でmastodon.social上のユーザーしかこのエラーに引っかからない

db-1  | 2024-11-10 04:08:44.413 UTC [114373] ERROR:  duplicate key value violates unique constraint "IDX_171e64971c780ebd23fae140bb"
db-1  | 2024-11-10 04:08:44.413 UTC [114373] DETAIL:  Key ("keyId")=(https://mastodon.social/users/<ユーザー名>#main-key) already exists.
db-1  | 2024-11-10 04:08:44.413 UTC [114373] STATEMENT:  INSERT INTO "user_publickey"("userId", "keyId", "keyPem") VALUES ($1, $2, $3)

負荷がめちゃくちゃ高くなったあとのログ

db-1  | 2024-09-17 13:04:22.505 UTC [23786] ERROR:  duplicate key value violates unique constraint hogehoge

結局元記事ってこれが言いたかったんじゃないのという

I should point out that, of course, this could come under the broader remit of forwarding email to an incorrect email address, a typo, and as such applies to any email platform rather than being an underlying Gmail security issue. Better still, just don’t do it at all. Apple users can make use of the Hide My Email which generates unique, random email addresses that are forwarded automatically to your personal inbox. My preferred email client, Proton Mail, also has a hide-my-email alias feature that works in the same way.