Pinned Tweet
【登壇資料を公開しました】
本日の「#bq_sushi #19 bq_sushi今年はがんばるぞい!」にて登壇し発表資料を公開しました。ご興味がある方はぜひご覧ください!
speakerdeck.com/monotaro/big…
#bq_sushi
見てる: "ソフトウェアダークファクトリー | 技術評論社" gihyo.jp/book/2026/978-4-297…
Nakamura Masato retweeted
ソフトウェア開発で「やったほうがいいけど人間がやるには手間が多すぎる」ことがエージェントのおかげでやり方すら知らなくても片付けられるようになったわけだけど、そもそも何をやったほうがいいのか、それはなぜかを考えるのは、まだしばらくは人間の責務であるように思われる
Nakamura Masato retweeted
【🌸お知らせ🌸】
#さくらのAIEngine で
「GLM-5.3-Flash」
「DeepSeek-V4.1-Flash-1017」
のパブリックプレビューを開始しました❗️
🔹画像も扱えるマルチモーダルモデル
🔹Chat Completions APIに対応
🔹月3,000リクエストまで無償
▽詳細
cloud.sakura.ad.jp/news/2026…
Nakamura Masato retweeted
🧩NVIDIA introduced a 512GB desktop AI cluster designed to run models with up to 70B parameters locally - no switch needed.
And you don't need a traditional GPU server rack.
This is NVIDIA's new DGX Spark HPC Developer Kit.
Announced at SC26.
It's 4x DGX Sparks connected in a ring.
Each Spark has ...
🟢 NVIDIA GB10 Grace Blackwell
💾 128GB unified memory
⚡ Up to 1 PFLOP FP4 AI compute
🔗 ConnectX-7 networking
💻 20-core ARM CPU
Now connect four of them.
Combined hardware ...
🔥 512GB aggregate memory
🔥 4× GB10 Blackwell Superchips
🔥 Up to 4 PFLOPS theoretical FP4 compute
🔗 200Gb/s per ConnectX-7 port
🔌 Four direct interconnect cables
🎯 No Network switch required for NVIDIA's new four-node ring configuration.
NVIDIA says the cluster can deploy models up to 700B parameters using NVFP4 precision.
Including models such as DeepSeek V4.1.
Locally. On your desk. 👀
NVIDIA is positioning this for scientific computing, not just LLM inference.
The company also highlights UC Berkeley researchers LoRA fine-tuning a 120B-class Nemotron model on ONE DGX Spark.
💰 What's the complete kit price?
⚡ How many tokens/sec on a 700B model?
🧠 How well does the four-node ring scale?
🔧 When does the new HPC setup playbook arrive?
The kit is listed for sale, but a public bundle price and 700B inference benchmarks weren't included in the announcement.
And the standard NVIDIA Sync documentation still requires a switch for four-node setup, so this new ring configuration deserves a closer look to clarify by NVIDIA
Nakamura Masato retweeted
Orca使ってる人は全員読んでくれ!!
って感じの記事を書きました
zenn.dev/andoshin11/articles…
Nakamura Masato retweeted
最高にロックな文章だった。 “デザインの第一印象を後から覆すのは非常に難しい。人間関係と同じだ。人間はあらゆるものの第一印象に支配されていて、デザインもその例外ではない。” / “デザインハーネスという虚像 - takanorip blog” htn.to/229NwVTkqD
Nakamura Masato retweeted
I used AI and somehow built a JavaScript engine in just 2–3 days.
* Pure Go
* `unsafe`-free
* ES2025 support (99.99% of Test262 tests pass)
* Over 3× faster than goja and Sobek
* Over 2× faster than cznic's Go port of QuickJS
#golang
github.com/hajimehoshi/ekuma
Nakamura Masato retweeted
More details on the root cause can be found in the Microsoft 365 Admin center, and an abridged version can be found below.
We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations.
The incident on Thursday, November 12th, 2026, was caused by three main factors that together caused a global outage for the networking gateway that fronts many Microsoft 365 services.
First, a latent defect caused servers to become overwhelmed and unresponsive under certain load conditions. This was due to lock contention inside an internal process which caused the machine to become unavailable. This defect was the result of a fix that was prepared specifically for Microsoft 365 networking gateway servers; neither the underlying defect nor the fix applies to broader Windows deployments.
The initial change in behavior first started deployment in July of this year. The update went through safe deployment and saturated globally over several weeks, during which time no issues were observed. For more than three months, the change was deployed worldwide without impact.
Our normal load testing did not detect the latent issue because the different traffic and SKU mix used in our test labs. The contention issue is worsened on machines with more cores and newer hardware; whereas our load testing tended to focus on our weaker hardware SKUs with fewer cores.
Second, a surge in load increased the likelihood for the networking gateways to encounter the contention. Within Microsoft 365, we maintain two independent and heterogenous network gateway systems designed for isolation and high availability. This allows many Microsoft 365 services to fail to/from them during outages or disruptions. Approximately fifteen hours before the outage, Teams failed over from the alternative networking gateway to the ‘primary’ gateway that also supports Exchange Online. This increased the load on the networking gateway and changed its traffic patterns. This type of failover is part of normal operations and is integral to standard Microsoft resiliency efforts.
Third, at the same time, nearly 14% of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day. This server capacity was on track to be returned to active service through routine maintenance and health processes. The service had sufficient capacity headroom, so the reduction in server capacity had no impact on its own.
Taken together, the increased load and the reduced server capacity, caused the network gateway to encounter the latent bug from July. This caused requests to build up until servers ultimately stopped responding. This occurred during the peak window of traffic in the United States.
When servers lose connectivity, our traffic management systems automatically route users to other healthy endpoints. This happens often and is critical to avoiding any interruption due to hardware, software, or network defects and is normally what makes the service resilient. However, the redirected traffic increased the likelihood for the same problem to occur on the remaining endpoints. This caused a cascading failure from server to server as the same amount of load was spread across fewer servers. In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive. At its lowest, more than 80% of servers were unresponsive.
Normally, the network gateway is composed of thousands of ‘capacity units’ which represent shards of capacity, hardware, and networking infrastructure. These ‘capacity units’ are then organized into regions. In this case, due to a separate issue, the normal bulkheads between these different partitions did not stop the cascading failure. This is what allowed the impact to spread across our network gateway infrastructure globally.
Several services like Teams, OneDrive, SharePoint, and Office apps failed out of the faulty network gateway infrastructure. That is why those services were restored earlier, with Teams chats and meetings functioning without issue for most of the outage. But not all services, like Exchange Online, can fail out of this network gateway.
Recovery took longer than usual because as servers returned to service, they were immediately overwhelmed by waiting traffic and became unresponsive again. Our normally automated recovery processes were not designed to restore service from this broad unresponsive state. Additionally, since the main code defect was a latent bug from several months previous, our normal rollback, flighting, and feature flags were unable to quickly revert the change.
After engineers confirmed the defect as the cause, we developed an update that returned the code path to the previously known good state. To effectively apply this fix, and to slowly bring the service online again, we took groups of servers out of service, applied the change, and restarted them before returning them to service. This process was carefully applied to large quantities of infrastructure at a time (e.g. 50%+ of a region).
The final Post-Incident Review (PIR) will provide more details later this week.
Replying to @MSFT365Status
We have released the Preliminary Post-Incident Report of last week’s outage, which is accessible via the Admin center under MO1550821 and EX1550543.
Apple containerにkubernetes きてるやん!
github.com/apple/container/b…
mariadb.com/docs/server/serv… はー mariadbって trigger update of column対応してるんだ。 mysqlでは対応してないのでmariadbでも対応してないと思ってたー。
1
1
117
jira.mariadb.org/browse/MDEV… そしてこんな不具合があることがわかった。mariamem作らなければこんなん知らなかったな
65
Nakamura Masato retweeted
OpenAI、これガチで公開して良いんかw
公式が御用達のCodexを動かす中核
「Harness」がオープンソースで公開された‼️
CLI・SDK・App Serverに加えて、
Skillsやクラウド用のベース実行環境まで
公開されています。
・AIにどうツールを使わせるか
・作業の文脈をどう引き継ぐか
・実行できる範囲をどう制御するか
こういうエージェントの設計を
実際のコードから学べるのが大きい。
自分のAI社員や業務自動化エージェントを
作りたい人には、かなりありがたい教材。
これは保存しておきたい。
github.com/openai/codex














