feedback on incorrect operation

オープン
  • 何か問題がありますか？
#62,735 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
バグ
明瞭さ
説明が足りない
活発さ
活発
技術スタック
typescript
領域
ai-infra-agents

調査の方向性

Start by reading the issue thread for details about the reported token usage and any response from maintainers. The report does not identify a specific feature, file, or test to investigate; first trace how the service measures and displays token consumption. Done means identifying and addressing the cause of unexpectedly high usage and making token consumption clear to users.

索引モデルが issue の本文から書いたものです。

説明

triaging

Before the news about the DDoS attack on OpenCode, token usage was completely normal. The limits were being consumed at a reasonable rate, and the service was perfectly usable.

However, after the attack, OpenCode has become practically unusable. Now, even sending a very simple request, such as “hello”, can result in the available limit being almost completely exhausted. This was not happening before.

It really feels like something changed in the way token usage is calculated, or that additional restrictions were introduced after the DDoS attack, and they are now affecting regular users far too heavily.

I really hope the developers look into this. If these changes are indeed related to the aftermath of the attack or the measures introduced to prevent similar incidents, the token limits need to be handled much more reasonably. It would also be helpful to clearly show users exactly what is consuming their tokens.

Right now, the situation is extremely frustrating: you can send one simple request, and suddenly most or all of your available limit is gone. In its current state, the service is simply too difficult to use for any meaningful work.

主要言語
TypeScript
スター
225k
フォーク
30.4k
平均マージ
4時間 16分
マージ済み PR（30日）
528

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

anomalyco/opencode のほかの issue

anomalyco/opencode の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。