We encountered a problem

---

CMetaAsync internal error: cannot access local variable 'ind' where it is not associated with a value
concurrent.futures.process._RemoteTraceback: 
"""
Traceback (most recent call last):
  File "/home/fursin/.local/share/uv/python/cpython-3.14.7-linux-x86_64-gnu/lib/python3.14/concurrent/futures/process.py", line 254, in _process_worker
    r = call_item.fn(*call_item.args, **call_item.kwargs)
  File "/home/fursin/CMETA/repos/local/cache/task--setup--python--de4f425bf3ca481c/.venv/lib/python3.14/site-packages/cmeta/core_async.py", line 82, in _access_worker
    return cmeta.access(params)
           ~~~~~~~~~~~~^^^^^^^^
  File "/home/fursin/CMETA/repos/local/cache/task--setup--python--de4f425bf3ca481c/.venv/lib/python3.14/site-packages/cmeta/core.py", line 920, in access
    result = func(command_params)
  File "/home/fursin/CMETA-CTUNING-AI-FGG/repos/cmeta-ctuning-ai-server2/category/cserver.ctuning.ck.challenge/api/v1.py", line 94, in web
    return v1_1._web(self, **params)
           ~~~~~~~~~^^^^^^^^^^^^^^^^
  File "/home/fursin/CMETA-CTUNING-AI-FGG/repos/cmeta-ctuning-ai-server2/category/cserver.ctuning.ck.challenge/api/v1_1.py", line 303, in _web
    {str(ind)}) {prefix}{name_item}
         ^^^
UnboundLocalError: cannot access local variable 'ind' where it is not associated with a value
"""

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/fursin/CMETA/repos/local/cache/task--setup--python--de4f425bf3ca481c/.venv/lib/python3.14/site-packages/cmeta/core_async.py", line 178, in access
    return await loop.run_in_executor(self._executor, func)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
UnboundLocalError: cannot access local variable 'ind' where it is not associated with a value

---

If this problem persists, please contact us !