ExecutionErr: ExitCode: 1, last log lines:
ll/__init__.py", line 1, in <module>
from .client import *
File "/tmp/windmill/cache/pip/wmill==1.338.1/wmill/client.py", line 13, in <module>
from typing import Dict, Any, Union, Literal
File "/tmp/windmill/cache/pip/typing==3.7.4.3/typing.py", line 1359, in <module>
class Callable(extra=collections_abc.Callable, metaclass=CallableMeta):
File "/tmp/windmill/cache/pip/typing==3.7.4.3/typing.py", line 1007, in __new__
self._abc_registry = extra._abc_registry
^^^^^^^^^^^^^^^^^^^
AttributeError: type object 'Callable' has no attribute '_abc_registry'
There are now many ways to pass specific context to the AIChat for full-code apps. You can use the inspector in the preview, select lines in the editor, use @ mentions (which works with datatables, backend runnables and frontend runnables)
rubenf · 5d ago
**Full-code apps local development in alpha with datatables and any local AI agents ** For the most adventurous of you, in 1.599.0 you can build raw apps fully locally and windmill will take care of providing enough contexts for an agent like Claude to use datatables for storage when initialized with `wmill app new` . Use `wmill app dev` in the app folder to generate a live preview that will also allow you to apply datatables migrations generated by the agents to generate any datatable needed. Highly recommend setting datatable in your workspace settings for the full experience. Require both an updated CLI and windmill. https://www.youtube.com/watch?v=hNQCmpehE2w Merry christmas 🎅
rubenf · 7d ago
little surprise to discover on latest 🎅 It's early, it works especially well with AI and the new data tables. We're eager for your feedback
rubenf · 2w ago
