Swift Package IndexBuild Information
Successful build of Sloppy, reference main (a5adfa), with Swift 6.2 for macOS (SPM) on 30 Apr 2026 23:37:45 UTC.
Swift 6 data race errors: 0
Build Command
env DEVELOPER_DIR=/Applications/Xcode-26.3.0.app xcrun swift build --arch arm64Build Log
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:245:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
243 | }
244 | context.eventLoop.execute {
245 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
246 | }
247 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:323:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
321 | return
322 | }
323 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
324 | context.close(promise: nil)
325 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:324:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
322 | }
323 | context.eventLoop.execute {
324 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
325 | }
326 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:410:29: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
408 | if !keepAlive {
409 | el.execute {
410 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
411 | }
412 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:410:29: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
408 | if !keepAlive {
409 | el.execute {
410 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
411 | }
412 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:590:21: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
588 | let frame = WebSocketFrame(fin: true, opcode: .connectionClose, data: data)
589 | context.writeAndFlush(self.wrapOutboundOut(frame)).whenComplete { _ in
590 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
591 | context.close(promise: nil)
592 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:591:25: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
589 | context.writeAndFlush(self.wrapOutboundOut(frame)).whenComplete { _ in
590 | context.eventLoop.execute {
591 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
592 | }
593 | continuation.resume()
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:283:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
281 | return
282 | }
283 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
284 | context.close(promise: nil)
285 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:284:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
282 | }
283 | context.eventLoop.execute {
284 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
285 | }
286 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:304:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
302 | return
303 | }
304 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
305 | context.close(promise: nil)
306 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:305:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
303 | }
304 | context.eventLoop.execute {
305 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
306 | }
307 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
[#SendableClosureCaptures]: <https://docs.swift.org/compiler/documentation/diagnostics/sendable-closure-captures>
[1376/1403] Compiling sloppy ChannelsAPIRouter.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:87:29: warning: result of 'try?' is unused [#no-usage]
85 | // Upgrade completion is not guaranteed to run on the channel loop.
86 | context.eventLoop.execute {
87 | try? context.pipeline.syncOperations.removeHandler(httpHandler)
| `- warning: result of 'try?' is unused [#no-usage]
88 | }
89 | }
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:93:40: warning: type 'any HTTPServerProtocolUpgrader' does not conform to the 'Sendable' protocol
91 |
92 | return channel.pipeline.configureHTTPServerPipeline(
93 | withServerUpgrade: upgradeConfig
| `- warning: type 'any HTTPServerProtocolUpgrader' does not conform to the 'Sendable' protocol
94 | ).flatMap {
95 | channel.pipeline.addHandler(httpHandler)
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:87:34: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
85 | // Upgrade completion is not guaranteed to run on the channel loop.
86 | context.eventLoop.execute {
87 | try? context.pipeline.syncOperations.removeHandler(httpHandler)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
88 | }
89 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:87:29: warning: no calls to throwing functions occur within 'try' expression
85 | // Upgrade completion is not guaranteed to run on the channel loop.
86 | context.eventLoop.execute {
87 | try? context.pipeline.syncOperations.removeHandler(httpHandler)
| `- warning: no calls to throwing functions occur within 'try' expression
88 | }
89 | }
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:201:49: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
199 | switch result {
200 | case .success(let response):
201 | self.writeResponse(context: context, requestHead: head, response: response)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
202 | case .failure(let error):
203 | self.logger.error("Failed to handle request: \(String(describing: error))")
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:244:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
242 | return
243 | }
244 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
245 | context.close(promise: nil)
246 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:245:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
243 | }
244 | context.eventLoop.execute {
245 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
246 | }
247 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:323:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
321 | return
322 | }
323 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
324 | context.close(promise: nil)
325 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:324:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
322 | }
323 | context.eventLoop.execute {
324 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
325 | }
326 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:410:29: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
408 | if !keepAlive {
409 | el.execute {
410 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
411 | }
412 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:410:29: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
408 | if !keepAlive {
409 | el.execute {
410 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
411 | }
412 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:590:21: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
588 | let frame = WebSocketFrame(fin: true, opcode: .connectionClose, data: data)
589 | context.writeAndFlush(self.wrapOutboundOut(frame)).whenComplete { _ in
590 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
591 | context.close(promise: nil)
592 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:591:25: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
589 | context.writeAndFlush(self.wrapOutboundOut(frame)).whenComplete { _ in
590 | context.eventLoop.execute {
591 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
592 | }
593 | continuation.resume()
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:283:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
281 | return
282 | }
283 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
284 | context.close(promise: nil)
285 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:284:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
282 | }
283 | context.eventLoop.execute {
284 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
285 | }
286 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:304:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
302 | return
303 | }
304 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
305 | context.close(promise: nil)
306 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:305:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
303 | }
304 | context.eventLoop.execute {
305 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
306 | }
307 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
[#SendableClosureCaptures]: <https://docs.swift.org/compiler/documentation/diagnostics/sendable-closure-captures>
[1377/1403] Compiling sloppy CoreRouter+HTTPRoutes.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:87:29: warning: result of 'try?' is unused [#no-usage]
85 | // Upgrade completion is not guaranteed to run on the channel loop.
86 | context.eventLoop.execute {
87 | try? context.pipeline.syncOperations.removeHandler(httpHandler)
| `- warning: result of 'try?' is unused [#no-usage]
88 | }
89 | }
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:93:40: warning: type 'any HTTPServerProtocolUpgrader' does not conform to the 'Sendable' protocol
91 |
92 | return channel.pipeline.configureHTTPServerPipeline(
93 | withServerUpgrade: upgradeConfig
| `- warning: type 'any HTTPServerProtocolUpgrader' does not conform to the 'Sendable' protocol
94 | ).flatMap {
95 | channel.pipeline.addHandler(httpHandler)
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:87:34: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
85 | // Upgrade completion is not guaranteed to run on the channel loop.
86 | context.eventLoop.execute {
87 | try? context.pipeline.syncOperations.removeHandler(httpHandler)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
88 | }
89 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:87:29: warning: no calls to throwing functions occur within 'try' expression
85 | // Upgrade completion is not guaranteed to run on the channel loop.
86 | context.eventLoop.execute {
87 | try? context.pipeline.syncOperations.removeHandler(httpHandler)
| `- warning: no calls to throwing functions occur within 'try' expression
88 | }
89 | }
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:201:49: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
199 | switch result {
200 | case .success(let response):
201 | self.writeResponse(context: context, requestHead: head, response: response)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
202 | case .failure(let error):
203 | self.logger.error("Failed to handle request: \(String(describing: error))")
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:244:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
242 | return
243 | }
244 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
245 | context.close(promise: nil)
246 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:245:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
243 | }
244 | context.eventLoop.execute {
245 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
246 | }
247 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:323:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
321 | return
322 | }
323 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
324 | context.close(promise: nil)
325 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:324:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
322 | }
323 | context.eventLoop.execute {
324 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
325 | }
326 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:410:29: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
408 | if !keepAlive {
409 | el.execute {
410 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
411 | }
412 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:410:29: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
408 | if !keepAlive {
409 | el.execute {
410 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
411 | }
412 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:590:21: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
588 | let frame = WebSocketFrame(fin: true, opcode: .connectionClose, data: data)
589 | context.writeAndFlush(self.wrapOutboundOut(frame)).whenComplete { _ in
590 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
591 | context.close(promise: nil)
592 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:591:25: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
589 | context.writeAndFlush(self.wrapOutboundOut(frame)).whenComplete { _ in
590 | context.eventLoop.execute {
591 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
592 | }
593 | continuation.resume()
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:283:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
281 | return
282 | }
283 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
284 | context.close(promise: nil)
285 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:284:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
282 | }
283 | context.eventLoop.execute {
284 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
285 | }
286 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:304:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
302 | return
303 | }
304 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
305 | context.close(promise: nil)
306 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:305:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
303 | }
304 | context.eventLoop.execute {
305 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
306 | }
307 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
[#SendableClosureCaptures]: <https://docs.swift.org/compiler/documentation/diagnostics/sendable-closure-captures>
[1378/1403] Compiling sloppy CoreRouterRegistrar.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:87:29: warning: result of 'try?' is unused [#no-usage]
85 | // Upgrade completion is not guaranteed to run on the channel loop.
86 | context.eventLoop.execute {
87 | try? context.pipeline.syncOperations.removeHandler(httpHandler)
| `- warning: result of 'try?' is unused [#no-usage]
88 | }
89 | }
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:93:40: warning: type 'any HTTPServerProtocolUpgrader' does not conform to the 'Sendable' protocol
91 |
92 | return channel.pipeline.configureHTTPServerPipeline(
93 | withServerUpgrade: upgradeConfig
| `- warning: type 'any HTTPServerProtocolUpgrader' does not conform to the 'Sendable' protocol
94 | ).flatMap {
95 | channel.pipeline.addHandler(httpHandler)
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:87:34: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
85 | // Upgrade completion is not guaranteed to run on the channel loop.
86 | context.eventLoop.execute {
87 | try? context.pipeline.syncOperations.removeHandler(httpHandler)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
88 | }
89 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:87:29: warning: no calls to throwing functions occur within 'try' expression
85 | // Upgrade completion is not guaranteed to run on the channel loop.
86 | context.eventLoop.execute {
87 | try? context.pipeline.syncOperations.removeHandler(httpHandler)
| `- warning: no calls to throwing functions occur within 'try' expression
88 | }
89 | }
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:201:49: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
199 | switch result {
200 | case .success(let response):
201 | self.writeResponse(context: context, requestHead: head, response: response)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
202 | case .failure(let error):
203 | self.logger.error("Failed to handle request: \(String(describing: error))")
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:244:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
242 | return
243 | }
244 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
245 | context.close(promise: nil)
246 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:245:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
243 | }
244 | context.eventLoop.execute {
245 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
246 | }
247 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:323:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
321 | return
322 | }
323 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
324 | context.close(promise: nil)
325 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:324:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
322 | }
323 | context.eventLoop.execute {
324 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
325 | }
326 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:410:29: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
408 | if !keepAlive {
409 | el.execute {
410 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
411 | }
412 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:410:29: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
408 | if !keepAlive {
409 | el.execute {
410 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
411 | }
412 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:590:21: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
588 | let frame = WebSocketFrame(fin: true, opcode: .connectionClose, data: data)
589 | context.writeAndFlush(self.wrapOutboundOut(frame)).whenComplete { _ in
590 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
591 | context.close(promise: nil)
592 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:591:25: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
589 | context.writeAndFlush(self.wrapOutboundOut(frame)).whenComplete { _ in
590 | context.eventLoop.execute {
591 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
592 | }
593 | continuation.resume()
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:283:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
281 | return
282 | }
283 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
284 | context.close(promise: nil)
285 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:284:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
282 | }
283 | context.eventLoop.execute {
284 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
285 | }
286 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:304:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
302 | return
303 | }
304 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
305 | context.close(promise: nil)
306 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:305:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
303 | }
304 | context.eventLoop.execute {
305 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
306 | }
307 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
[#SendableClosureCaptures]: <https://docs.swift.org/compiler/documentation/diagnostics/sendable-closure-captures>
[1379/1403] Compiling sloppy CronAPIRouter.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:87:29: warning: result of 'try?' is unused [#no-usage]
85 | // Upgrade completion is not guaranteed to run on the channel loop.
86 | context.eventLoop.execute {
87 | try? context.pipeline.syncOperations.removeHandler(httpHandler)
| `- warning: result of 'try?' is unused [#no-usage]
88 | }
89 | }
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:93:40: warning: type 'any HTTPServerProtocolUpgrader' does not conform to the 'Sendable' protocol
91 |
92 | return channel.pipeline.configureHTTPServerPipeline(
93 | withServerUpgrade: upgradeConfig
| `- warning: type 'any HTTPServerProtocolUpgrader' does not conform to the 'Sendable' protocol
94 | ).flatMap {
95 | channel.pipeline.addHandler(httpHandler)
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:87:34: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
85 | // Upgrade completion is not guaranteed to run on the channel loop.
86 | context.eventLoop.execute {
87 | try? context.pipeline.syncOperations.removeHandler(httpHandler)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
88 | }
89 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:87:29: warning: no calls to throwing functions occur within 'try' expression
85 | // Upgrade completion is not guaranteed to run on the channel loop.
86 | context.eventLoop.execute {
87 | try? context.pipeline.syncOperations.removeHandler(httpHandler)
| `- warning: no calls to throwing functions occur within 'try' expression
88 | }
89 | }
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:201:49: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
199 | switch result {
200 | case .success(let response):
201 | self.writeResponse(context: context, requestHead: head, response: response)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
202 | case .failure(let error):
203 | self.logger.error("Failed to handle request: \(String(describing: error))")
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:244:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
242 | return
243 | }
244 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
245 | context.close(promise: nil)
246 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:245:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
243 | }
244 | context.eventLoop.execute {
245 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
246 | }
247 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:323:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
321 | return
322 | }
323 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
324 | context.close(promise: nil)
325 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:324:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
322 | }
323 | context.eventLoop.execute {
324 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
325 | }
326 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:410:29: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
408 | if !keepAlive {
409 | el.execute {
410 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
411 | }
412 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:410:29: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
408 | if !keepAlive {
409 | el.execute {
410 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
411 | }
412 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:590:21: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
588 | let frame = WebSocketFrame(fin: true, opcode: .connectionClose, data: data)
589 | context.writeAndFlush(self.wrapOutboundOut(frame)).whenComplete { _ in
590 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
591 | context.close(promise: nil)
592 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:591:25: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
589 | context.writeAndFlush(self.wrapOutboundOut(frame)).whenComplete { _ in
590 | context.eventLoop.execute {
591 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
592 | }
593 | continuation.resume()
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:283:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
281 | return
282 | }
283 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
284 | context.close(promise: nil)
285 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:284:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
282 | }
283 | context.eventLoop.execute {
284 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
285 | }
286 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:304:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
302 | return
303 | }
304 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
305 | context.close(promise: nil)
306 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:305:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
303 | }
304 | context.eventLoop.execute {
305 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
306 | }
307 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
[#SendableClosureCaptures]: <https://docs.swift.org/compiler/documentation/diagnostics/sendable-closure-captures>
[1380/1403] Compiling sloppy DebugAPIRouter.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:87:29: warning: result of 'try?' is unused [#no-usage]
85 | // Upgrade completion is not guaranteed to run on the channel loop.
86 | context.eventLoop.execute {
87 | try? context.pipeline.syncOperations.removeHandler(httpHandler)
| `- warning: result of 'try?' is unused [#no-usage]
88 | }
89 | }
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:93:40: warning: type 'any HTTPServerProtocolUpgrader' does not conform to the 'Sendable' protocol
91 |
92 | return channel.pipeline.configureHTTPServerPipeline(
93 | withServerUpgrade: upgradeConfig
| `- warning: type 'any HTTPServerProtocolUpgrader' does not conform to the 'Sendable' protocol
94 | ).flatMap {
95 | channel.pipeline.addHandler(httpHandler)
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:87:34: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
85 | // Upgrade completion is not guaranteed to run on the channel loop.
86 | context.eventLoop.execute {
87 | try? context.pipeline.syncOperations.removeHandler(httpHandler)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
88 | }
89 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:87:29: warning: no calls to throwing functions occur within 'try' expression
85 | // Upgrade completion is not guaranteed to run on the channel loop.
86 | context.eventLoop.execute {
87 | try? context.pipeline.syncOperations.removeHandler(httpHandler)
| `- warning: no calls to throwing functions occur within 'try' expression
88 | }
89 | }
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:201:49: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
199 | switch result {
200 | case .success(let response):
201 | self.writeResponse(context: context, requestHead: head, response: response)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
202 | case .failure(let error):
203 | self.logger.error("Failed to handle request: \(String(describing: error))")
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:244:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
242 | return
243 | }
244 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
245 | context.close(promise: nil)
246 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:245:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
243 | }
244 | context.eventLoop.execute {
245 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
246 | }
247 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:323:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
321 | return
322 | }
323 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
324 | context.close(promise: nil)
325 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:324:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
322 | }
323 | context.eventLoop.execute {
324 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
325 | }
326 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:410:29: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
408 | if !keepAlive {
409 | el.execute {
410 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
411 | }
412 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:410:29: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
408 | if !keepAlive {
409 | el.execute {
410 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
411 | }
412 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:590:21: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
588 | let frame = WebSocketFrame(fin: true, opcode: .connectionClose, data: data)
589 | context.writeAndFlush(self.wrapOutboundOut(frame)).whenComplete { _ in
590 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
591 | context.close(promise: nil)
592 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:591:25: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
589 | context.writeAndFlush(self.wrapOutboundOut(frame)).whenComplete { _ in
590 | context.eventLoop.execute {
591 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
592 | }
593 | continuation.resume()
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:283:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
281 | return
282 | }
283 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
284 | context.close(promise: nil)
285 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:284:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
282 | }
283 | context.eventLoop.execute {
284 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
285 | }
286 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:304:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
302 | return
303 | }
304 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
305 | context.close(promise: nil)
306 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:305:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
303 | }
304 | context.eventLoop.execute {
305 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
306 | }
307 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
[#SendableClosureCaptures]: <https://docs.swift.org/compiler/documentation/diagnostics/sendable-closure-captures>
[1381/1403] Compiling sloppy GitHubAPIRouter.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:87:29: warning: result of 'try?' is unused [#no-usage]
85 | // Upgrade completion is not guaranteed to run on the channel loop.
86 | context.eventLoop.execute {
87 | try? context.pipeline.syncOperations.removeHandler(httpHandler)
| `- warning: result of 'try?' is unused [#no-usage]
88 | }
89 | }
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:93:40: warning: type 'any HTTPServerProtocolUpgrader' does not conform to the 'Sendable' protocol
91 |
92 | return channel.pipeline.configureHTTPServerPipeline(
93 | withServerUpgrade: upgradeConfig
| `- warning: type 'any HTTPServerProtocolUpgrader' does not conform to the 'Sendable' protocol
94 | ).flatMap {
95 | channel.pipeline.addHandler(httpHandler)
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:87:34: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
85 | // Upgrade completion is not guaranteed to run on the channel loop.
86 | context.eventLoop.execute {
87 | try? context.pipeline.syncOperations.removeHandler(httpHandler)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
88 | }
89 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:87:29: warning: no calls to throwing functions occur within 'try' expression
85 | // Upgrade completion is not guaranteed to run on the channel loop.
86 | context.eventLoop.execute {
87 | try? context.pipeline.syncOperations.removeHandler(httpHandler)
| `- warning: no calls to throwing functions occur within 'try' expression
88 | }
89 | }
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:201:49: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
199 | switch result {
200 | case .success(let response):
201 | self.writeResponse(context: context, requestHead: head, response: response)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
202 | case .failure(let error):
203 | self.logger.error("Failed to handle request: \(String(describing: error))")
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:244:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
242 | return
243 | }
244 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
245 | context.close(promise: nil)
246 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:245:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
243 | }
244 | context.eventLoop.execute {
245 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
246 | }
247 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:323:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
321 | return
322 | }
323 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
324 | context.close(promise: nil)
325 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:324:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
322 | }
323 | context.eventLoop.execute {
324 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
325 | }
326 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:410:29: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
408 | if !keepAlive {
409 | el.execute {
410 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
411 | }
412 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:410:29: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
408 | if !keepAlive {
409 | el.execute {
410 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
411 | }
412 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:590:21: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
588 | let frame = WebSocketFrame(fin: true, opcode: .connectionClose, data: data)
589 | context.writeAndFlush(self.wrapOutboundOut(frame)).whenComplete { _ in
590 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
591 | context.close(promise: nil)
592 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/CoreHTTPServer.swift:591:25: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
589 | context.writeAndFlush(self.wrapOutboundOut(frame)).whenComplete { _ in
590 | context.eventLoop.execute {
591 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
592 | }
593 | continuation.resume()
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:283:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
281 | return
282 | }
283 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
284 | context.close(promise: nil)
285 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:284:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
282 | }
283 | context.eventLoop.execute {
284 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
285 | }
286 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:304:13: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
302 | return
303 | }
304 | context.eventLoop.execute {
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
305 | context.close(promise: nil)
306 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Gateway/DashboardHTTPServer.swift:305:17: warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
303 | }
304 | context.eventLoop.execute {
305 | context.close(promise: nil)
| `- warning: capture of 'context' with non-Sendable type 'ChannelHandlerContext' in a '@Sendable' closure [#SendableClosureCaptures]
306 | }
307 | }
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/ChannelPipeline.swift:1859:20: note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1857 | /// at the right point in time. Often, the right behaviour is to react to an event and then forward it to the next
1858 | /// `ChannelHandler`.
1859 | public final class ChannelHandlerContext: ChannelInvoker {
| `- note: class 'ChannelHandlerContext' does not conform to the 'Sendable' protocol
1860 | // visible for ChannelPipeline to modify
1861 | fileprivate var next: Optional<ChannelHandlerContext>
[#SendableClosureCaptures]: <https://docs.swift.org/compiler/documentation/diagnostics/sendable-closure-captures>
[1382/1403] Compiling sloppy SleepTool.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Utils/SystemLogHandler.swift:37:8: warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
35 | }
36 |
37 | struct SystemJSONLLogHandler: LogHandler {
| `- warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
38 | private static let configurationLock = NSLock()
39 | private nonisolated(unsafe) static var sharedWriter: SystemLogFileWriter?
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-log/Sources/Logging/LogHandler.swift:256:17: note: 'log(event:)' declared here
143 | ///
144 | /// - Parameter event: The log event containing the level, message, metadata, and source location.
145 | func log(event: LogEvent)
| `- note: requirement 'log(event:)' declared here
146 |
147 | /// Please do _not_ implement this method when you create a `LogHandler` implementation.
:
254 | /// Implement ``log(event:)`` in your ``LogHandler`` instead.
255 | @available(*, deprecated, message: "You should implement this method instead of using the default implementation")
256 | public func log(event: LogEvent) {
| `- note: 'log(event:)' declared here
257 | self.log(
258 | level: event.level,
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1383/1403] Compiling sloppy SystemListToolsTool.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Utils/SystemLogHandler.swift:37:8: warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
35 | }
36 |
37 | struct SystemJSONLLogHandler: LogHandler {
| `- warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
38 | private static let configurationLock = NSLock()
39 | private nonisolated(unsafe) static var sharedWriter: SystemLogFileWriter?
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-log/Sources/Logging/LogHandler.swift:256:17: note: 'log(event:)' declared here
143 | ///
144 | /// - Parameter event: The log event containing the level, message, metadata, and source location.
145 | func log(event: LogEvent)
| `- note: requirement 'log(event:)' declared here
146 |
147 | /// Please do _not_ implement this method when you create a `LogHandler` implementation.
:
254 | /// Implement ``log(event:)`` in your ``LogHandler`` instead.
255 | @available(*, deprecated, message: "You should implement this method instead of using the default implementation")
256 | public func log(event: LogEvent) {
| `- note: 'log(event:)' declared here
257 | self.log(
258 | level: event.level,
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1384/1403] Compiling sloppy VisorStatusTool.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Utils/SystemLogHandler.swift:37:8: warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
35 | }
36 |
37 | struct SystemJSONLLogHandler: LogHandler {
| `- warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
38 | private static let configurationLock = NSLock()
39 | private nonisolated(unsafe) static var sharedWriter: SystemLogFileWriter?
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-log/Sources/Logging/LogHandler.swift:256:17: note: 'log(event:)' declared here
143 | ///
144 | /// - Parameter event: The log event containing the level, message, metadata, and source location.
145 | func log(event: LogEvent)
| `- note: requirement 'log(event:)' declared here
146 |
147 | /// Please do _not_ implement this method when you create a `LogHandler` implementation.
:
254 | /// Implement ``log(event:)`` in your ``LogHandler`` instead.
255 | @available(*, deprecated, message: "You should implement this method instead of using the default implementation")
256 | public func log(event: LogEvent) {
| `- note: 'log(event:)' declared here
257 | self.log(
258 | level: event.level,
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1385/1403] Compiling sloppy WebFetchTool.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Utils/SystemLogHandler.swift:37:8: warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
35 | }
36 |
37 | struct SystemJSONLLogHandler: LogHandler {
| `- warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
38 | private static let configurationLock = NSLock()
39 | private nonisolated(unsafe) static var sharedWriter: SystemLogFileWriter?
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-log/Sources/Logging/LogHandler.swift:256:17: note: 'log(event:)' declared here
143 | ///
144 | /// - Parameter event: The log event containing the level, message, metadata, and source location.
145 | func log(event: LogEvent)
| `- note: requirement 'log(event:)' declared here
146 |
147 | /// Please do _not_ implement this method when you create a `LogHandler` implementation.
:
254 | /// Implement ``log(event:)`` in your ``LogHandler`` instead.
255 | @available(*, deprecated, message: "You should implement this method instead of using the default implementation")
256 | public func log(event: LogEvent) {
| `- note: 'log(event:)' declared here
257 | self.log(
258 | level: event.level,
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1386/1403] Compiling sloppy WebSearchTool.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Utils/SystemLogHandler.swift:37:8: warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
35 | }
36 |
37 | struct SystemJSONLLogHandler: LogHandler {
| `- warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
38 | private static let configurationLock = NSLock()
39 | private nonisolated(unsafe) static var sharedWriter: SystemLogFileWriter?
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-log/Sources/Logging/LogHandler.swift:256:17: note: 'log(event:)' declared here
143 | ///
144 | /// - Parameter event: The log event containing the level, message, metadata, and source location.
145 | func log(event: LogEvent)
| `- note: requirement 'log(event:)' declared here
146 |
147 | /// Please do _not_ implement this method when you create a `LogHandler` implementation.
:
254 | /// Implement ``log(event:)`` in your ``LogHandler`` instead.
255 | @available(*, deprecated, message: "You should implement this method instead of using the default implementation")
256 | public func log(event: LogEvent) {
| `- note: 'log(event:)' declared here
257 | self.log(
258 | level: event.level,
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1387/1403] Compiling sloppy FileSystemToolErrorMapping.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Utils/SystemLogHandler.swift:37:8: warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
35 | }
36 |
37 | struct SystemJSONLLogHandler: LogHandler {
| `- warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
38 | private static let configurationLock = NSLock()
39 | private nonisolated(unsafe) static var sharedWriter: SystemLogFileWriter?
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-log/Sources/Logging/LogHandler.swift:256:17: note: 'log(event:)' declared here
143 | ///
144 | /// - Parameter event: The log event containing the level, message, metadata, and source location.
145 | func log(event: LogEvent)
| `- note: requirement 'log(event:)' declared here
146 |
147 | /// Please do _not_ implement this method when you create a `LogHandler` implementation.
:
254 | /// Implement ``log(event:)`` in your ``LogHandler`` instead.
255 | @available(*, deprecated, message: "You should implement this method instead of using the default implementation")
256 | public func log(event: LogEvent) {
| `- note: 'log(event:)' declared here
257 | self.log(
258 | level: event.level,
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1388/1403] Compiling sloppy SubagentDelegation.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Utils/SystemLogHandler.swift:37:8: warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
35 | }
36 |
37 | struct SystemJSONLLogHandler: LogHandler {
| `- warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
38 | private static let configurationLock = NSLock()
39 | private nonisolated(unsafe) static var sharedWriter: SystemLogFileWriter?
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-log/Sources/Logging/LogHandler.swift:256:17: note: 'log(event:)' declared here
143 | ///
144 | /// - Parameter event: The log event containing the level, message, metadata, and source location.
145 | func log(event: LogEvent)
| `- note: requirement 'log(event:)' declared here
146 |
147 | /// Please do _not_ implement this method when you create a `LogHandler` implementation.
:
254 | /// Implement ``log(event:)`` in your ``LogHandler`` instead.
255 | @available(*, deprecated, message: "You should implement this method instead of using the default implementation")
256 | public func log(event: LogEvent) {
| `- note: 'log(event:)' declared here
257 | self.log(
258 | level: event.level,
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1389/1403] Compiling sloppy ToolAuthorizationService.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Utils/SystemLogHandler.swift:37:8: warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
35 | }
36 |
37 | struct SystemJSONLLogHandler: LogHandler {
| `- warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
38 | private static let configurationLock = NSLock()
39 | private nonisolated(unsafe) static var sharedWriter: SystemLogFileWriter?
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-log/Sources/Logging/LogHandler.swift:256:17: note: 'log(event:)' declared here
143 | ///
144 | /// - Parameter event: The log event containing the level, message, metadata, and source location.
145 | func log(event: LogEvent)
| `- note: requirement 'log(event:)' declared here
146 |
147 | /// Please do _not_ implement this method when you create a `LogHandler` implementation.
:
254 | /// Implement ``log(event:)`` in your ``LogHandler`` instead.
255 | @available(*, deprecated, message: "You should implement this method instead of using the default implementation")
256 | public func log(event: LogEvent) {
| `- note: 'log(event:)' declared here
257 | self.log(
258 | level: event.level,
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1390/1403] Compiling sloppy ToolCatalog.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Utils/SystemLogHandler.swift:37:8: warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
35 | }
36 |
37 | struct SystemJSONLLogHandler: LogHandler {
| `- warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
38 | private static let configurationLock = NSLock()
39 | private nonisolated(unsafe) static var sharedWriter: SystemLogFileWriter?
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-log/Sources/Logging/LogHandler.swift:256:17: note: 'log(event:)' declared here
143 | ///
144 | /// - Parameter event: The log event containing the level, message, metadata, and source location.
145 | func log(event: LogEvent)
| `- note: requirement 'log(event:)' declared here
146 |
147 | /// Please do _not_ implement this method when you create a `LogHandler` implementation.
:
254 | /// Implement ``log(event:)`` in your ``LogHandler`` instead.
255 | @available(*, deprecated, message: "You should implement this method instead of using the default implementation")
256 | public func log(event: LogEvent) {
| `- note: 'log(event:)' declared here
257 | self.log(
258 | level: event.level,
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1391/1403] Compiling sloppy ToolExecutionService.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Utils/SystemLogHandler.swift:37:8: warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
35 | }
36 |
37 | struct SystemJSONLLogHandler: LogHandler {
| `- warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
38 | private static let configurationLock = NSLock()
39 | private nonisolated(unsafe) static var sharedWriter: SystemLogFileWriter?
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-log/Sources/Logging/LogHandler.swift:256:17: note: 'log(event:)' declared here
143 | ///
144 | /// - Parameter event: The log event containing the level, message, metadata, and source location.
145 | func log(event: LogEvent)
| `- note: requirement 'log(event:)' declared here
146 |
147 | /// Please do _not_ implement this method when you create a `LogHandler` implementation.
:
254 | /// Implement ``log(event:)`` in your ``LogHandler`` instead.
255 | @available(*, deprecated, message: "You should implement this method instead of using the default implementation")
256 | public func log(event: LogEvent) {
| `- note: 'log(event:)' declared here
257 | self.log(
258 | level: event.level,
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1392/1403] Compiling sloppy ToolExecutionWorkerExecutorAdapter.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Utils/SystemLogHandler.swift:37:8: warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
35 | }
36 |
37 | struct SystemJSONLLogHandler: LogHandler {
| `- warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
38 | private static let configurationLock = NSLock()
39 | private nonisolated(unsafe) static var sharedWriter: SystemLogFileWriter?
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-log/Sources/Logging/LogHandler.swift:256:17: note: 'log(event:)' declared here
143 | ///
144 | /// - Parameter event: The log event containing the level, message, metadata, and source location.
145 | func log(event: LogEvent)
| `- note: requirement 'log(event:)' declared here
146 |
147 | /// Please do _not_ implement this method when you create a `LogHandler` implementation.
:
254 | /// Implement ``log(event:)`` in your ``LogHandler`` instead.
255 | @available(*, deprecated, message: "You should implement this method instead of using the default implementation")
256 | public func log(event: LogEvent) {
| `- note: 'log(event:)' declared here
257 | self.log(
258 | level: event.level,
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1393/1403] Compiling sloppy ToolHelpers.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Utils/SystemLogHandler.swift:37:8: warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
35 | }
36 |
37 | struct SystemJSONLLogHandler: LogHandler {
| `- warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
38 | private static let configurationLock = NSLock()
39 | private nonisolated(unsafe) static var sharedWriter: SystemLogFileWriter?
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-log/Sources/Logging/LogHandler.swift:256:17: note: 'log(event:)' declared here
143 | ///
144 | /// - Parameter event: The log event containing the level, message, metadata, and source location.
145 | func log(event: LogEvent)
| `- note: requirement 'log(event:)' declared here
146 |
147 | /// Please do _not_ implement this method when you create a `LogHandler` implementation.
:
254 | /// Implement ``log(event:)`` in your ``LogHandler`` instead.
255 | @available(*, deprecated, message: "You should implement this method instead of using the default implementation")
256 | public func log(event: LogEvent) {
| `- note: 'log(event:)' declared here
257 | self.log(
258 | level: event.level,
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1394/1403] Compiling sloppy ToolLoopGuard.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Utils/SystemLogHandler.swift:37:8: warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
35 | }
36 |
37 | struct SystemJSONLLogHandler: LogHandler {
| `- warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
38 | private static let configurationLock = NSLock()
39 | private nonisolated(unsafe) static var sharedWriter: SystemLogFileWriter?
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-log/Sources/Logging/LogHandler.swift:256:17: note: 'log(event:)' declared here
143 | ///
144 | /// - Parameter event: The log event containing the level, message, metadata, and source location.
145 | func log(event: LogEvent)
| `- note: requirement 'log(event:)' declared here
146 |
147 | /// Please do _not_ implement this method when you create a `LogHandler` implementation.
:
254 | /// Implement ``log(event:)`` in your ``LogHandler`` instead.
255 | @available(*, deprecated, message: "You should implement this method instead of using the default implementation")
256 | public func log(event: LogEvent) {
| `- note: 'log(event:)' declared here
257 | self.log(
258 | level: event.level,
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1395/1403] Compiling sloppy ToolRegistry.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Utils/SystemLogHandler.swift:37:8: warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
35 | }
36 |
37 | struct SystemJSONLLogHandler: LogHandler {
| `- warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
38 | private static let configurationLock = NSLock()
39 | private nonisolated(unsafe) static var sharedWriter: SystemLogFileWriter?
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-log/Sources/Logging/LogHandler.swift:256:17: note: 'log(event:)' declared here
143 | ///
144 | /// - Parameter event: The log event containing the level, message, metadata, and source location.
145 | func log(event: LogEvent)
| `- note: requirement 'log(event:)' declared here
146 |
147 | /// Please do _not_ implement this method when you create a `LogHandler` implementation.
:
254 | /// Implement ``log(event:)`` in your ``LogHandler`` instead.
255 | @available(*, deprecated, message: "You should implement this method instead of using the default implementation")
256 | public func log(event: LogEvent) {
| `- note: 'log(event:)' declared here
257 | self.log(
258 | level: event.level,
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1396/1403] Compiling sloppy NetworkAddressResolver.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Utils/SystemLogHandler.swift:37:8: warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
35 | }
36 |
37 | struct SystemJSONLLogHandler: LogHandler {
| `- warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
38 | private static let configurationLock = NSLock()
39 | private nonisolated(unsafe) static var sharedWriter: SystemLogFileWriter?
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-log/Sources/Logging/LogHandler.swift:256:17: note: 'log(event:)' declared here
143 | ///
144 | /// - Parameter event: The log event containing the level, message, metadata, and source location.
145 | func log(event: LogEvent)
| `- note: requirement 'log(event:)' declared here
146 |
147 | /// Please do _not_ implement this method when you create a `LogHandler` implementation.
:
254 | /// Implement ``log(event:)`` in your ``LogHandler`` instead.
255 | @available(*, deprecated, message: "You should implement this method instead of using the default implementation")
256 | public func log(event: LogEvent) {
| `- note: 'log(event:)' declared here
257 | self.log(
258 | level: event.level,
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1397/1403] Compiling sloppy SystemLogHandler.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Utils/SystemLogHandler.swift:37:8: warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
35 | }
36 |
37 | struct SystemJSONLLogHandler: LogHandler {
| `- warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
38 | private static let configurationLock = NSLock()
39 | private nonisolated(unsafe) static var sharedWriter: SystemLogFileWriter?
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-log/Sources/Logging/LogHandler.swift:256:17: note: 'log(event:)' declared here
143 | ///
144 | /// - Parameter event: The log event containing the level, message, metadata, and source location.
145 | func log(event: LogEvent)
| `- note: requirement 'log(event:)' declared here
146 |
147 | /// Please do _not_ implement this method when you create a `LogHandler` implementation.
:
254 | /// Implement ``log(event:)`` in your ``LogHandler`` instead.
255 | @available(*, deprecated, message: "You should implement this method instead of using the default implementation")
256 | public func log(event: LogEvent) {
| `- note: 'log(event:)' declared here
257 | self.log(
258 | level: event.level,
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1398/1403] Compiling sloppy VisorScheduler.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Utils/SystemLogHandler.swift:37:8: warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
35 | }
36 |
37 | struct SystemJSONLLogHandler: LogHandler {
| `- warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
38 | private static let configurationLock = NSLock()
39 | private nonisolated(unsafe) static var sharedWriter: SystemLogFileWriter?
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-log/Sources/Logging/LogHandler.swift:256:17: note: 'log(event:)' declared here
143 | ///
144 | /// - Parameter event: The log event containing the level, message, metadata, and source location.
145 | func log(event: LogEvent)
| `- note: requirement 'log(event:)' declared here
146 |
147 | /// Please do _not_ implement this method when you create a `LogHandler` implementation.
:
254 | /// Implement ``log(event:)`` in your ``LogHandler`` instead.
255 | @available(*, deprecated, message: "You should implement this method instead of using the default implementation")
256 | public func log(event: LogEvent) {
| `- note: 'log(event:)' declared here
257 | self.log(
258 | level: event.level,
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1399/1403] Compiling sloppy VisorTaskPlanner.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Utils/SystemLogHandler.swift:37:8: warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
35 | }
36 |
37 | struct SystemJSONLLogHandler: LogHandler {
| `- warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
38 | private static let configurationLock = NSLock()
39 | private nonisolated(unsafe) static var sharedWriter: SystemLogFileWriter?
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-log/Sources/Logging/LogHandler.swift:256:17: note: 'log(event:)' declared here
143 | ///
144 | /// - Parameter event: The log event containing the level, message, metadata, and source location.
145 | func log(event: LogEvent)
| `- note: requirement 'log(event:)' declared here
146 |
147 | /// Please do _not_ implement this method when you create a `LogHandler` implementation.
:
254 | /// Implement ``log(event:)`` in your ``LogHandler`` instead.
255 | @available(*, deprecated, message: "You should implement this method instead of using the default implementation")
256 | public func log(event: LogEvent) {
| `- note: 'log(event:)' declared here
257 | self.log(
258 | level: event.level,
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1400/1403] Compiling sloppy resource_bundle_accessor.swift
/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Utils/SystemLogHandler.swift:37:8: warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
35 | }
36 |
37 | struct SystemJSONLLogHandler: LogHandler {
| `- warning: deprecated default implementation is used to satisfy instance method 'log(event:)' required by protocol 'LogHandler': You should implement this method instead of using the default implementation [#DeprecatedDeclaration]
38 | private static let configurationLock = NSLock()
39 | private nonisolated(unsafe) static var sharedWriter: SystemLogFileWriter?
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-log/Sources/Logging/LogHandler.swift:256:17: note: 'log(event:)' declared here
143 | ///
144 | /// - Parameter event: The log event containing the level, message, metadata, and source location.
145 | func log(event: LogEvent)
| `- note: requirement 'log(event:)' declared here
146 |
147 | /// Please do _not_ implement this method when you create a `LogHandler` implementation.
:
254 | /// Implement ``log(event:)`` in your ``LogHandler`` instead.
255 | @available(*, deprecated, message: "You should implement this method instead of using the default implementation")
256 | public func log(event: LogEvent) {
| `- note: 'log(event:)' declared here
257 | self.log(
258 | level: event.level,
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1400/1403] Write Objects.LinkFileList
[1401/1403] Linking sloppy
[1402/1403] Applying sloppy
Build complete! (114.72s)
Fetching https://github.com/mattt/AnyLanguageModel.git
[1/3304] Fetching anylanguagemodel
Fetched https://github.com/mattt/AnyLanguageModel.git from cache (1.18s)
Fetching https://github.com/TeamSloppy/CodexBar.git
[1/13934] Fetching codexbar
Fetched https://github.com/TeamSloppy/CodexBar.git from cache (1.82s)
Fetching https://github.com/TeamSloppy/swift-acp
[1/269] Fetching swift-acp
Fetched https://github.com/TeamSloppy/swift-acp from cache (0.74s)
Fetching https://github.com/swiftlang/swift-tools-protocols.git
[1/33101] Fetching swift-tools-protocols
Fetched https://github.com/swiftlang/swift-tools-protocols.git from cache (1.51s)
Fetching https://github.com/apple/swift-log.git
Fetching https://github.com/mattt/PartialJSONDecoder
Fetching https://github.com/mattt/EventSource
Fetching https://github.com/modelcontextprotocol/swift-sdk.git
Fetching https://github.com/mattt/JSONSchema
Fetching https://github.com/apple/swift-syntax
Fetching https://github.com/apple/swift-system.git
[1/39] Fetching partialjsondecoder
[24/310] Fetching partialjsondecoder, eventsource
[144/517] Fetching partialjsondecoder, eventsource, jsonschema
[386/6118] Fetching partialjsondecoder, eventsource, jsonschema, swift-system
[412/9638] Fetching partialjsondecoder, eventsource, jsonschema, swift-system, swift-sdk
[800/16447] Fetching partialjsondecoder, eventsource, jsonschema, swift-system, swift-sdk, swift-log
Fetched https://github.com/apple/swift-log.git from cache (1.28s)
[1/75037] Fetching swift-syntax
Fetching https://github.com/apple/swift-distributed-tracing.git
[24013/80831] Fetching swift-syntax, swift-distributed-tracing
Fetched https://github.com/apple/swift-distributed-tracing.git from cache (1.20s)
[53277/75037] Fetching swift-syntax
Fetching https://github.com/apple/swift-nio.git
[75038/158267] Fetching swift-syntax, swift-nio
Fetched https://github.com/apple/swift-syntax from cache (4.37s)
Fetched https://github.com/modelcontextprotocol/swift-sdk.git from cache (4.37s)
Fetched https://github.com/mattt/PartialJSONDecoder from cache (4.37s)
Fetched https://github.com/apple/swift-system.git from cache (4.37s)
Fetched https://github.com/mattt/EventSource from cache (4.37s)
Fetched https://github.com/mattt/JSONSchema from cache (4.37s)
[9156/83230] Fetching swift-nio
Fetching https://github.com/apple/swift-configuration.git
Fetching https://github.com/steipete/SweetCookieKit
Fetching https://github.com/apple/swift-argument-parser.git
[34958/83578] Fetching swift-nio, sweetcookiekit
[35923/86830] Fetching swift-nio, sweetcookiekit, swift-configuration
[37179/104376] Fetching swift-nio, sweetcookiekit, swift-configuration, swift-argument-parser
Fetched https://github.com/steipete/SweetCookieKit from cache (1.03s)
Fetched https://github.com/apple/swift-configuration.git from cache (1.03s)
[36491/100776] Fetching swift-nio, swift-argument-parser
Fetched https://github.com/apple/swift-argument-parser.git from cache (1.68s)
[49938/83230] Fetching swift-nio
Fetched https://github.com/apple/swift-nio.git from cache (11.15s)
Computing version for https://github.com/steipete/SweetCookieKit
Computed https://github.com/steipete/SweetCookieKit at 0.4.0 (14.26s)
Computing version for https://github.com/apple/swift-syntax
Computed https://github.com/apple/swift-syntax at 600.0.1 (2.32s)
Computing version for https://github.com/mattt/PartialJSONDecoder
Computed https://github.com/mattt/PartialJSONDecoder at 1.0.0 (0.56s)
Computing version for https://github.com/apple/swift-distributed-tracing.git
Computed https://github.com/apple/swift-distributed-tracing.git at 1.4.1 (0.54s)
Fetching https://github.com/apple/swift-service-context.git
[1/1287] Fetching swift-service-context
Fetched https://github.com/apple/swift-service-context.git from cache (0.94s)
Computing version for https://github.com/apple/swift-configuration.git
Computed https://github.com/apple/swift-configuration.git at 0.2.0 (1.65s)
Fetching https://github.com/swift-server/swift-service-lifecycle
[1/2751] Fetching swift-service-lifecycle
Fetched https://github.com/swift-server/swift-service-lifecycle from cache (0.85s)
Computing version for https://github.com/mattt/JSONSchema
Computed https://github.com/mattt/JSONSchema at 1.3.1 (1.42s)
Fetching https://github.com/apple/swift-collections.git
[1/23880] Fetching swift-collections
Fetched https://github.com/apple/swift-collections.git from cache (2.08s)
Computing version for https://github.com/modelcontextprotocol/swift-sdk.git
Computed https://github.com/modelcontextprotocol/swift-sdk.git at 0.12.0 (2.67s)
Computing version for https://github.com/mattt/EventSource
Computed https://github.com/mattt/EventSource at 1.4.1 (0.56s)
Computing version for https://github.com/apple/swift-service-context.git
Computed https://github.com/apple/swift-service-context.git at 1.3.0 (0.54s)
Computing version for https://github.com/apple/swift-log.git
Computed https://github.com/apple/swift-log.git at 1.12.0 (0.56s)
Computing version for https://github.com/apple/swift-system.git
Computed https://github.com/apple/swift-system.git at 1.6.4 (0.59s)
Computing version for https://github.com/apple/swift-argument-parser.git
Computed https://github.com/apple/swift-argument-parser.git at 1.7.1 (0.56s)
Computing version for https://github.com/swift-server/swift-service-lifecycle
Computed https://github.com/swift-server/swift-service-lifecycle at 2.11.0 (0.54s)
Fetching https://github.com/apple/swift-async-algorithms.git
[1/6245] Fetching swift-async-algorithms
Fetched https://github.com/apple/swift-async-algorithms.git from cache (1.13s)
Computing version for https://github.com/apple/swift-async-algorithms.git
Computed https://github.com/apple/swift-async-algorithms.git at 1.1.3 (1.77s)
Computing version for https://github.com/apple/swift-collections.git
Computed https://github.com/apple/swift-collections.git at 1.4.1 (0.64s)
Computing version for https://github.com/apple/swift-nio.git
Computed https://github.com/apple/swift-nio.git at 2.99.0 (0.73s)
Fetching https://github.com/apple/swift-atomics.git
[1/1820] Fetching swift-atomics
Fetched https://github.com/apple/swift-atomics.git from cache (1.01s)
Computing version for https://github.com/apple/swift-atomics.git
Computed https://github.com/apple/swift-atomics.git at 1.3.0 (1.58s)
Creating working copy for https://github.com/apple/swift-atomics.git
Working copy of https://github.com/apple/swift-atomics.git resolved at 1.3.0
Creating working copy for https://github.com/mattt/PartialJSONDecoder
Working copy of https://github.com/mattt/PartialJSONDecoder resolved at 1.0.0
Creating working copy for https://github.com/TeamSloppy/swift-acp
Working copy of https://github.com/TeamSloppy/swift-acp resolved at main (71cb789)
Creating working copy for https://github.com/apple/swift-collections.git
Working copy of https://github.com/apple/swift-collections.git resolved at 1.4.1
Creating working copy for https://github.com/swiftlang/swift-tools-protocols.git
Working copy of https://github.com/swiftlang/swift-tools-protocols.git resolved at main (4967801)
Creating working copy for https://github.com/mattt/JSONSchema
Working copy of https://github.com/mattt/JSONSchema resolved at 1.3.1
Creating working copy for https://github.com/apple/swift-configuration.git
Working copy of https://github.com/apple/swift-configuration.git resolved at 0.2.0
Creating working copy for https://github.com/apple/swift-async-algorithms.git
Working copy of https://github.com/apple/swift-async-algorithms.git resolved at 1.1.3
Creating working copy for https://github.com/mattt/EventSource
Working copy of https://github.com/mattt/EventSource resolved at 1.4.1
Creating working copy for https://github.com/apple/swift-service-context.git
Working copy of https://github.com/apple/swift-service-context.git resolved at 1.3.0
Creating working copy for https://github.com/apple/swift-log.git
Working copy of https://github.com/apple/swift-log.git resolved at 1.12.0
Creating working copy for https://github.com/steipete/SweetCookieKit
Working copy of https://github.com/steipete/SweetCookieKit resolved at 0.4.0
Creating working copy for https://github.com/swift-server/swift-service-lifecycle
Working copy of https://github.com/swift-server/swift-service-lifecycle resolved at 2.11.0
Creating working copy for https://github.com/TeamSloppy/CodexBar.git
Working copy of https://github.com/TeamSloppy/CodexBar.git resolved at main (8a079c0)
Creating working copy for https://github.com/modelcontextprotocol/swift-sdk.git
Working copy of https://github.com/modelcontextprotocol/swift-sdk.git resolved at 0.12.0
Creating working copy for https://github.com/apple/swift-nio.git
Working copy of https://github.com/apple/swift-nio.git resolved at 2.99.0
Creating working copy for https://github.com/apple/swift-distributed-tracing.git
Working copy of https://github.com/apple/swift-distributed-tracing.git resolved at 1.4.1
Creating working copy for https://github.com/apple/swift-syntax
Working copy of https://github.com/apple/swift-syntax resolved at 600.0.1
Creating working copy for https://github.com/apple/swift-system.git
Working copy of https://github.com/apple/swift-system.git resolved at 1.6.4
Creating working copy for https://github.com/mattt/AnyLanguageModel.git
Working copy of https://github.com/mattt/AnyLanguageModel.git resolved at main (701d7e6)
Creating working copy for https://github.com/apple/swift-argument-parser.git
Working copy of https://github.com/apple/swift-argument-parser.git resolved at 1.7.1
Downloading package prebuilt https://download.swift.org/prebuilts/swift-syntax/600.0.1/swiftlang-6.2.4.1.4-MacroSupport-macos_aarch64.zip
Downloaded https://download.swift.org/prebuilts/swift-syntax/600.0.1/swiftlang-6.2.4.1.4-MacroSupport-macos_aarch64.zip (0.45s)
warning: 'anylanguagemodel': Conflicting identity for swift-syntax: dependency 'github.com/swiftlang/swift-syntax' and dependency 'github.com/apple/swift-syntax' both point to the same package identity 'swift-syntax'. The dependencies are introduced through the following chains: (A) /users/admin/builder/spi-builder-workspace->github.com/mattt/anylanguagemodel->github.com/swiftlang/swift-syntax (B) /users/admin/builder/spi-builder-workspace->github.com/teamsloppy/codexbar->github.com/apple/swift-syntax. If there are multiple chains that lead to the same dependency, only the first chain is shown here. To see all chains use debug output option. To resolve the conflict, coordinate with the maintainer of the package that introduces the conflicting dependency. This will be escalated to an error in future versions of SwiftPM.
Build complete.
{
"dependencies" : [
{
"identity" : "swift-argument-parser",
"requirement" : {
"range" : [
{
"lower_bound" : "1.5.0",
"upper_bound" : "2.0.0"
}
]
},
"type" : "sourceControl",
"url" : "https://github.com/apple/swift-argument-parser.git"
},
{
"identity" : "swift-configuration",
"requirement" : {
"range" : [
{
"lower_bound" : "0.2.0",
"upper_bound" : "1.0.0"
}
]
},
"type" : "sourceControl",
"url" : "https://github.com/apple/swift-configuration.git"
},
{
"identity" : "swift-log",
"requirement" : {
"range" : [
{
"lower_bound" : "1.6.0",
"upper_bound" : "2.0.0"
}
]
},
"type" : "sourceControl",
"url" : "https://github.com/apple/swift-log.git"
},
{
"identity" : "swift-nio",
"requirement" : {
"range" : [
{
"lower_bound" : "2.74.0",
"upper_bound" : "3.0.0"
}
]
},
"type" : "sourceControl",
"url" : "https://github.com/apple/swift-nio.git"
},
{
"identity" : "swift-distributed-tracing",
"requirement" : {
"range" : [
{
"lower_bound" : "1.4.1",
"upper_bound" : "2.0.0"
}
]
},
"type" : "sourceControl",
"url" : "https://github.com/apple/swift-distributed-tracing.git"
},
{
"identity" : "swift-system",
"requirement" : {
"range" : [
{
"lower_bound" : "1.6.0",
"upper_bound" : "2.0.0"
}
]
},
"type" : "sourceControl",
"url" : "https://github.com/apple/swift-system.git"
},
{
"identity" : "anylanguagemodel",
"requirement" : {
"branch" : [
"main"
]
},
"type" : "sourceControl",
"url" : "https://github.com/mattt/AnyLanguageModel.git"
},
{
"identity" : "codexbar",
"requirement" : {
"branch" : [
"main"
]
},
"type" : "sourceControl",
"url" : "https://github.com/TeamSloppy/CodexBar.git"
},
{
"identity" : "swift-sdk",
"requirement" : {
"range" : [
{
"lower_bound" : "0.11.0",
"upper_bound" : "1.0.0"
}
]
},
"type" : "sourceControl",
"url" : "https://github.com/modelcontextprotocol/swift-sdk.git"
},
{
"identity" : "swift-acp",
"requirement" : {
"branch" : [
"main"
]
},
"type" : "sourceControl",
"url" : "https://github.com/TeamSloppy/swift-acp"
},
{
"identity" : "swift-tools-protocols",
"requirement" : {
"branch" : [
"main"
]
},
"type" : "sourceControl",
"url" : "https://github.com/swiftlang/swift-tools-protocols.git"
}
],
"manifest_display_name" : "Sloppy",
"name" : "Sloppy",
"path" : "/Users/admin/builder/spi-builder-workspace",
"platforms" : [
{
"name" : "macos",
"version" : "14.0"
}
],
"products" : [
{
"name" : "Protocols",
"targets" : [
"Protocols"
],
"type" : {
"library" : [
"automatic"
]
}
},
{
"name" : "PluginSDK",
"targets" : [
"PluginSDK"
],
"type" : {
"library" : [
"automatic"
]
}
},
{
"name" : "AgentRuntime",
"targets" : [
"AgentRuntime"
],
"type" : {
"library" : [
"automatic"
]
}
},
{
"name" : "ChannelPluginSupport",
"targets" : [
"ChannelPluginSupport"
],
"type" : {
"library" : [
"automatic"
]
}
},
{
"name" : "ChannelPluginTelegram",
"targets" : [
"ChannelPluginTelegram"
],
"type" : {
"library" : [
"automatic"
]
}
},
{
"name" : "ChannelPluginDiscord",
"targets" : [
"ChannelPluginDiscord"
],
"type" : {
"library" : [
"automatic"
]
}
},
{
"name" : "sloppy",
"targets" : [
"sloppy"
],
"type" : {
"executable" : null
}
},
{
"name" : "SloppyNode",
"targets" : [
"SloppyNode"
],
"type" : {
"executable" : null
}
}
],
"targets" : [
{
"c99name" : "sloppyTests",
"module_type" : "SwiftTarget",
"name" : "sloppyTests",
"path" : "Tests/sloppyTests",
"sources" : [
"ACPConfigTests.swift",
"ACPSessionManagerTests.swift",
"AgentModelResolutionTests.swift",
"AgentPetTests.swift",
"AgentSessionOrchestratorTests.swift",
"AgentToolsFileStoreTests.swift",
"AgentsDelegateTaskToolTests.swift",
"BuiltInChannelPluginLifecycleTests.swift",
"CLITests.swift",
"ChannelDeliveryServiceTests.swift",
"ChannelGatewayScopeTests.swift",
"ChannelInboundBtwParsingTests.swift",
"ChannelModelStoreTests.swift",
"ChannelSessionFileStoreTests.swift",
"CoreConfig+Testing.swift",
"CoreConfigTests.swift",
"CoreHTTPServerTests.swift",
"CoreMainTests.swift",
"CoreModelProviderFactoryTests.swift",
"CoreRouterTests.swift",
"DashboardTerminalTests.swift",
"DiscordGatewayPluginTests.swift",
"FilesReadToolTests.swift",
"GatewayToolInvocationTests.swift",
"GitHubAuthServiceTests.swift",
"GitWorktreeServiceTests.swift",
"HeartbeatTests.swift",
"HybridMemoryStoreTests.swift",
"LSPToolTests.swift",
"OAuthAnthropicAuthHeadersTests.swift",
"OpenAIOAuthModelTranscriptTests.swift",
"OpenAIOAuthServiceTests.swift",
"OpenProjectTests.swift",
"PendingApprovalTests.swift",
"ProjectArchiveTests.swift",
"ProjectFilesTests.swift",
"ProjectTaskToolProjectIdTests.swift",
"PromptTemplateTests.swift",
"ProviderProbeTests.swift",
"ResolveSessionIDTests.swift",
"ReviewFlowTests.swift",
"SearchProviderServiceTests.swift",
"SessionProcessRegistryTests.swift",
"SessionToolsTests.swift",
"SkillSKILLFrontmatterTests.swift",
"SkillsGitHubClientTests.swift",
"SkillsRegistryServiceTests.swift",
"SleepToolTests.swift",
"SloppyToolExecutionDelegateTests.swift",
"SloppyVersionTests.swift",
"SubagentDelegationTests.swift",
"SwarmCoordinatorTests.swift",
"TaskActivitiesTests.swift",
"TaskApprovalCommandParserTests.swift",
"TaskClarificationTests.swift",
"TaskCommentsTests.swift",
"TaskCompletionConfirmationTests.swift",
"TeamHandoffTests.swift",
"TelegramModelPickerTests.swift",
"TelegramPluginConfigTests.swift",
"ToolLoopGuardTests.swift",
"ToolPathResolutionTests.swift",
"ToolRegistryTests.swift",
"UpdateCheckerServiceTests.swift",
"UpdatesAPITests.swift",
"VisorPhase4CoreTests.swift",
"VisorSchedulerTests.swift",
"VisorTodoLoopTests.swift",
"WebFetchServiceTests.swift"
],
"target_dependencies" : [
"sloppy",
"AgentRuntime",
"ChannelPluginDiscord",
"ChannelPluginTelegram",
"ChannelPluginSupport",
"Protocols",
"PluginSDK",
"CSQLite3"
],
"type" : "test"
},
{
"c99name" : "sloppy",
"module_type" : "SwiftTarget",
"name" : "sloppy",
"path" : "Sources/sloppy",
"product_dependencies" : [
"AnyLanguageModel",
"ArgumentParser",
"Configuration",
"Logging",
"NIOCore",
"NIOPosix",
"NIOHTTP1",
"NIOWebSocket",
"Tracing",
"CodexBarCore",
"MCP",
"ACP",
"ACPModel",
"ACPHTTP",
"SystemPackage",
"LanguageServerProtocol",
"LanguageServerProtocolTransport"
],
"product_memberships" : [
"sloppy"
],
"resources" : [
{
"path" : "/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Resources/Prompts/en/partials/branching_rules.md",
"rule" : {
"process" : {
}
}
},
{
"path" : "/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Resources/Prompts/en/partials/cli_awareness.md",
"rule" : {
"process" : {
}
}
},
{
"path" : "/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Resources/Prompts/en/partials/documentation_awareness.md",
"rule" : {
"process" : {
}
}
},
{
"path" : "/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Resources/Prompts/en/partials/memory_rules.md",
"rule" : {
"process" : {
}
}
},
{
"path" : "/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Resources/Prompts/en/partials/runtime_rules.md",
"rule" : {
"process" : {
}
}
},
{
"path" : "/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Resources/Prompts/en/partials/session_capabilities.md",
"rule" : {
"process" : {
}
}
},
{
"path" : "/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Resources/Prompts/en/partials/skills_rules.md",
"rule" : {
"process" : {
}
}
},
{
"path" : "/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Resources/Prompts/en/partials/tools_instruction.md",
"rule" : {
"process" : {
}
}
},
{
"path" : "/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Resources/Prompts/en/partials/worker_rules.md",
"rule" : {
"process" : {
}
}
},
{
"path" : "/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Resources/sloppy-version.json",
"rule" : {
"process" : {
}
}
},
{
"path" : "/Users/admin/builder/spi-builder-workspace/Sources/sloppy/Storage/schema.sql",
"rule" : {
"process" : {
}
}
}
],
"sources" : [
"ACP/ACPSessionManager.swift",
"ACP/ACPSessionStateStore.swift",
"ACP/ACPTransportClients.swift",
"Agent/AgentCatalogFileStore.swift",
"Agent/AgentCronTask.swift",
"Agent/AgentPetSupport.swift",
"Agent/AgentPromptComposer.swift",
"Agent/AgentSessionFileStore.swift",
"Agent/AgentSessionOrchestrator.swift",
"Agent/AgentSkillsFileStore.swift",
"Agent/AgentToolsFileStore.swift",
"Agent/SkillSKILLFrontmatter.swift",
"CLI/CLIFormatters.swift",
"CLI/CLIStyle.swift",
"CLI/Commands/ActorCommands.swift",
"CLI/Commands/AgentCommands.swift",
"CLI/Commands/ChannelCommands.swift",
"CLI/Commands/ConfigCommands.swift",
"CLI/Commands/MCPCommands.swift",
"CLI/Commands/PluginCommands.swift",
"CLI/Commands/ProjectCommands.swift",
"CLI/Commands/ProvidersCommands.swift",
"CLI/Commands/RunCommand.swift",
"CLI/Commands/ServiceCommands.swift",
"CLI/Commands/SkillsCommands.swift",
"CLI/Commands/SystemCommands.swift",
"CLI/Commands/VisorCommands.swift",
"CLI/SloppyCLIClient.swift",
"CLI/SloppyGroupCommand.swift",
"Channels/ChannelDeliveryService.swift",
"Channels/ChannelInboundBtwParsing.swift",
"Channels/ChannelModelStore.swift",
"Channels/ChannelSessionFileStore.swift",
"Channels/ChannelStreamCancelRegistry.swift",
"CoreConfig.swift",
"CorePersistenceFactory.swift",
"CoreService+ActorBoard.swift",
"CoreService+Agents.swift",
"CoreService+ChannelAccess.swift",
"CoreService+ChannelModel.swift",
"CoreService+ChannelPlugins.swift",
"CoreService+Channels.swift",
"CoreService+Config.swift",
"CoreService+CronTasks.swift",
"CoreService+DashboardAuth.swift",
"CoreService+DashboardTerminal.swift",
"CoreService+Debug.swift",
"CoreService+GatewayPlugins.swift",
"CoreService+InboundMessageReceiver.swift",
"CoreService+MemoryCheckpoint.swift",
"CoreService+Projects.swift",
"CoreService+Providers.swift",
"CoreService+Runtime.swift",
"CoreService+Sessions.swift",
"CoreService+Skills.swift",
"CoreService+Support.swift",
"CoreService+Swarm.swift",
"CoreService+TaskActivity.swift",
"CoreService+TaskClarifications.swift",
"CoreService+TaskComments.swift",
"CoreService+TaskLifecycle.swift",
"CoreService+TelegramModelPickerBridge.swift",
"CoreService+Tools.swift",
"CoreService+Visor.swift",
"CoreService.swift",
"CronEvaluator.swift",
"Gateway/CoreHTTPServer.swift",
"Gateway/CoreRouter.swift",
"Gateway/DashboardHTTPServer.swift",
"Gateway/Routers/ACPAPIRouter.swift",
"Gateway/Routers/APIRouter.swift",
"Gateway/Routers/ActorsAPIRouter.swift",
"Gateway/Routers/AgentsAPIRouter.swift",
"Gateway/Routers/ArtifactsAPIRouter.swift",
"Gateway/Routers/ChannelsAPIRouter.swift",
"Gateway/Routers/CoreRouter+HTTPRoutes.swift",
"Gateway/Routers/CoreRouterRegistrar.swift",
"Gateway/Routers/CronAPIRouter.swift",
"Gateway/Routers/DebugAPIRouter.swift",
"Gateway/Routers/GitHubAPIRouter.swift",
"Gateway/Routers/PluginsAPIRouter.swift",
"Gateway/Routers/ProjectsAPIRouter.swift",
"Gateway/Routers/ProvidersAPIRouter.swift",
"Gateway/Routers/SessionsAPIRouter.swift",
"Gateway/Routers/SkillsAPIRouter.swift",
"Gateway/Routers/SystemAPIRouter.swift",
"Gateway/Routers/TasksAPIRouter.swift",
"GitWorktreeService.swift",
"JSONValueTypealias.swift",
"LSP/LSPServerManager.swift",
"MCP/MCPClientRegistry.swift",
"Memory/EmbeddingService.swift",
"Memory/HybridMemoryStore.swift",
"Memory/MemoryOutboxIndexer.swift",
"Memory/MemoryProvider.swift",
"PluginLoader.swift",
"Projects/ProjectContextLoader.swift",
"Prompts/PromptProcessKind.swift",
"Prompts/PromptRenderContext.swift",
"Prompts/PromptTemplateLoader.swift",
"Prompts/PromptTemplateRenderer.swift",
"Providers/AnthropicModelProviderFactory.swift",
"Providers/AnthropicOAuthService.swift",
"Providers/CoreModelProviderFactory.swift",
"Providers/GeminiModelProviderFactory.swift",
"Providers/OllamaModelProviderFactory.swift",
"Providers/OpenAICompatibleCatalogEndpoint.swift",
"Providers/OpenAIModelProviderFactory.swift",
"Providers/OpenAIOAuthService.swift",
"Providers/OpenAIProviderCatalogService.swift",
"Providers/OpenAPIGenerator.swift",
"Providers/OpenRouterModelProviderFactory.swift",
"Providers/ProxySessionFactory.swift",
"RecoveryManager.swift",
"Runners/CronRunner.swift",
"Runners/HeartbeatRunner.swift",
"SQLiteStore.swift",
"Services/BuildMetadataResolver.swift",
"Services/GitHubAuthService.swift",
"Services/KanbanEventService.swift",
"Services/NotificationService.swift",
"Services/PendingApprovalService.swift",
"Services/ProviderProbeService.swift",
"Services/SearchProviderService.swift",
"Services/UpdateCheckerService.swift",
"Services/WebFetchService.swift",
"SessionProcessRegistry.swift",
"Skills/SkillsGitHubClient.swift",
"Skills/SkillsRegistryService.swift",
"SloppyApp.swift",
"SloppyVersion.swift",
"Stores/ActorBoardFileStore.swift",
"Stores/PersistenceStore.swift",
"Stores/SystemLogFileStore.swift",
"Support/IssueReportBuilder.swift",
"Swarm/SwarmCoordinator.swift",
"Swarm/SwarmPlanner.swift",
"TaskApprovalCommandParser.swift",
"Terminal/DashboardTerminalService.swift",
"Tools/AgentTools/Agents/ActorConcludeDiscussionTool.swift",
"Tools/AgentTools/Agents/ActorDiscussTool.swift",
"Tools/AgentTools/Agents/AgentDocumentsMarkdownTools.swift",
"Tools/AgentTools/Agents/AgentsDelegateTaskTool.swift",
"Tools/AgentTools/Agents/AgentsListTool.swift",
"Tools/AgentTools/Agents/BranchesSpawnTool.swift",
"Tools/AgentTools/Agents/SkillsTools.swift",
"Tools/AgentTools/Agents/WorkersRouteTool.swift",
"Tools/AgentTools/Agents/WorkersSpawnTool.swift",
"Tools/AgentTools/Files/FilesEditTool.swift",
"Tools/AgentTools/Files/FilesListTool.swift",
"Tools/AgentTools/Files/FilesReadTool.swift",
"Tools/AgentTools/Files/FilesWriteTool.swift",
"Tools/AgentTools/MCP/MCPConfigTools.swift",
"Tools/AgentTools/MCP/MCPTools.swift",
"Tools/AgentTools/Memory/MemoryGetTool.swift",
"Tools/AgentTools/Memory/MemorySaveTool.swift",
"Tools/AgentTools/Memory/MemorySearchTool.swift",
"Tools/AgentTools/Project/ProjectCreateTool.swift",
"Tools/AgentTools/Project/ProjectDeleteTool.swift",
"Tools/AgentTools/Project/ProjectEscalateTool.swift",
"Tools/AgentTools/Project/ProjectListTool.swift",
"Tools/AgentTools/Project/ProjectMetaMemoryTool.swift",
"Tools/AgentTools/Project/ProjectTaskCancelTool.swift",
"Tools/AgentTools/Project/ProjectTaskCreateTool.swift",
"Tools/AgentTools/Project/ProjectTaskGetTool.swift",
"Tools/AgentTools/Project/ProjectTaskListTool.swift",
"Tools/AgentTools/Project/ProjectTaskUpdateTool.swift",
"Tools/AgentTools/Project/ProjectUpdateTool.swift",
"Tools/AgentTools/Project/TaskClarificationCreateTool.swift",
"Tools/AgentTools/Sessions/ChannelHistoryTool.swift",
"Tools/AgentTools/Sessions/SessionsHistoryTool.swift",
"Tools/AgentTools/Sessions/SessionsListTool.swift",
"Tools/AgentTools/Sessions/SessionsSendTool.swift",
"Tools/AgentTools/Sessions/SessionsSpawnTool.swift",
"Tools/AgentTools/Sessions/SessionsStatusTool.swift",
"Tools/AgentTools/SystemTools/CoreTool.swift",
"Tools/AgentTools/SystemTools/CronTool.swift",
"Tools/AgentTools/SystemTools/LSPTool.swift",
"Tools/AgentTools/SystemTools/RuntimeExecTool.swift",
"Tools/AgentTools/SystemTools/RuntimeProcessTool.swift",
"Tools/AgentTools/SystemTools/SleepTool.swift",
"Tools/AgentTools/SystemTools/SystemListToolsTool.swift",
"Tools/AgentTools/Visor/VisorStatusTool.swift",
"Tools/AgentTools/Web/WebFetchTool.swift",
"Tools/AgentTools/Web/WebSearchTool.swift",
"Tools/FileSystemToolErrorMapping.swift",
"Tools/SubagentDelegation.swift",
"Tools/ToolAuthorizationService.swift",
"Tools/ToolCatalog.swift",
"Tools/ToolExecutionService.swift",
"Tools/ToolExecutionWorkerExecutorAdapter.swift",
"Tools/ToolHelpers.swift",
"Tools/ToolLoopGuard.swift",
"Tools/ToolRegistry.swift",
"Utils/NetworkAddressResolver.swift",
"Utils/SystemLogHandler.swift",
"Visor/VisorScheduler.swift",
"Visor/VisorTaskPlanner.swift"
],
"target_dependencies" : [
"AgentRuntime",
"ChannelPluginSupport",
"ChannelPluginDiscord",
"ChannelPluginTelegram",
"Protocols",
"PluginSDK",
"CSQLite3"
],
"type" : "executable"
},
{
"c99name" : "SloppyNode",
"module_type" : "SwiftTarget",
"name" : "SloppyNode",
"path" : "Sources/Node",
"product_dependencies" : [
"ArgumentParser",
"Logging"
],
"product_memberships" : [
"SloppyNode"
],
"sources" : [
"NodeDaemon.swift",
"NodeMain.swift"
],
"target_dependencies" : [
"Protocols",
"CSQLite3"
],
"type" : "executable"
},
{
"c99name" : "ProtocolsTests",
"module_type" : "SwiftTarget",
"name" : "ProtocolsTests",
"path" : "Tests/ProtocolsTests",
"sources" : [
"ACPModelsTests.swift",
"ActorSystemRoleTests.swift",
"ProtocolCompatibilityTests.swift",
"ProtocolEnvelopeTests.swift"
],
"target_dependencies" : [
"Protocols"
],
"type" : "test"
},
{
"c99name" : "Protocols",
"module_type" : "SwiftTarget",
"name" : "Protocols",
"path" : "Sources/Protocols",
"product_dependencies" : [
"Logging"
],
"product_memberships" : [
"Protocols",
"PluginSDK",
"AgentRuntime",
"ChannelPluginTelegram",
"ChannelPluginDiscord",
"sloppy",
"SloppyNode"
],
"sources" : [
"APIModels.swift",
"AgentMarkdownLimits.swift",
"CodableJSON.swift",
"ColoredLogHandler.swift",
"EventEnvelope.swift",
"JSONValue+Accessors.swift",
"JSONValue.swift",
"MemoryModels.swift",
"RuntimeModels.swift"
],
"type" : "library"
},
{
"c99name" : "PluginSDK",
"module_type" : "SwiftTarget",
"name" : "PluginSDK",
"path" : "Sources/PluginSDK",
"product_dependencies" : [
"AnyLanguageModel",
"Logging"
],
"product_memberships" : [
"PluginSDK",
"AgentRuntime",
"ChannelPluginTelegram",
"ChannelPluginDiscord",
"sloppy"
],
"sources" : [
"ChannelGatewayScope.swift",
"JSONValueTypealias.swift",
"OpenAIOauthModel.swift",
"OpenRouterLanguageModelSupport.swift",
"PluginProtocols.swift",
"Providers/AnthropicModelProvider.swift",
"Providers/CompositeModelProvider.swift",
"Providers/GeminiModelProvider.swift",
"Providers/OAuthAnthropicAuthHeaders.swift",
"Providers/OAuthAnthropicLanguageModel.swift",
"Providers/OAuthAnthropicURLProtocol.swift",
"Providers/OllamaModelProvider.swift",
"Providers/OpenAIModelProvider.swift",
"SloppyToolExecutionDelegate.swift",
"TelegramModelPickerBridge.swift"
],
"target_dependencies" : [
"Protocols"
],
"type" : "library"
},
{
"c99name" : "ChannelPluginTelegram",
"module_type" : "SwiftTarget",
"name" : "ChannelPluginTelegram",
"path" : "Sources/ChannelPluginTelegram",
"product_dependencies" : [
"Logging"
],
"product_memberships" : [
"ChannelPluginTelegram",
"sloppy"
],
"sources" : [
"TelegramBotAPI.swift",
"TelegramGatewayPlugin.swift",
"TelegramModelPicker.swift",
"TelegramPluginConfig.swift",
"TelegramPoller.swift"
],
"target_dependencies" : [
"ChannelPluginSupport",
"Protocols",
"PluginSDK"
],
"type" : "library"
},
{
"c99name" : "ChannelPluginSupport",
"module_type" : "SwiftTarget",
"name" : "ChannelPluginSupport",
"path" : "Sources/ChannelPluginSupport",
"product_memberships" : [
"ChannelPluginSupport",
"ChannelPluginTelegram",
"ChannelPluginDiscord",
"sloppy"
],
"sources" : [
"ChannelCommandHandler.swift",
"SkillSlashCommandNaming.swift"
],
"type" : "library"
},
{
"c99name" : "ChannelPluginDiscord",
"module_type" : "SwiftTarget",
"name" : "ChannelPluginDiscord",
"path" : "Sources/ChannelPluginDiscord",
"product_dependencies" : [
"Logging"
],
"product_memberships" : [
"ChannelPluginDiscord",
"sloppy"
],
"sources" : [
"DiscordGatewayLoop.swift",
"DiscordGatewayPlugin.swift",
"DiscordPluginConfig.swift",
"DiscordTransport.swift"
],
"target_dependencies" : [
"ChannelPluginSupport",
"Protocols",
"PluginSDK"
],
"type" : "library"
},
{
"c99name" : "CSQLite3",
"module_type" : "ClangTarget",
"name" : "CSQLite3",
"path" : "Sources/CSQLite3",
"product_memberships" : [
"sloppy",
"SloppyNode"
],
"sources" : [
],
"type" : "library"
},
{
"c99name" : "AgentRuntimeTests",
"module_type" : "SwiftTarget",
"name" : "AgentRuntimeTests",
"path" : "Tests/AgentRuntimeTests",
"sources" : [
"BranchRuntimeTodoRegressionTests.swift",
"EventPayloadRegressionTests.swift",
"RuntimeFlowTests.swift",
"VisorBulletinTests.swift",
"VisorPhase2Tests.swift",
"VisorPhase3Tests.swift",
"VisorPhase4Tests.swift",
"WorkerRuntimeExecutorTests.swift"
],
"target_dependencies" : [
"AgentRuntime",
"Protocols",
"PluginSDK"
],
"type" : "test"
},
{
"c99name" : "AgentRuntime",
"module_type" : "SwiftTarget",
"name" : "AgentRuntime",
"path" : "Sources/AgentRuntime",
"product_dependencies" : [
"Logging"
],
"product_memberships" : [
"AgentRuntime",
"sloppy"
],
"sources" : [
"BranchRuntime.swift",
"ChannelRuntime.swift",
"Compactor.swift",
"EventBus.swift",
"JSONValueTypealias.swift",
"MemoryStore.swift",
"RuntimeSystem.swift",
"Visor.swift",
"WorkerExecutor.swift",
"WorkerRuntime.swift"
],
"target_dependencies" : [
"Protocols",
"PluginSDK"
],
"type" : "library"
}
],
"tools_version" : "6.2"
}
Done.