asyncio.run() and create_task() fail on Feather Bluefruit Sense (nRF52840) with TaskQueue push_head error

[muhammadawais92]

When running any code that uses asyncio.run() or asyncio.create_task() on the Adafruit Feather Bluefruit Sense (nRF52840), the program fails with the following error:
Traceback (most recent call last):
File "code.py", line XX, in
File "/lib/asyncio/core.py", line XXX, in run
File "/lib/asyncio/core.py", line XXX, in create_task
AttributeError: 'TaskQueue' object has no attribute 'push_head'

Steps to reproduce:

1. Use Feather Bluefruit Sense (nRF52840) with CircuitPython 10.x.
2. Install adafruit_asyncio from the Adafruit bundle.
3. Run a minimal asyncio script such as:

import asyncio
async def main():
    while True:
        print("Hello")
        await asyncio.sleep(0.5)
asyncio.run(main())

Expected behavior:

• The coroutine should run, printing “Hello” every 0.5 seconds.

Observed behavior:

• The program crashes immediately with TaskQueue push_head AttributeError.

Additional context:

• This appears to be a hardware/library limitation.
• Using a single while loop without asyncio.run() works as a workaround.

Environment:

Board: Feather Bluefruit Sense (nRF52840)

• CircuitPython: 10.x
• adafruit_asyncio version: latest bundle

Workaround:

• Use a normal while loop or a single async function without create_task() or asyncio.run().

[dhalbert]

I could not duplicate this with 10.0.x and the latest asyncio library. push_head() and some other operations were removed in #71, and are not in the library at all anymore.

I think the asyncio library on your board may not be completely updated, or there may be two copies of the library , perhaps one in CIRCUITPY and one in /lib, or maybe pieces of an old version of the library. For instance, .py files override .mpy files, so if both are in the asyncio library, and one is old, you may get the problem you saw. Could you check for that? Maybe do import storage; storage.erase_filesystem() if you want to get a fresh start on the board.

[muhammadawais92]

Thank you for your response.
You are correct; there were some file conflicts on my board. Certain files were overriding others, and some components were outdated. I have resolved these conflicts and updated the outdated files. The board is now functioning correctly.

[dhalbert]

Great! Closing.