Key event to command palette seems to cancel pending workers?

[otherjason]

I have an app that uses several long-lived workers to asynchronously poll external services for data and update the UI. I found that closing the command palette, either via ESC or by selecting a command, seems to cancel any pending workers. Here's a small example:

import asyncio
from textual import work
from textual.app import App, ComposeResult
from textual.widgets import RichLog

class Test(App):
    CSS = '''
    RichLog {
        height: 100%;
    }
    '''
    def compose(self) -> ComposeResult:
        yield RichLog(id = 'log')

        self.my_worker()

    @work(exclusive = False)
    async def my_worker(self):
        counter = 1

        log = self.query_one('#log')
        while True:
            log.write(f'test {counter}')
            counter += 1
            await asyncio.sleep(1)

if __name__ == "__main__":
    Test().run()

When running the above, it will print a new line to the RichLog every second. If you open the command palette, then the worker stays running. But it seems that after the palette comes up, as soon as I press a key, the worker stops running.

Is this behavior intended, or is this a bug?

[davep]

Is this behavior intended, or is this a bug?

Absolutely isn't intended behaviour.

[davep]

My suspicion would be the use of self.workers.cancel_all() -- I think I thought that self.workers was all the workers on the current screen/widget. Looks like that might need double-checking.

[davep]

Raised as #3615.

[davep]

A fix is in the works: #3618

[davep]

Fixed in 0.41.0.