You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem\n\n only recognizes Service invocation paths (). When Restate sends Virtual Object invocations over the protocol (used for HTTP/1.1 deployments such as Uvicorn), the path is . The current parser returns , so the ASGI app returns 404 before the handler runs.\n\n## Impact\n\nAny Python deployment served over HTTP/1.1 cannot receive Virtual Object invocations, including internal calls from one service to a Virtual Object. This breaks patterns where a Service handler calls and Restate routes the resulting invocation back to the deployment.\n\n## Reproduction\n\n1. Register a Virtual Object service in an endpoint served by Uvicorn (HTTP/1.1).\n2. From another Service, call .\n3. Restate sends to the deployment.\n4. returns → 404.\n\n## Expected behavior\n\n should detect the Virtual Object path shape and route to . The key is already available in the Restate protocol body, so routing only needs service/handler.\n\n## Workaround\n\nWe currently monkey-patch at import time to handle the extra key segment. We would prefer to remove this once the SDK supports it natively.
Problem\n\n only recognizes Service invocation paths (). When Restate sends Virtual Object invocations over the protocol (used for HTTP/1.1 deployments such as Uvicorn), the path is . The current parser returns , so the ASGI app returns 404 before the handler runs.\n\n## Impact\n\nAny Python deployment served over HTTP/1.1 cannot receive Virtual Object invocations, including internal calls from one service to a Virtual Object. This breaks patterns where a Service handler calls and Restate routes the resulting invocation back to the deployment.\n\n## Reproduction\n\n1. Register a Virtual Object service in an endpoint served by Uvicorn (HTTP/1.1).\n2. From another Service, call .\n3. Restate sends to the deployment.\n4. returns → 404.\n\n## Expected behavior\n\n should detect the Virtual Object path shape and route to . The key is already available in the Restate protocol body, so routing only needs service/handler.\n\n## Workaround\n\nWe currently monkey-patch at import time to handle the extra key segment. We would prefer to remove this once the SDK supports it natively.