Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Windows: BLE workflow serial notifications are delivered twice

オープン
#11,212 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

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

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

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
35/100
issue の種類
バグ
明瞭さ
説明が足りない
活発さ
静か
技術スタック
javascript, python
領域
embedded-iot

調査の方向性

Start by tracing connectToSerial() and its notification subscription path in the web editor. Compare whether notifications are duplicated on air or only after reaching the editor, using a BLE trace if available; check first connections and reconnects on Windows. Done means the source of the duplicate delivery is identified and the terminal no longer shows each notification twice.

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

説明

ble workflow

Claude wrote this:

Over the BLE workflow serial connection from Chrome on Windows, every notification arrives twice. Consistently, not intermittently. The same board and the same firmware do not show it from Chrome on macOS.

Not investigated beyond the observation, so the cause could be anywhere: the peripheral sending twice, the Windows BLE stack delivering twice, or the editor subscribing twice.

What is known

  • Seen on Chrome on Windows; not reproduced on macOS with the same board and build.
  • The board was a Feather nRF52840 Express running CircuitPython 10.3.0-alpha.4.
  • It duplicates the data the user sees in the terminal, so it is user-visible rather than merely wasteful.

Worth checking first

  • Whether the duplication is on air or above it. A sniffer or btmon-equivalent trace would settle immediately whether the peripheral sends one notification or two.
  • Whether the TX characteristic's CCCD gets subscribed twice — connectToSerial() in the web editor removes and re-adds its characteristicvaluechanged listener before calling startNotifications(), so a double subscription is a plausible shape for this.
  • Whether it survives a page reload, and whether it appears on a first connection or only after a reconnect.

Notes

Observed during the three-platform testing behind adafruit/circuitpython#11178, and originally recorded in a comment there that has since been removed because most of its content was superseded. This observation was not, and it is unrelated to that PR's changes.

Also unexplained on Windows, and possibly related: Chrome spins while reading boot_out.txt for the board-information dialog. That one is noted as pre-existing in #11178.

主要言語
C
スター
4.6k
フォーク
1.4k
平均マージ
1日 8時間
マージ済み PR(30日)
153

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

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

adafruit/circuitpython のほかの issue

adafruit/circuitpython の issue をすべて見る

似ている issue

C の issue をもっと見る

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

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