issue_comments
Data license: AGPL · Data source: ACEmulator Project
1 row where user = 25497527
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
id ▼ | html_url | issue_url | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
277143116 | https://github.com/ACEmulator/ACE/issues/12#issuecomment-277143116 | https://api.github.com/repos/ACEmulator/ACE/issues/12 | MDEyOklzc3VlQ29tbWVudDI3NzE0MzExNg== | firesickle 25497527 | 2017-02-03T01:52:42Z | 2017-02-03T01:52:42Z | NONE | As an alternative, You can run it in its current state with a scheduled task, which I think you can set up to execute upon start up. Additionally, you can set a scheduled task to run again if it is not already running, to get the client to start back up if it threw an exception and ended. Not sure myself what extra steps would need to make this into a service. In my past experience, I have had never-ending problems with custom built windows services that do web interactions, had a lot more success when switching to scheduled tasks | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Converting ACE to run as a Windows service 205040357 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] ( [html_url] TEXT, [issue_url] TEXT, [id] INTEGER PRIMARY KEY, [node_id] TEXT, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [updated_at] TEXT, [author_association] TEXT, [body] TEXT, [reactions] TEXT, [performed_via_github_app] TEXT, [issue] INTEGER REFERENCES [issues]([id]) ); CREATE INDEX [idx_issue_comments_issue] ON [issue_comments] ([issue]); CREATE INDEX [idx_issue_comments_user] ON [issue_comments] ([user]);