Title: Bursty prints · Issue #151 · rovercode/rovercode · GitHub
Open Graph Title: Bursty prints · Issue #151 · rovercode/rovercode
X Title: Bursty prints · Issue #151 · rovercode/rovercode
Description: The print statements from app.py appear in bursts, with long delays between bursts. Even the initial "Starting rovercode service" print is delayed. The problem seems to be only with printing -- the server still runs and responds to a GET...
Open Graph Description: The print statements from app.py appear in bursts, with long delays between bursts. Even the initial "Starting rovercode service" print is delayed. The problem seems to be only with printing -- the...
X Description: The print statements from app.py appear in bursts, with long delays between bursts. Even the initial "Starting rovercode service" print is delayed. The problem seems to be only with print...
Opengraph URL: https://github.com/rovercode/rovercode/issues/151
X: @github
Domain: patch-diff.githubusercontent.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Bursty prints","articleBody":"The print statements from app.py appear in bursts, with long delays between bursts.\r\n\r\n- Even the initial \"Starting rovercode service\" print is delayed.\r\n- The problem seems to be only with printing -- the server still runs and responds to a GET on the `/` endpoint.\r\n- This does *not* seem to be related to @jeeshofone's logging changes in the upcoming systemd service installation. It happens now in the standard docker install.\r\n- Increasing the sensor polling period to 20 seconds did not improve the problem.\r\n- Commenting out all `socketio.start_background_task()` and `socketio.run()` made the problem go away.\r\n- Using the debugging server instead of eventlet behind socketio did not help.\r\n- [This thread](https://github.com/miguelgrinberg/Flask-SocketIO/issues/418) suggested sprinkling in some `socketio.sleep(0)`s to release the CPU. I put them a lot of places, with no effect.\r\n- That thread also suggested monkey_patching with eventlet. We should probably add that, but it didn't seem to fix the problem.","author":{"url":"https://github.com/hbradio","@type":"Person","name":"hbradio"},"datePublished":"2018-05-31T02:59:49.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/151/rovercode/issues/151"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:6abe0fb1-c3b4-0a4e-3cad-61008d41f19c |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 9634:27C649:34EC788:4497246:69804A43 |
| html-safe-nonce | cb56a930cb9750bc21855da0328ac065be24534bd2f0c09e92fa2c1ecd0e52f5 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5NjM0OjI3QzY0OTozNEVDNzg4OjQ0OTcyNDY6Njk4MDRBNDMiLCJ2aXNpdG9yX2lkIjoiNzczNzEzOTI0NDgyNDU0NTg1OSIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 95af063cb47533b3eb2b82658d45a8dddff017c73d4d409b079a2377d79ad3e7 |
| hovercard-subject-tag | issue:327975972 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/rovercode/rovercode/151/issue_layout |
| twitter:image | https://opengraph.githubassets.com/d8991da58de015f67a7f4e49accc93664609f2a87aa9158c40a1eb3f1f3d1133/rovercode/rovercode/issues/151 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/d8991da58de015f67a7f4e49accc93664609f2a87aa9158c40a1eb3f1f3d1133/rovercode/rovercode/issues/151 |
| og:image:alt | The print statements from app.py appear in bursts, with long delays between bursts. Even the initial "Starting rovercode service" print is delayed. The problem seems to be only with printing -- the... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | hbradio |
| hostname | github.com |
| expected-hostname | github.com |
| None | 60279d4097367e16897439d16d6bbe4180663db828c666eeed2656988ffe59f6 |
| turbo-cache-control | no-preview |
| go-import | github.com/rovercode/rovercode git https://github.com/rovercode/rovercode.git |
| octolytics-dimension-user_id | 22405869 |
| octolytics-dimension-user_login | rovercode |
| octolytics-dimension-repository_id | 48381501 |
| octolytics-dimension-repository_nwo | rovercode/rovercode |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 48381501 |
| octolytics-dimension-repository_network_root_nwo | rovercode/rovercode |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 7c85641c598ad130c74f7bcc27f58575cac69551 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width