Hugging Face's logo

Spaces:
KingZack
/
ctp-slack-bot
Runtime error

App Files Community
KingZack commited on
Commit
a1d4c39
·
1 Parent(s): f317cf0

committing files to for the HF space

Browse files
Files changed (1) hide show
  1. src/ctp_slack_bot/api/logs/app.log +176 -0
src/ctp_slack_bot/api/logs/app.log ADDED
@@ -0,0 +1,176 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ 2025-04-10 21:31:27.061 | INFO | ctp_slack_bot.core.logging:setup_logging:97 - Logging configured with level INFO
2
+ 2025-04-10 21:31:27.061 | INFO | __main__:main:27 - Starting application
3
+ 2025-04-10 21:31:27.062 | INFO | logging:callHandlers:1736 - Scheduler started
4
+ 2025-04-10 21:31:27.062 | INFO | ctp_slack_bot.tasks.scheduler:start_scheduler:41 - Scheduler started with timezone: UTC
5
+ 2025-04-10 21:31:27.062 | INFO | __main__:main:31 - Started scheduler
6
+ 2025-04-10 21:31:27.128 | INFO | __main__:main:51 - Starting Slack Socket Mode handler…
7
+ 2025-04-10 21:31:28.172 | INFO | logging:callHandlers:1736 - A new session (s_275541900) has been established
8
+ 2025-04-10 21:31:28.172 | INFO | logging:callHandlers:1736 - ⚡️ Bolt app is running!
9
+ 2025-04-10 21:31:50.759 | INFO | logging:callHandlers:1736 - HTTP Request: POST https://api.openai.com/v1/chat/completions "HTTP/1.1 200 OK"
10
+ 2025-04-10 21:31:55.342 | INFO | logging:callHandlers:1736 - HTTP Request: POST https://api.openai.com/v1/chat/completions "HTTP/1.1 200 OK"
11
+ 2025-04-10 21:32:47.535 | INFO | logging:callHandlers:1736 - HTTP Request: POST https://api.openai.com/v1/chat/completions "HTTP/1.1 200 OK"
12
+ 2025-04-10 21:33:47.153 | INFO | logging:callHandlers:1736 - HTTP Request: POST https://api.openai.com/v1/chat/completions "HTTP/1.1 200 OK"
13
+ 2025-04-10 21:33:51.673 | INFO | ctp_slack_bot.core.logging:setup_logging:97 - Logging configured with level INFO
14
+ 2025-04-10 21:33:51.673 | INFO | __main__:main:27 - Starting application
15
+ 2025-04-10 21:33:51.673 | INFO | logging:callHandlers:1736 - Scheduler started
16
+ 2025-04-10 21:33:51.673 | INFO | ctp_slack_bot.tasks.scheduler:start_scheduler:41 - Scheduler started with timezone: UTC
17
+ 2025-04-10 21:33:51.673 | INFO | __main__:main:31 - Started scheduler
18
+ 2025-04-10 21:33:51.742 | INFO | __main__:main:51 - Starting Slack Socket Mode handler…
19
+ 2025-04-10 21:33:52.609 | INFO | logging:callHandlers:1736 - A new session (s_277291916) has been established
20
+ 2025-04-10 21:33:52.610 | INFO | logging:callHandlers:1736 - ⚡️ Bolt app is running!
21
+ 2025-04-10 21:33:56.280 | WARNING | logging:callHandlers:1736 - Unhandled request ({'type': 'event_callback', 'event': {'type': 'message'}})
22
+ ---
23
+ [Suggestion] You can handle this type of event with the following listener function:
24
+
25
+ @app.event("message")
26
+ async def handle_message_events(body, logger):
27
+ logger.info(body)
28
+
29
+ 2025-04-10 21:33:56.280 | INFO | logging:callHandlers:1736 - Unsuccessful Bolt execution result (status: 404, body: {"error": "unhandled request"})
30
+ 2025-04-10 21:33:59.954 | WARNING | logging:callHandlers:1736 - Unhandled request ({'type': 'event_callback', 'event': {'type': 'message'}})
31
+ ---
32
+ [Suggestion] You can handle this type of event with the following listener function:
33
+
34
+ @app.event("message")
35
+ async def handle_message_events(body, logger):
36
+ logger.info(body)
37
+
38
+ 2025-04-10 21:33:59.955 | INFO | logging:callHandlers:1736 - Unsuccessful Bolt execution result (status: 404, body: {"error": "unhandled request"})
39
+ 2025-04-10 21:35:20.361 | INFO | ctp_slack_bot.core.logging:setup_logging:97 - Logging configured with level INFO
40
+ 2025-04-10 21:35:20.362 | INFO | __main__:main:27 - Starting application
41
+ 2025-04-10 21:35:20.362 | INFO | logging:callHandlers:1736 - Scheduler started
42
+ 2025-04-10 21:35:20.362 | INFO | ctp_slack_bot.tasks.scheduler:start_scheduler:41 - Scheduler started with timezone: UTC
43
+ 2025-04-10 21:35:20.362 | INFO | __main__:main:31 - Started scheduler
44
+ 2025-04-10 21:35:20.425 | INFO | __main__:main:51 - Starting Slack Socket Mode handler…
45
+ 2025-04-10 21:35:21.134 | INFO | logging:callHandlers:1736 - A new session (s_278569952) has been established
46
+ 2025-04-10 21:35:21.135 | INFO | logging:callHandlers:1736 - ⚡️ Bolt app is running!
47
+ 2025-04-10 21:35:28.228 | INFO | ctp_slack_bot.core.logging:setup_logging:97 - Logging configured with level INFO
48
+ 2025-04-10 21:35:28.228 | INFO | __main__:main:27 - Starting application
49
+ 2025-04-10 21:35:28.228 | INFO | logging:callHandlers:1736 - Scheduler started
50
+ 2025-04-10 21:35:28.229 | INFO | ctp_slack_bot.tasks.scheduler:start_scheduler:41 - Scheduler started with timezone: UTC
51
+ 2025-04-10 21:35:28.229 | INFO | __main__:main:31 - Started scheduler
52
+ 2025-04-10 21:35:28.283 | INFO | __main__:main:51 - Starting Slack Socket Mode handler…
53
+ 2025-04-10 21:35:29.041 | INFO | logging:callHandlers:1736 - A new session (s_277652448) has been established
54
+ 2025-04-10 21:35:29.049 | INFO | logging:callHandlers:1736 - ⚡️ Bolt app is running!
55
+ 2025-04-10 21:35:41.841 | WARNING | logging:callHandlers:1736 - Unhandled request ({'type': 'event_callback', 'event': {'type': 'message'}})
56
+ ---
57
+ [Suggestion] You can handle this type of event with the following listener function:
58
+
59
+ @app.event("message")
60
+ async def handle_message_events(body, logger):
61
+ logger.info(body)
62
+
63
+ 2025-04-10 21:35:41.842 | INFO | logging:callHandlers:1736 - Unsuccessful Bolt execution result (status: 404, body: {"error": "unhandled request"})
64
+ 2025-04-10 21:35:45.473 | WARNING | logging:callHandlers:1736 - Unhandled request ({'type': 'event_callback', 'event': {'type': 'message'}})
65
+ ---
66
+ [Suggestion] You can handle this type of event with the following listener function:
67
+
68
+ @app.event("message")
69
+ async def handle_message_events(body, logger):
70
+ logger.info(body)
71
+
72
+ 2025-04-10 21:35:45.473 | INFO | logging:callHandlers:1736 - Unsuccessful Bolt execution result (status: 404, body: {"error": "unhandled request"})
73
+ 2025-04-10 21:36:11.033 | INFO | logging:callHandlers:1736 - HTTP Request: POST https://api.openai.com/v1/chat/completions "HTTP/1.1 200 OK"
74
+ 2025-04-10 21:36:24.241 | WARNING | logging:callHandlers:1736 - Unhandled request ({'type': 'event_callback', 'event': {'type': 'message'}})
75
+ ---
76
+ [Suggestion] You can handle this type of event with the following listener function:
77
+
78
+ @app.event("message")
79
+ async def handle_message_events(body, logger):
80
+ logger.info(body)
81
+
82
+ 2025-04-10 21:36:24.242 | INFO | logging:callHandlers:1736 - Unsuccessful Bolt execution result (status: 404, body: {"error": "unhandled request"})
83
+ 2025-04-10 21:36:27.821 | WARNING | logging:callHandlers:1736 - Unhandled request ({'type': 'event_callback', 'event': {'type': 'message'}})
84
+ ---
85
+ [Suggestion] You can handle this type of event with the following listener function:
86
+
87
+ @app.event("message")
88
+ async def handle_message_events(body, logger):
89
+ logger.info(body)
90
+
91
+ 2025-04-10 21:36:27.822 | INFO | logging:callHandlers:1736 - Unsuccessful Bolt execution result (status: 404, body: {"error": "unhandled request"})
92
+ 2025-04-10 21:37:03.941 | WARNING | logging:callHandlers:1736 - Unhandled request ({'type': 'event_callback', 'event': {'type': 'message'}})
93
+ ---
94
+ [Suggestion] You can handle this type of event with the following listener function:
95
+
96
+ @app.event("message")
97
+ async def handle_message_events(body, logger):
98
+ logger.info(body)
99
+
100
+ 2025-04-10 21:37:03.942 | INFO | logging:callHandlers:1736 - Unsuccessful Bolt execution result (status: 404, body: {"error": "unhandled request"})
101
+ 2025-04-10 21:37:04.607 | WARNING | logging:callHandlers:1736 - Unhandled request ({'type': 'event_callback', 'event': {'type': 'message'}})
102
+ ---
103
+ [Suggestion] You can handle this type of event with the following listener function:
104
+
105
+ @app.event("message")
106
+ async def handle_message_events(body, logger):
107
+ logger.info(body)
108
+
109
+ 2025-04-10 21:37:04.607 | INFO | logging:callHandlers:1736 - Unsuccessful Bolt execution result (status: 404, body: {"error": "unhandled request"})
110
+ 2025-04-10 21:37:08.556 | WARNING | logging:callHandlers:1736 - Unhandled request ({'type': 'event_callback', 'event': {'type': 'message'}})
111
+ ---
112
+ [Suggestion] You can handle this type of event with the following listener function:
113
+
114
+ @app.event("message")
115
+ async def handle_message_events(body, logger):
116
+ logger.info(body)
117
+
118
+ 2025-04-10 21:37:08.557 | INFO | logging:callHandlers:1736 - Unsuccessful Bolt execution result (status: 404, body: {"error": "unhandled request"})
119
+ 2025-04-10 21:37:17.414 | INFO | ctp_slack_bot.core.logging:setup_logging:97 - Logging configured with level INFO
120
+ 2025-04-10 21:37:17.414 | INFO | __main__:main:27 - Starting application
121
+ 2025-04-10 21:37:17.414 | INFO | logging:callHandlers:1736 - Scheduler started
122
+ 2025-04-10 21:37:17.414 | INFO | ctp_slack_bot.tasks.scheduler:start_scheduler:41 - Scheduler started with timezone: UTC
123
+ 2025-04-10 21:37:17.414 | INFO | __main__:main:31 - Started scheduler
124
+ 2025-04-10 21:37:17.467 | INFO | __main__:main:51 - Starting Slack Socket Mode handler…
125
+ 2025-04-10 21:37:18.268 | INFO | logging:callHandlers:1736 - A new session (s_277099488) has been established
126
+ 2025-04-10 21:37:18.268 | INFO | logging:callHandlers:1736 - ⚡️ Bolt app is running!
127
+ 2025-04-10 21:37:37.436 | WARNING | logging:callHandlers:1736 - Unhandled request ({'type': 'event_callback', 'event': {'type': 'app_mention'}})
128
+ ---
129
+ [Suggestion] You can handle this type of event with the following listener function:
130
+
131
+ @app.event("app_mention")
132
+ async def handle_app_mention_events(body, logger):
133
+ logger.info(body)
134
+
135
+ 2025-04-10 21:37:37.437 | INFO | logging:callHandlers:1736 - Unsuccessful Bolt execution result (status: 404, body: {"error": "unhandled request"})
136
+ 2025-04-10 21:37:41.138 | WARNING | logging:callHandlers:1736 - Unhandled request ({'type': 'event_callback', 'event': {'type': 'app_mention'}})
137
+ ---
138
+ [Suggestion] You can handle this type of event with the following listener function:
139
+
140
+ @app.event("app_mention")
141
+ async def handle_app_mention_events(body, logger):
142
+ logger.info(body)
143
+
144
+ 2025-04-10 21:37:41.139 | INFO | logging:callHandlers:1736 - Unsuccessful Bolt execution result (status: 404, body: {"error": "unhandled request"})
145
+ 2025-04-10 21:38:59.556 | WARNING | logging:callHandlers:1736 - Unhandled request ({'type': 'event_callback', 'event': {'type': 'app_mention'}})
146
+ ---
147
+ [Suggestion] You can handle this type of event with the following listener function:
148
+
149
+ @app.event("app_mention")
150
+ async def handle_app_mention_events(body, logger):
151
+ logger.info(body)
152
+
153
+ 2025-04-10 21:38:59.558 | INFO | logging:callHandlers:1736 - Unsuccessful Bolt execution result (status: 404, body: {"error": "unhandled request"})
154
+ 2025-04-10 21:41:54.547 | INFO | logging:callHandlers:1736 - HTTP Request: POST https://api.openai.com/v1/chat/completions "HTTP/1.1 200 OK"
155
+ 2025-04-10 21:43:47.542 | WARNING | logging:callHandlers:1736 - Unhandled request ({'type': 'event_callback', 'event': {'type': 'app_mention'}})
156
+ ---
157
+ [Suggestion] You can handle this type of event with the following listener function:
158
+
159
+ @app.event("app_mention")
160
+ async def handle_app_mention_events(body, logger):
161
+ logger.info(body)
162
+
163
+ 2025-04-10 21:43:47.543 | INFO | logging:callHandlers:1736 - Unsuccessful Bolt execution result (status: 404, body: {"error": "unhandled request"})
164
+ 2025-04-10 22:54:27.960 | INFO | logging:callHandlers:1736 - The session (s_277099488) seems to be stale. Reconnecting... reason: disconnected for 118+ seconds)
165
+ 2025-04-10 22:54:28.864 | INFO | logging:callHandlers:1736 - The old session (s_277099488) has been abandoned
166
+ 2025-04-10 22:54:29.424 | INFO | logging:callHandlers:1736 - A new session (s_277108397) has been established
167
+ 2025-04-10 22:56:28.963 | INFO | logging:callHandlers:1736 - The session (s_277108397) seems to be stale. Reconnecting... reason: disconnected for 79+ seconds)
168
+ 2025-04-10 22:56:29.519 | INFO | logging:callHandlers:1736 - The old session (s_277108397) has been abandoned
169
+ 2025-04-10 22:56:30.028 | INFO | logging:callHandlers:1736 - A new session (s_277108557) has been established
170
+ 2025-04-10 23:03:52.469 | INFO | logging:callHandlers:1736 - The session (s_277108557) seems to be stale. Reconnecting... reason: disconnected for 402+ seconds)
171
+ 2025-04-10 23:03:52.995 | INFO | logging:callHandlers:1736 - The old session (s_277108557) has been abandoned
172
+ 2025-04-10 23:03:53.579 | INFO | logging:callHandlers:1736 - A new session (s_277125144) has been established
173
+ 2025-04-10 23:16:11.541 | INFO | logging:callHandlers:1736 - The session (s_277125144) seems to be stale. Reconnecting... reason: disconnected for 707+ seconds)
174
+ 2025-04-10 23:16:12.126 | INFO | logging:callHandlers:1736 - The old session (s_277125144) has been abandoned
175
+ 2025-04-10 23:16:12.660 | INFO | logging:callHandlers:1736 - A new session (s_277125638) has been established
176
+ 2025-04-10 23:21:27.332 | INFO | logging:callHandlers:1736 - The session (s_277125638) seems to be stale. Reconnecting... reason: disconnected for 274+ seconds)