15 commits

Author	SHA1	Message	Date
Felipe Martin	0afef7760c	Include connection ID in plugin context (#36074) ... * feat: include connection id in the plugin context * refactor: group ConnectionId next to SessionId in plugin Context Addresses review feedback to keep related identifier fields adjacent. * fix(files): forward Connection-Id on file uploads to plugin hooks The webapp uploadFile XHR didn't attach the Connection-Id header, so FileWillBeUploaded plugin hooks always received an empty ConnectionId. Read it from the websocket selector and set it on the request, matching how drafts and channel bookmarks already do it. Adds a server-side test asserting the connection id propagates through pluginContext. * fix(lint): reorder file_actions imports to satisfy import/order * Document ConnectionId on request.Context	2026-05-11 10:09:47 +02:00
Ben Schumacher	ed3a7e8539	Add trigger field to command execution logs (#34950) ... Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>	2026-01-21 11:31:05 +01:00
Jesse Hallam	7dff47ee6d	Sentry context nil session (#34383) ... * whitespace changes * context.WithSession: ignore if nil * unit test context.WithSession	2025-11-04 10:12:30 -04:00
Ben Schumacher	bfb15ab179	[MM-61074] Fix errcheck issues in oauth_test.go and web_test.go (#30707) ... Co-authored-by: Claude <noreply@anthropic.com>	2025-05-07 12:41:10 +02:00
Ben Schumacher	166a676fe5	Enforce use of any instead of interface{} (#30588)	2025-03-31 10:44:34 +02:00
Agniva De Sarker	6075b1cd4e	MM-61225: Revert session pooling (#28901) ... This originated from https://github.com/mattermost/mattermost/issues/15249. However, the original idea was discarded https://github.com/mattermost/mattermost/issues/15249#issuecomment-709713065 as being too complicated to implement. Then I had another idea to implement it just for session objects. My thinking was that since every single request allocates a new session struct, it would be good to use a sync.Pool for that. However, 4 years later, now we know that the primary bottleneck in app performance comes from websocket event marshalling. Therefore, while it would be good to do this, it is difficult to do it correctly (as shown by the numerous racy tests). Hence, reverting this. ```release-note NONE ```	2024-10-24 22:50:44 +05:30
Ben Schumacher	7ff22436dc	[MM-60685] Fix racy TestSyncLdap (#28324)	2024-10-14 13:04:48 +02:00
Ben Schumacher	929ab6b289	Document variable names for request.CTX and mlog.Logger (#26029)	2024-01-26 14:03:35 +01:00
Ben Schumacher	486e836b83	Fix racy test issues (#24971)	2023-11-06 12:26:17 +01:00
Ben Schumacher	4408ece955	Fix data race in bulk import tests (#24897)	2023-10-16 22:40:19 +02:00
Ben Schumacher	13c05a571f	Migrate store methods to use request.Context instead of context.Context (#24836)	2023-10-11 13:08:55 +02:00
Felipe Martin	f65dad83bb	Migrate emojiStore to use request.CTX instead of context.Context (#24514) ... * migrate emojistore to request.ctx * use mlog.CreateConsoleTestLogger * Add comment to WithMaster and RequestContextWithMaster	2023-09-11 17:07:29 +02:00
Ben Schumacher	c656ca3fe3	Remove unused err field from request.Context (#24471)	2023-09-07 12:12:25 +02:00
Ben Schumacher	30b12f199b	[MM-54132] Use annotated logger for log messages from jobs (#24275)	2023-09-07 08:50:22 +02:00
Felipe Martin	9f7521d003	Move request package into public/shared folder (#24420) ... * move request package to public/shared * updated app-layers * update app layer * remove original package location	2023-09-05 09:47:30 +02:00