René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`feast serve_offline` displays no info logging","articleBody":"## Expected Behavior \r\nThe `feast serve_offline` command (which launches a feast offline server process) should behave similar to the `feast serve` command, which displays helpful information, including the serving endpoint (host:port). The `feast serve` command shows info like the following:\r\n```\r\n[2024-10-16 19:14:32 -0600] [17832] [INFO] Starting gunicorn 22.0.0\r\n[2024-10-16 19:14:32 -0600] [17832] [INFO] Listening at: http://127.0.0.1:6566 (17832)\r\n[2024-10-16 19:14:32 -0600] [17832] [INFO] Using worker: uvicorn.workers.UvicornWorker\r\n[2024-10-16 19:14:32 -0600] [17863] [INFO] Booting worker with pid: 17863\r\n[2024-10-16 19:14:32 -0600] [17863] [INFO] Started server process [17863]\r\n[2024-10-16 19:14:32 -0600] [17863] [INFO] Waiting for application startup.\r\n[2024-10-16 19:14:32 -0600] [17863] [INFO] Application startup complete.\r\n```\r\nAnd on shutdown, the `feast serve` command gives:\r\n```\r\n[2024-10-16 19:28:02 -0600] [17832] [INFO] Handling signal: int\r\n[2024-10-16 19:28:02 -0600] [17863] [INFO] Shutting down\r\n[2024-10-16 19:28:02 -0600] [17863] [INFO] Error while closing socket [Errno 9] Bad file descriptor\r\n[2024-10-16 19:28:02 -0600] [17863] [INFO] Waiting for application shutdown.\r\n[2024-10-16 19:28:02 -0600] [17863] [INFO] Application shutdown complete.\r\n[2024-10-16 19:28:02 -0600] [17863] [INFO] Finished server process [17863]\r\n[2024-10-16 19:28:02 -0600] [17832] [ERROR] Worker (pid:17863) was sent SIGINT!\r\n[2024-10-16 19:28:02 -0600] [17832] [INFO] Shutting down: Master\r\n```\r\n\r\nNote: this issue may affect the registry server as well. I have not looked into that, but my expectation would be that all three servers should have logging at startup, during operation, and at shutdown.\r\n\r\n## Current Behavior\r\nThe `feast serve_offline` command just launches the process and displays no output but a blinking cursor. The user is left wondering if the server is ready, and what endpoint it is running on. There is also presumably no information to capture for logging to show for example, when the server started or shutdown.\r\n\r\n## Steps to reproduce\r\n```\r\n# setup temp feature store\r\nfeast init feature_store\r\n\r\ncd feature_store/feature_repo\r\nfeast apply\r\n```\r\n\r\n```\r\n# run the online server to see its behavior\r\n# (after output you can kill with ctl-c)\r\nfeast serve\r\n\r\n# run the offline server\r\n# (observe that there is no output logged)\r\nfeast serve_offline\r\n```\r\n### Specifications\r\n\r\n- Version: 0.40.1\r\n- Platform: MacOS M2, Sequoia 15.0.1\r\n- Subsystem:\r\n\r\n## Possible Solution\r\nAdd logging to `feast serve_offline` following the pattern of `feast serve`.","author":{"url":"https://github.com/dandawg","@type":"Person","name":"dandawg"},"datePublished":"2024-10-17T01:51:42.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/4639/feast/issues/4639"}