// Copyright © 2022 Rangeproof Pty Ltd. All rights reserved. import Foundation import Combine import GRDB import SessionSnodeKit import SessionUtilitiesKit // MARK: - Log.Category private extension Log.Category { static let cat: Log.Category = .create("AttachmentUploadJob", defaultLevel: .info) } // MARK: - AttachmentUploadJob public enum AttachmentUploadJob: JobExecutor { public static var maxFailureCount: Int = 10 public static var requiresThreadId: Bool = true public static let requiresInteractionId: Bool = true public static func run( _ job: Job, scheduler: S, success: @escaping (Job, Bool) -> Void, failure: @escaping (Job, Error, Bool) -> Void, deferred: @escaping (Job) -> Void, using dependencies: Dependencies ) { guard let threadId: String = job.threadId, let interactionId: Int64 = job.interactionId, let detailsData: Data = job.details, let details: Details = try? JSONDecoder(using: dependencies).decode(Details.self, from: detailsData), let attachment: Attachment = dependencies[singleton: .storage] .read({ db in try Attachment.fetchOne(db, id: details.attachmentId) }) else { return failure(job, JobRunnerError.missingRequiredDetails, true) } // If the original interaction no longer exists then don't bother uploading the attachment (ie. the // message was deleted before it even got sent) guard dependencies[singleton: .storage].read({ db in try Interaction.exists(db, id: interactionId) }) == true else { Log.info(.cat, "Failed due to missing interaction") return failure(job, StorageError.objectNotFound, true) } // If the attachment is still pending download the hold off on running this job guard attachment.state != .pendingDownload && attachment.state != .downloading else { Log.info(.cat, "Deferred as attachment is still being downloaded") return deferred(job) } // If this upload is related to sending a message then trigger the 'handleMessageWillSend' logic // as if this is a retry the logic wouldn't run until after the upload has completed resulting in // a potentially incorrect delivery status dependencies[singleton: .storage].write { db in guard let sendJob: Job = try Job.fetchOne(db, id: details.messageSendJobId), let sendJobDetails: Data = sendJob.details, let details: MessageSendJob.Details = try? JSONDecoder(using: dependencies) .decode(MessageSendJob.Details.self, from: sendJobDetails) else { return } MessageSender.handleMessageWillSend( db, message: details.message, destination: details.destination, interactionId: interactionId ) } // Note: In the AttachmentUploadJob we intentionally don't provide our own db instance to prevent // reentrancy issues when the success/failure closures get called before the upload as the JobRunner // will attempt to update the state of the job immediately dependencies[singleton: .storage] .writePublisher { db -> Network.PreparedRequest in try attachment.preparedUpload(db, threadId: threadId, logCategory: .cat, using: dependencies) } .flatMap { $0.send(using: dependencies) } .subscribe(on: scheduler, using: dependencies) .receive(on: scheduler, using: dependencies) .sinkUntilComplete( receiveCompletion: { result in switch result { case .failure(let error): // If this upload is related to sending a message then trigger the // 'handleFailedMessageSend' logic as we want to ensure the message // has the correct delivery status var didLogError: Bool = false dependencies[singleton: .storage].read { db in guard let sendJob: Job = try Job.fetchOne(db, id: details.messageSendJobId), let sendJobDetails: Data = sendJob.details, let details: MessageSendJob.Details = try? JSONDecoder(using: dependencies) .decode(MessageSendJob.Details.self, from: sendJobDetails) else { return } MessageSender.handleFailedMessageSend( db, message: details.message, destination: nil, error: .other(.cat, "Failed", error), interactionId: interactionId, using: dependencies ) didLogError = true } // If we didn't log an error above then log it now if !didLogError { Log.error(.cat, "Failed due to error: \(error)") } failure(job, error, false) case .finished: success(job, false) } } ) } } // MARK: - AttachmentUploadJob.Details extension AttachmentUploadJob { public struct Details: Codable { /// This is the id for the messageSend job this attachmentUpload job is associated to, the value isn't used for any of /// the logic but we want to mandate that the attachmentUpload job can only be used alongside a messageSend job /// /// **Note:** If we do decide to remove this the `_003_YDBToGRDBMigration` will need to be updated as it /// fails if this connection can't be made public let messageSendJobId: Int64 /// The id of the `Attachment` to upload public let attachmentId: String public init(messageSendJobId: Int64, attachmentId: String) { self.messageSendJobId = messageSendJobId self.attachmentId = attachmentId } } }